You can access it locally without https and externally with https using your DDNS. That is the magic of NGINX. Have you port forwarded 443 to 443 Hassio?
I have got 443 forwarded in the router.
Additionally, I tried clearing the browser cache and got this error in firefox:
Error code: SSL_ERROR_RX_RECORD_TOO_LONG
And just to confirm - I can now access locally, but I cannot access it externally using https://
Have you tried to recreate the certificates? Try restarting or even reinstalling DuckDns addon.
You also need to forward 80 to 80 Hassio for certificate renewal.
Here works just fine.
I have time to have another blast at getting nginx going today. I’m still running into problems though in that I cannot now access hassio remotely (https).
What I have done:
Removed these lines from my configuration.yaml:
# ssl_certificate: /ssl/fullchain.pem
# ssl_key: /ssl/privkey.pem
Reinstalled duckdns, which has regenned my ssl certs
changed my port forwarding to the following:
installed nginx and configured as:
{
“domain”: “yourddns.duckdns.org”,
“certfile”: “fullchain.pem”,
“keyfile”: “privkey.pem”,
“hsts”: “max-age=31536000; includeSubDomains”,
“customize”: {
“active”: false,
“default”: “nginx_proxy_default*.conf”,
“servers”: “nginx_proxy/*.conf”
}
}
tooka ages to start - but eventually did.
when I try to access hass using my external IP (https://myhassio.duckdns.org) I get the following:
“Unable to connect to Home Assistant. Retry”
also - my log is filled with this:
Log Details (ERROR)
Mon Jan 21 2019 11:45:14 GMT+0000 (Greenwich Mean Time)
Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.6/site-packages/aiohttp/web_protocol.py", line 263, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
File "aiohttp\_http_parser.pyx", line 523, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: invalid HTTP method
Anyone have any ideas?
I have the same issue here, ended up going back to original config without nginx…
Has this been resolved?
Having a flood of this error