-
Notifications
You must be signed in to change notification settings - Fork 97
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No Remote Access with SSL/Proxy #344
Comments
@willsanderson I have ha-fusion running and can access mine via duckdns & nginx proxy with no issues. I've attached images showing it working via the proxy and what I have in my config. I'm running 2014.1.11 if that helps |
How are you able to add "hass_url" in the Fusion options? I see Network options and only the ability to change the port. I am running the latest 2024.1.11 build as well. |
To add to the above; The webpage also briefly loads before it is redirected to the authentication URL mentioned in the post above. This could be a privacy issue. |
I ended up deploying ha-fusion on my k8s cluster instead of using the ha addon because of this issue. My HA instance listens on http, haproxy on the router terminates HTTPS between homeassistant and the internet. Eg, inside the LAN, homeassistant can be accessed at http://10.1.2.3:8123. When I access hafusion as addon and expose a port, eg http://10.1.2.3:8124 - this works fine I think expressjs needs some special parameters to accept X-Forwarded-* headers. In theory, with reverse proxy enabled in express, adding X-Forwarded-Proto=https to requests routed through haproxy would trigger |
Any fix for this issue.. I am using NGINX proxy with duckdns. Fusion dashboard can't connect wss of hass. |
Unable to access Fusion dashboard remotely (using NGINX Home Assistant SSL proxy with Duck DNS.). Currently receiving error in Fusion logs showing attempted connections using http instead of https. Screenshots with details below:
Fusion Logs:
Browser details:
The text was updated successfully, but these errors were encountered: