You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like the official NGINX Home Assistant SSL Proxy add-on to allow HTTP on port 80 without automatic HTTPS redirection. Currently, port 80 is hardcoded to redirect all traffic to HTTPS, even though the add-on already supports additional custom HTTP ports. The enhancement would let users optionally serve Home Assistant via plain HTTP on the standard port 80, while keeping the existing HTTPS functionality unchanged.
Use cases
Users may want Home Assistant accessible via standard HTTP (:80) for local network devices, legacy clients, or testing purposes.
Useful for setups with self-signed certificates, where the root CA cannot be installed everywhere; in these cases, plain HTTP avoids certificate warnings.
Avoids having to remember or specify a non-standard port for HTTP.
Provides more flexible network configurations while retaining secure HTTPS access on port 443.
Upstream project
No response
Anything else?
Existing community add-ons, like NGINX Proxy Manager, allow full HTTP configuration, but the official add-on is preferred for seamless Home Assistant integration. Maintenance could be simple: add an http_enable_on_80: true/false option to control whether port 80 is redirected or serves HTTP directly.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
What type of request is this?
Enhancement to existing add-on
Existing add-on name
NGINX Home Assistant SSL proxy
Describe the add-on or add-on enhancement
I would like the official NGINX Home Assistant SSL Proxy add-on to allow HTTP on port 80 without automatic HTTPS redirection. Currently, port 80 is hardcoded to redirect all traffic to HTTPS, even though the add-on already supports additional custom HTTP ports. The enhancement would let users optionally serve Home Assistant via plain HTTP on the standard port 80, while keeping the existing HTTPS functionality unchanged.
Use cases
Upstream project
No response
Anything else?
Existing community add-ons, like NGINX Proxy Manager, allow full HTTP configuration, but the official add-on is preferred for seamless Home Assistant integration.
Maintenance could be simple: add an http_enable_on_80: true/false option to control whether port 80 is redirected or serves HTTP directly.
Beta Was this translation helpful? Give feedback.
All reactions