Cyberdise can be operated in a network that has no direct route to the internet and reaches it only through an HTTP proxy. When a proxy is configured, every outbound component of the product uses it: the API clients, the file downloads and the headless browser that renders landing pages.
The proxy is a system-wide setting, stored once for the whole instance and applied to every realm. A tenant or realm operator can neither see nor change it.
Where the settings are
Sign in as a SuperAdmin on the system domain and open Settings → Proxy Settings.
The fields
| Field | Meaning |
|---|---|
| Enable proxy | Master switch. With it off, Cyberdise connects directly, exactly as before this feature existed |
| HTTP proxy URL | Required once the proxy is enabled, for example http://proxy.example.com:3128
|
| HTTPS proxy URL (optional) | A separate proxy for HTTPS. Leave it empty to send HTTPS through the HTTP proxy |
| Excluded from proxy | Comma-separated hosts that must be reached directly, for example localhost,127.0.0.1
|
| Verify SSL certificates | Whether certificates are validated on proxied connections |
How the two URL fields combine
- Both set — HTTP and HTTPS each go through their own proxy. Use this when your TLS
proxy is a separate host.
- Only the HTTP proxy set — HTTPS falls back to the same proxy. This is the usual case.
- Only the HTTPS proxy set — HTTPS is proxied and plain HTTP stays direct.
- Enabled, but both empty — treated as no proxy. Cyberdise will not send requests into
an empty proxy address.
- Disabled — no proxy settings are applied anywhere, and behaviour is identical to an
installation that never had the feature.
The exclusion list
Fill Excluded from proxy with the hosts that live inside your network — your mail server, your domain controller, an internal license or update mirror. localhost and 127.0.0.1 belong there in nearly every deployment. An empty list is not passed to the outbound clients, so leaving it empty is safe.
Proxy authentication
If the proxy requires credentials, include them in the URL: http://user:password@proxy.example.com:3128. The credentials are stored with the setting, so treat screenshots of this page as sensitive.
TLS interception
If your proxy terminates and re-issues TLS, its certificate authority must be trusted by Cyberdise, otherwise proxied requests fail with certificate errors. Either install the CA in the container's trust store, or — for a lab only — turn Verify SSL certificates off.
Turning off certificate validation makes outbound traffic vulnerable to tampering. Install the proxy CA instead of disabling the check on a production system.
Verifying
Use Test connection on the same page: it reports whether Cyberdise can reach the internet through the configured proxy. Save first, then test.
Follow it with an end-to-end check that exercises a different client — run a license check, or send a test message and open a landing page so the headless browser is used too.
Comments
0 comments
Article is closed for comments.