A few days ago I noticed that I was not able to login to my HASSIO with Chrome.
I have trusted network set correctly, but if I choose a user and move onto the next step, all I get is the HA logo with a “retry” link.
The same happens if I try to use the legacy API password.
From the browser’s console I notice there are some things going on related to SSL:
WebSocket connection to 'wss://xxx.xxx.xxx.xxx:8123/api/websocket' failed: Error in connection establishment: net::ERR_CERT_COMMON_NAME_INVALID e @ core.2755f59a.js:1 lovelace:1 Uncaught (in promise) 1 app.a9501bd7.js:20473 Uncaught (in promise) DOMException: Failed to register a ServiceWorker for scope ('https://xxx.xxx.xxx.xxx:8123/') with script ('https://xxx.xxx.xxx.xxx:8123/service_worker.js'): An SSL certificate error occurred when fetching the script.
But this problem does not happen if I login with my duckdns.org dynamic DNS name (although I can only use the legacy API password, as the public IP is not recognized as a trusted network for individual users to login).
Nonetheless, if I use Firefox, I can login without any hassle, so I was wondering if there are any recent changes to Chrome that may prevent logging in to HASSIO (for all due purposes, the SSL certificate is issued to my duckdns name and not to my local IP).