Native HTTPS Support / SSL for the PatchMon web server
In our case, PatchMon communicates with Nginx Proxy Manager over an unencrypted HTTP connection (default port 3000). While HTTPS is available for external client access via Nginx Proxy Manager, the backend connection between Nginx Proxy Manager and PatchMon remains unencrypted.
For corporate environments with strict security or compliance requirements, all internal traffic must also be encrypted. This currently prevents us from deploying PatchMon.
It would be very helpful if PatchMon supported HTTPS for the backend connection, allowing Nginx Proxy Manager to communicate with PatchMon over TLS (e.g., port 443 or another configurable HTTPS port). Ideally, this should also support self-signed certificates or custom CA certificates for internal deployments.
Suggested functionality:
- Native HTTPS support for the PatchMon web server.
- Configurable HTTP/HTTPS ports.
- Support for self-signed and custom TLS certificates.
- Documentation describing the recommended configuration with reverse proxies such as Nginx Proxy Manager.
Use case:
Many organizations require encryption for all network traffic, including communication between reverse proxies and backend services. Supporting HTTPS for the PatchMon backend would improve security, simplify compliance with internal security policies, and make PatchMon suitable for more enterprise environments.
3 Comments
This would be nice. That way, it would finally be possible to use encryption internally without even needing a proxy.
I fully support this fearure and agree this is also our own corporate security requirements. But this should add the functionalitynot replace the current solution 3000 port solution. Many people within docker front end patchmon with a reverse proxy that is within a docker network with no external facing open ports so adding an SSL requirement in that case would make little sense.
Feature to use self signed certificates is here too