SubWave refuses to start without ADMIN_USER and ADMIN_PASS
The service sub-wave-controller did not start (unhealthy), so the application was not started either. It printed: [auth] FATAL: NODE_ENV=production but ADMIN_USER and ADMIN_PASS are not set. /debug, /settings and admin endpoints would be publicly readable. Set ADMIN_USER and ADMIN_PASS in controller/.env, then rebuild the controller. The full output is in the deploy log.
TypeErrorAn error that occurred in the deployed application. It is not necessarily a PanelAlpha Engine error, but we keep working on improvements so you run into fewer of them.
Seen1 times
WhereDocker Compose
StatusResolve ReadyOur team will look into this soon, verify the cause and try to fix it in an upcoming release.
Why it happens
The app's controller stops in production mode when no admin login is set, so its admin endpoints are never left open.
What the log looks like
Deploy log
error: service sub-wave-controller did not start (unhealthy): [auth] FATAL: NODE_ENV=production but ADMIN_USER and ADMIN_PASS are not set. /debug, /settings and admin endpoints would be publicly readable. Set ADMIN_USER and ADMIN_PASS in controller/.env, then rebuild the controller.Container sub-wave-controller Error dependency controller failed to startdependency failed to start: container sub-wave-controller is unhealthy