Connection Diagnostics
Why sign-in works but pages fail to load — checked from the machine running Plantwin, not from your browser. No sign-in required.
Backend connectivity
Checked from the machine running Plantwin, not from your browser
Signing in happens directly between your browser and the backend. Everything after that — dashboards, the admin panel, reports — is verified by the application server process on this machine, which needs its own outbound HTTPS access to the same host.
What a restricted network must allow
On-premise / plant installations
1. Outbound HTTPS. The machine running Plantwin needs TCP 443 to the backend host shown above. Allowing only the browser is not enough — the server process makes its own calls.
2. TLS inspection. If your network intercepts HTTPS, start the app with NODE_EXTRA_CA_CERTS pointing at the corporate root certificate, and set HTTPS_PROXY if a proxy is mandatory — the server process does not read Windows proxy settings automatically.
3. Clock. Session tokens are time-based. Keep the machine synced to an NTP source; more than a minute of drift invalidates every session.
4. Historian access is separate. The PHD REST endpoint or Windows bridge stays entirely on your plant network — see PHD connection & cache.