What the reverse proxy is
The panel's Reverse Proxy section lets you publish an internal service (for example, a web application running on a server in the network) so it is reachable through a web address, with FiveGuardian5 access control in front of it. The internal service does not need to be exposed directly to the internet.
It is useful when certain people need to use an internal application from a browser without connecting a whole device to the network.
Before using it
Enabling the reverse proxy in the service, bringing your own proxy and publishing from the command line are infrastructure settings managed by the FiveGuardian5 team. If you need any of them, request it through Support.
Authentication
A published service must require people to authenticate before reaching the application. Whenever possible:
- Require sign-in with the company account through the configured identity provider.
- Limit access to the groups that truly need it.
- Do not publish services without authentication, even if the application has its own sign-in.
Domains and access logs
Published services are reached through a domain name. Using custom domains requires DNS and certificate configuration coordinated by the FiveGuardian5 team.
Access to published services generates logs that help you know who used the service and when. Review them periodically, just like activity events.
Common problems
- The service does not respond: check that the internal server is running and that the device hosting it is connected under Peers.
- The user cannot get in: confirm they belong to an authorized group and are signing in with their company account.
- Certificate or domain errors: contact Support; do not ask users to ignore browser warnings.
If your case does not require browser access, consider instead granting access through Networks, which keeps the service inside the private network only.