I’ve been tinkering with the NGINX/SSL addon for Hass.io, and I’m almost there. I still need local access to my install via the hassio.local address (because the router provided by my ISP is stupid), so was hoping I wouldn’t need to change the base URL of my install.
I can visit my install fine at https://myinstall.duckdns.org, but whenever I try to log in Chrome says it is unable to connect to the wss:// address.
WebSocket connection to 'wss://myinstall.duckdns.org/api/websocket?latest' failed: Error in connection establishment: net::ERR_NOT_IMPLEMENTED
I’m stuck, so I’m asking for any pointers as to how I can resolve this.
As I am using Hass.io’s NGINX Proxy Add-on, I’m unsure as to how much modifications I can do, but seeing in the Github-repo, these are present in that config.
CloudFlare as my DNS provider (also provides some DDOS and other protection) for my external domain (in this example https://my_domain_name.com)
My internal subnet is 192.168.1.x
NGINX as my internal proxy running on a Raspberry PI 3 (on internal IP address 192.168.1.101) - also runs PI HOLE. NGINX is also my SSL termination for external users (home assistant running HTTP only)
HomeAssistant running on a Raspberry PI 3 (on internal address 192.168.1.38), using internal host header http://home.lan.
My HTTP config (in HomeAssistant configuration.yaml) is:
http:
# Allow all
server_host: 0.0.0.0
# Allow these host headers for CORS reqests
cors_allowed_origins:
- http://home.lan
- http://my_domain_name.com
- https://my_domain_name.com
# Enable parsing of the X-Forwarded-For header to pass
# correct client IP when proxied
use_x_forwarded_for: true
# The proxies that are permitted to process requests
# sent to home assistant
trusted_proxies:
- 192.168.1.101
# Enable IP banning
ip_ban_enabled: true
# Ban login attempts threshold
login_attempts_threshold: 5