Recently jumped a few revs to 0.95.4 and when trying to access my server from remote I can’t get past a “Initializing” screen. I’ve tried clearing cookies, different browsers, all that jazz.
My setup is using nginx and forwarding to HA, i’m using my own SSL valid certs etc. The nginx conf looks like,
map $http_upgrade $connection_upgrade {
default upgrade;
'' close;
}
server {
server_name homepants.net www.homepants.net;
listen [::]:443 ssl default_server ipv6only=off;
add_header Strict-Transport-Security "max-age=31536000; includeSubdomains";
ssl on;
ssl_certificate /etc/nginx/ssl/homepants_net/ssl-bundle.crt;
ssl_certificate_key /etc/nginx/ssl/homepants_net/homepants_net.key;
ssl_prefer_server_ciphers on;
ssl_session_cache shared:SSL:10m;
proxy_buffering off;
ssl_trusted_certificate /etc/nginx/ssl/homepants_net/ssl-bundle.crt;
error_page 502 /error-502.html;
location = /error-502.html {
internal;
root /var/www/html;
}
location / {
proxy_pass http://192.168.86.250:8123;
proxy_set_header Host $host;
proxy_redirect http:// https://;
proxy_http_version 1.1;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $connection_upgrade;
}
location /api/websocket {
proxy_pass http://192.168.86.250:8123/api/websocket;
proxy_set_header Host $host;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
I’ve went through hass configuration.yaml and fixed all the warnings, the connection config information looks like,
homeassistant:
customize: !include customize.yaml
name: Home
latitude: 37.7647679
longitude: -122.456229
elevation: 122
unit_system: imperial
time_zone: America/Los_Angeles
auth_providers:
- type: trusted_networks
trusted_networks:
- 192.168.86.0/24
- type: legacy_api_password
api_password: !secret http_password
http:
base_url: http://192.168.86.250:8123
cors_allowed_origins:
- https://google.com
- https://home-assistant.io
use_x_forwarded_for: True
trusted_proxies:
- 192.168.86.0/24
- 155.64.38.0/24
This is really a bugger, any insight on what I’m missing? From what I know of OAuth maybe there is something to do w/ redirects? I dunno… and I’m not doing anything crazy, surprised more peeps aren’t encountering this.