Hello guys… I’m here to ask your help… I already checked other threads but I haven’t resolved my problem…
I have a Synology NAS and I have installed on it docker with an homeassistant container running in http without ssl certificate.
I have enabled a reverse proxy on my public DNS (example: https://ciquattro:8888 to http://10.10.10.200:8123 ) and it work… but when I’ll try to login to the HASS with the login password I’m not able to login… don’t know why… anyone have the same problem?
Here’s the solution
topic can be closed… thanks
Hi @Ciquattro,
I haved configured proxy-reverse in my synology, and when i write: https://ha.mydomain.com i see the main HA website where i need to put password.
Once i put the password, after few seconds, appears me a message that says: Unable to connect.
If i access to my HA in local network http://IP:8123 and i put password i enter.
Did you hav the same problem? Did you resolved with the link you added?
Thanks
I had the same proble… you need to follow this link for resolve your issue:
you need to ssh on your synology and change the portal.mustache and add these lines as described in the link:
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection “upgrade”;
proxy_read_timeout 86400;
no issue at all… you need to do this steps on every Synology update that replace the portal.mustache file.
Good news: I just got the information that customized headers for Reverse Proxy will be supported in DSM 6.2.1, which is expected to be released in late August or early September. Finally no more fiddling around after each DSM update!
I created a support ticket and got that as an answer.
that’s awesome
what settings do you use to make this work?
This has been live for me for some time, but I’m currently running build DSM 6.2.1-32824 Update 1.
You can set it by going to Control Panel > Application Portal > Reverse Proxy > Create and then select your Source/Destination entry > Edit > Custom Header > Down Carrot next to “Create” > WebSocket
This should add two Header Name & Value entries (“Upgrade $http_upgrade” and “Connection $connection_upgrade”). After this option became available, I no longer had to SSH into the device to allow the https redirect work correctly.