Unable to connect to HA after recreating docker on Synology

Installation
1

So by mistake I deleted my HA docker on synology. Didn’t have a backup

I recreated it with the following

  1. Volume - Mapped /config to the folder which exists
  2. Port - Mapped as host
  3. Environment - Just added TZ Variable

I start the docker and it starts fine. No error in logs

But

When I try to connect (I had duckdns configured for it) it simply spins on connecting and errors “Unable to connect” at password screen
When using internal IP HTTPS and HTTP I get ERR_CONNECTION_REFUSED on Chrome

I believe I am missing some environment variable for the config but can’t seem to recall. Any help?

My configuration.yaml has http configured with api_password (Tried disabling it as well - same issue), base_url, ssl_certificate and ssl_keys

No files were affected as I simply deleted the docker by mistake. The drive files remained intact.

2

Any help guys?

3

Try to add an excepction in your browser if this don’t fix it I think the cert files must be brocken for your current set up. Try to renew them with current setup.

4

How is port forwarding setup on your router?

Can you get into hass from outside you LAN? (try your cell connection)

Could this a be a NAT reflection issue?

What might be happening is your try to hit hass by it’s “subdomain.duckdns.org” address. that request has to leave your network to whoever you have set to resolve DNS for you, then it comes back in at your WAN address. If ports are not forwarded to the host with hass on it then it stops there. Another thing is your may need to append the URL with “:8123” so that if you are taking that round trip and coming back in, the host knows what port you are trying to hit (the one that hass is served on). Now if you can do NAT reflection then it should just resolve right to to host machine while staying in the LAN. This may have more to do with how your have your network and DNS setup than anything.

5

Cert is fine… Expires end of Oct … Thanks

Interesting… I have not changed it but its not working even on 4G

But I am wondering if I had missed a configuration in settings of the docker which might have broken it.

Other ports are working… Just the port reflecting HA isin’t (internally or externally)

I still believe something might be missing in my docker setup (TZ has a value)

image
image1310×1108 55.9 KB

6

Actually it’s something very basic… The port 8123 is not even showing open on NAS (netstat)… The docker should open it up simply right? or missing the port config on top?

Nothing in the home-assistant.log as well

EDIT: So found the problem (not the solution)… Commented out all my SSL related stuff in config and basic port is working now… Will see what is missing for my SSL config

EDIT2: Solved. So when I recreated the docker - i forgot to map the SSL Certificate location as it was in a different folder and HA couldn’t find it

Thanks everyone!!!

7

There it was. Good job finding the simple error and getting it working again.

Also the TZ setting is only to put error logs in local time instead of UTC. Don’t hold me to that though.