Configuration
Change how your panel behaves, whether the setting is on a screen or in a file.
Almost everything is in the admin area. A few values live in a file on the panel server, and this page covers both.
Configuration in the panel
Go to Admin > Settings. The tabs across the top hold most of what you configure day to day:
| Tab | What you set |
|---|---|
| General | The panel name, the panel URL, the custom domain, the timezone, and the language. |
| Features | The features that your users can reach, for example backups, schedules, and sub-users. |
| License | Your license key and the features that the license includes. |
| The outgoing mail server. | |
| Webhooks | Outbound webhooks for panel events. |
| OAuth / SSO | External sign-in providers. |
Some tabs appear only when your license includes that feature. The timezone and the language are under General > Localization. There is no timezone value in the configuration file.
TIP
If your license is bound to a domain, the Panel URL field shows a "Locked by license" mark. You cannot change it from the panel.
Other areas of the admin sidebar hold their own configuration:
- Admin > Nodes - the machines that run your game servers
- Admin > Databases - the external database hosts that game servers use
- Admin > Nests and Admin > Eggs - the game templates
- Admin > Users and Admin > Roles & Permissions - accounts and access
- Admin > Settings > Security - password rules, two-factor, and brute-force protection
- Admin > Settings > Advanced - the low-level options
Secrets
The installer asks where to keep your secrets. There are two answers.
BadgerVault. BadgerPanel holds your secrets and the panel reads them as it runs. That covers every password and key the installer generated. There is nothing for you to manage, and BadgerPanel support changes one for you on request.
Local file. The same values sit in plain text in the .env file on your server. The file permissions are 600.
The .env file records which mode is active in the BADGER_VAULT value. A copy of every generated credential is also written to the .credentials file next to it.
WARNING
Never share the .env file or the .credentials file. The encryption key protects sensitive database columns. If you lose that key, the data that it protects cannot be read again.
The environment file
The .env file sits in your installation directory, for example /root/badgerpanel/.env. The installer writes it. Change only these values:
| Value | Description |
|---|---|
APP_URL, APP_BASE_URL, API_URL | The full URL of your panel, for example https://panel.example.com. Keep all three the same. |
NEXT_PUBLIC_API_URL | The same URL again. The web interface calls the API at this address. |
CORS_ALLOWED_ORIGINS | The same URL again. A browser request from another origin is refused. |
HTTP_PORT, HTTPS_PORT | The ports the panel answers on. The defaults are 80 and 443. |
BP_VERSION | The image tag of the panel. The update flow sets this for you. |
The other values in the file are credentials and internal keys. Do not edit them by hand.
WARNING
If you change your panel URL, you must change every URL value in the list above. A mismatch causes sign-in failures and blank pages.
Apply a change
After you edit the .env file, restart the panel:
cd ~/badgerpanel
docker compose down
docker compose up -dThe panel is offline for less than a minute. A panel restart does not stop the game servers on your nodes. The daemons reconnect on their own.