Nuclos external access: HTTPS NAT, reverse proxy, VPN, OpenVPN, port 443, security, remote access. |
Language: Deutsch · English
Provide Nuclos externally – HTTPS/NAT, reverse proxy or VPN compared with pros and cons.
On this page |
There are three methods to make a Nuclos instance available externally.
Port 443 is forwarded to the Nuclos server via NAT; HTTPS must be configured in Nuclos. A different port is possible (then always specify it, e.g. https://nuclos.company.tld:8443).
| Advantages | Disadvantages |
|---|---|
| Simple configuration, no extra hardware. | Tomcat start page reachable externally; HTTPS port occupied by a single application. |
Port 443 is routed to the reverse proxy, which filters and forwards requests. This allows addressing several instances via different (sub)domains – ideal when port 443 is already taken (see reverse proxy configuration).
| Advantages | Disadvantages |
|---|---|
| Multiple applications on one port; distinction via subdomain; no VPN client needed. | Extra VM/hardware; more demanding configuration. |
Users establish a VPN connection and access encrypted just like internally. With correct configuration the highest security level; without a VPN router an OpenVPN server on the Nuclos server suffices.
| Advantages | Disadvantages |
|---|---|
| Highest security level; no change for employees; full network access if needed. | A VPN client must be installed. |
Access via HTTP (unencrypted) should never be used for external connections. |