HA behind NGINX Reverse Proxy, Lets Encrypt Issue

Configuration
1

Hey,
I’ve been trying to set up Lets Encrypt via DuckDNS for a day but having a few issues with my custom domain. Duck DNS is working and gets it’s cert fine, the http challenge fails for my domain and DNS updating doesn’t seem to work.

I think the issue is that my HA instance (HASSIO, Supervisor Install) is on Unraid Docker, so the port is always 8123. I have port forwarded 80 & 443 temporarily to HA port 8123 to get the certs issued. Duck DNS goes through my domain doesn’t. Both domains are routable in a browser.

When i then try to put HA back behind the reverse proxy the duck dns domain stop working also.
I figure i have a mismatch somewhere but can’t work it out.

I get a 502 bad gateway when hitting the duck dns URL now, i suspect because on the reverse proxy i have entered https:://ip:8123 rather than the base URL of the duckdns domain. But i can’t change that, that i know of. HA was installed via Supervisor so it doesn’t look like i have control of the port number. It remains open and working on 8123, but this mismatch between the reverse proxy and HA seems to be breaking things.

Any feedback or thoughts would be much appreciated.
Using the GUI NGinx Proxy Manager as a standalone docker instance, so can’t post a config file, it is also not nginx within HA.

Can i set alias base url addresses?

Oli

2

Your port forwarding should be

  • outside 80 to 80 on the machine ip address with nginx
  • outside 443 to 443 on the machine ip address with nginx

Then in your nginx proxy manager, your duckdns url should be forwarding to HTTP 8123 on your machine with homeassistant.

(It’s fine if they’re all on the same machine)

Set the checkbox in nginx proxy manager to upgrade all connections to ssl.