Skip to main content
The control panel is a separate process with its own environment file — panel.env, installed by fireflo-panel-install and never replaced by an update.
It is not on the message path. A panel that is down costs you the ability to make changes, not the ability to send.

​
Required

​
Connecting to the gateway

GATEWAY_API_URL pointed at the ops port yields 404s on every playground call — the mirror of pointing GATEWAY_OPS_URL at the messaging port. The two are different ports carrying different things.
Under --vhost, CDR_EXPORT_DIR must also sit inside a BindPaths= root. That failure is silent — exports are prepared and then cannot be read.

​
The customer portal’s sign-in mail

A customer signs in through a magic link. With these unset, no customer can sign in at all — the portal says the link cannot be sent rather than failing silently, but nobody gets in.
FIREFLO_SMTP_SECURE is parsed as a yes or a no, not tested for presence — it was once the latter, which made FIREFLO_SMTP_SECURE=0 mean “yes”. An unrecognisable value now falls back to the port and logs.
See Installing the control panel for how these are derived at install time, and Portal access for the operator’s side of getting a customer signed in.