Frequently Asked Questions (FAQ)
Below are answers to the most frequently asked questions regarding the use and configuration of ERD Builder Pro.
Why should I use Port 6543 for Backup?
GitHub Actions runs in an environment that only supports IPv4. Since the latest Supabase database often uses IPv6, direct connections through the default port 5432 will fail. Port 6543 is the Transaction Pooler which provides a stable IPv4 path for the backup process.
How does this application work when Offline?
ERD Builder Pro is designed with an Offline-First approach.
- All changes you make are saved first to IndexedDB in your browser.
- When an internet connection is available, the system will automatically attempt to sync that local data to the Supabase (Cloud) database.
Is it safe to use a Public Bucket in Cloudflare R2?
Although the bucket is set to Public, your data remains safe because:
- Random File Names: Each image is given a unique UUID name that is impossible to guess.
- CORS Policy: You can restrict images to only load from your application's official domain.
- No Indexing: As long as the image links are not shared on public sites, search engines like Google will not be able to find them.
What does the "Experimental" label on some features mean?
Features labeled Experimental (such as Import Notes or Export PDF) are features that are functional but still in active development. You may encounter minor visual issues or small bugs. We recommend always backing up your database before trying these features extensively.
Can I change the theme color (Dark/Light Mode)?
ERD Builder Pro is currently optimized for Dark Mode to provide a focused and elegant design experience. Support for Light Mode is on our development roadmap.
Where can I see the application change log?
You can view the list of new features, bug fixes, and version updates directly through the Changelog menu, which is directly linked to our GitHub releases.
What if I forget my Supabase password?
Since authentication uses Supabase, you can reset your password or manage user accounts through the dashboard Supabase > Authentication > Users.
What if I forget my password in self-hosted mode (Local PostgreSQL / Docker)?
For self-hosted mode using local authentication (not Supabase), use the following CLI script from the project directory:
npm run reset-password -- --email your-admin-email@example.com --password newpassword123
This script will:
- Find the user by email
- Hash the new password using the
scryptalgorithm (same as normal login) - Update the password in the database
No application restart required. The user can log in immediately with the new password.
Why is admin@local.dev / admin123 invalid in self-host mode?
That combination is only the Desktop/CLI bootstrap credential. Local PostgreSQL self-host mode rejects it so a shared deployment does not run with a default password. After an empty database starts, use Create administrator account to create a super admin with a new email and password.
Why does the super-admin registration page appear again?
It appears when the database has no configured super admin or still contains the bootstrap account. Register with a new email/password and ensure the application uses the same DATABASE_URL as the database you seeded. /api/auth-config reads setup status directly from the database.
What happens if ERD_ENCRYPTION_KEY is lost or changed?
Stored DB Connect passwords and AI API keys cannot be decrypted. Restore the same key from your secret manager or environment backup. Do not generate a new key for an existing database unless you are ready to save all encrypted credentials again.