Forced subscription screen on self-hosted instance even with HOSTED_ON_BIGCAPITAL_CLOUD=false

After a fresh self-hosted installation of Bigcapital, users are being forced to the subscription/upgrade screen (or redirected to `/setup`) even though `HOSTED_ON_BIGCAPITAL_CLOUD=false` is set. The app works correctly when accessed directly via IP + port, but the subscription modal appears when accessed through a reverse proxy (Traefik in Dokploy, Nginx Proxy Manager, etc.). ### Steps to Reproduce 1. Deploy Bigcapital using Docker / Dokploy (or any reverse proxy). 2. Be sure to set the following environment variables: ``` HOSTED_ON_BIGCAPITAL_CLOUD=false BASE_URL=https://yourdomain.com ``` 3. Complete registration and create the first organization. 4. Access the app through the domain (via proxy). 5. Use normal, shut down container, restart container 6. Should then observe the issue of going to `/setup` **Expected behavior:** No subscription enforcement — full functionality should be available for self-hosted users. **Actual behavior:** Forced subscription screen (eventually) appears (even clicking Subscribe doesn't do anything for what it's worth). The screen disappears only when accessing the app directly on the backend port (e.g. `:3000`). ### Additional Information - This issue has also been reported on Discord. - Migrations run successfully. - Traefik routing for `/api` paths is correctly configured. ### Environment - Bigcapital latest version (`bigcapitalhq/server:latest` + `bigcapitalhq/webapp:latest`) - Docker / Dokploy - Reverse proxy: Traefik (Dokploy default) This makes self-hosting unnecessarily difficult, as users expect the open-source version to be fully functional without any subscription prompts.