Nginx DuckDNS and Home Assistant Port Forwarding

Started by alfuth, November 14, 2025, 04:57:15 AM

Previous topic - Next topic
November 14, 2025, 04:57:15 AM Last Edit: November 14, 2025, 01:26:45 PM by alfuth
Hi All, I've followed the tutorial here: https://forum.opnsense.org/index.php?topic=24778.0

and found that I can access my Home Assistant by entering my Duckdns website (with the :8123 port at the end) from my home network, but when I try to access from my phone or even https://www.ssllabs.com/ssltest/ I get "took too long to respond" from my phone and "unable to connect to server" from ssl labs.

I figured it was a firewall problem because if, from my phone, I put in the xxx.duckdns.org:80 it times out immediately. However, when I go in to the firewall logs it shows no blocked access when I try to access it normally from my phone (without wifi).

So I have two questions:
1). following the tutorial while using duckdns.org, has anyone had any issues or see any issues with my results?
2). from my home network do I always have to access my duckdns.org website by adding the :8123 port at the end?

Any help is greatly appreciated, I've searched for days and tried many different things and cannot figure it out. Not getting any blocked or allowed access from my phone is very strange to me.

As a clarification, I do get a log showing blocked access from my phone (without WiFi) if I put in xxx.duckdns.org:8123 but no log that I can find if I access it via https (443). Also, I'm running OPNsense on a protectli firewall with the Nginx and Acme plugins, and the home assistant is running as a docker container on my home server using a MACVlan for networking.