SSL on Home Assistant with Nginx Proxy Manager on Unraid server

Hello,

At this moment I am trying to get my HomeAssistant on HTTPS, but I can’t get it working. My setup is a little bit different then others, so I have searched alot but cannot find the answer.

My setup:

  • Home Assistant on a Raspberry Pi
  • Nginx Proxy Manager with Let’s Encrypt on an Unraid server
  • My own domain (instead of duckdns)

What I have done:

  • Port forwarding: 443 -> 8123. 8123 -> 8123 (to RPI)
  • Created a certificate with Let’s Encrypt in Nginx Proxy Manager
  • Created a subdomain for HA

What is working:

I think I am missing the configuration part, but I don’t know where to begin, because the certificate is not on the Raspberry Pi (refer to: ssl_certificate: /ssl/fullchain.pem and ssl_key: /ssl/privkey.pem).

I alreadyhave forwarded port 80 to my Unraid server, so I am really confused and don’t know where to begin.

Does anyone the magic trick to get this working? :smile:

Greetings,

Melvin

Why? You need to forward 443 to 443 of the NGINX machine and NGINX handles the routing to the correct IP and port.
In NGINX you configure which of your internal services will be called when you hit https://subdomain.domain.com

Ok, I removed that. I already have forwarded 443 to 443 of the NGINX machine, so that is working well.

But the problem is still going on :slight_smile: .

Then please show your NGINX config.

Phuu, I have no experience with a UI configuration for NGINX, sorry.

But what I notice is that you use https for the as a scheme. Are you able to acces home assistant locally through ssl? Does https://192.168.1.30:8123 work? If not, you could try changing it to http and see if that works.

Wow, that did the trick! Everything is working fine now! I am now able to open HA with https://subdomain.domain.com!

Thanks @Burningstone!

1 Like

Hi there, i will need some help please, i learned from you about the nginxproxymanager thanks.
i have it installed in my unraid, I have a domain that i am able to access to my hassio like
subdomain.domain.com:8123 i set up my nginxproxymanage just like you have it
http then my local ip then 8123. i set up my router port forwarding port 443 to 18443 and 80 to 1880 and 8123 to 8123. i am missing anything? i can access my hassio with subdomain.domain.com

And what exactly is your problem?

trying to get my hassio on https.
first I tried editing config file with:
http: base_url: https://mysubdomain.duckdns.org ssl_certificate: /ssl/fullchain.pem ssl_key: /ssl/privkey.pem
did work
I tried editing Let encrypt nginx docker and didn’t work
I found this post using Nginx manager and I am trying to make it work

The term hass.io has been deprecated around 6 months ago. The base_url option has also been deprecated for quite some time. Please also format your code correctly, we can’t see if you have a indentation error.
Do the certificates exist? Have you forwarded port 443 from your router to port 443 on the machine running NGINX? Please show your NGINX Proxy Managrr settings.

This is all the port I forwarded
External Port Internal Port

443 18443
443 8123
8123 8123
80 1880
I don’t know what you mean with Do the certificates exist? i can access hassio with http://mysubdomain.domain.com:8123 but i can’t with https

Capture

i finally getting working, wrong port forwarding set up

Would love to see this up w/my Google wifi router.

My home assistant instance is using a VM on my unRAID server. I utilize port 8123.

When I go to port management on my router setting internal port 80 to external port 80, doesn’t open the port. But when I set internal 8123 to external 80, the port is open. Same can be said for port 443.

I contacted my isp (FiOS) and they do not block opening ports.

When I follow the nginx add-on instructions and click on my duckdns subdomain I’m trying to link, I get a bad request error.

What am I doing wrong? in the nginx ui for setup, did switching it to http instead of https solve it for you? i see your ports on the previous ports, but are all those necessary to open?