Cannot access via NGINX on port other than 443

Configuration
,
#1

Hi all

I am accessing my Home Assistant via a DDNS, which works just fine. However, the Nuki lock seems to have issues with connecting via https, which is why I want to switch my local environment to http. Using DDNS + Let’s Encrypt does not allow for that, as it only accepts https connections.

In comes NGINX. Setting it up on port 443 works fine. But: My port 443 is already in use and I want to run NGINX on a different port. Say 4433. As soon as I set it up that way, access is no longer possible.
There’s no error message or anything, the browser just keeps loading for a long time and then tells me that the site I am looking for cannot be reached.

Using Home Assistant OS
NGINX Home Assistant SSL proxy version 3.1.5

I followed the add-on documentation to the dot. As mentioned, it works fine with port 443.

This is my add-on config:

domain: my.domain.com
hsts: max-age=31536000; includeSubDomains
certfile: fullchain.pem
keyfile: privkey.pem
cloudflare: false
customize:
  active: false
  default: nginx_proxy_default*.conf
  servers: nginx_proxy/*.conf

In the Network section I changed from 443/tcp to 4433

Let’s Encrypt is taking care of the certificates

This is the addition to config.yaml

http:
  #ssl_certificate: /ssl/fullchain.pem
  #ssl_key: /ssl/privkey.pem
  use_x_forwarded_for: true
  trusted_proxies:
    - 172.30.33.0/24

Can anybody help me out to resolve this issue? Why does it suddenly not work anymore when I switch from 443 to 4433?
I feel like I’m missing something super obvious here…

#2

oh, and of course there’s also a port forward for TCP from 4433 to homeassistantIP:4433

#3

Turns out this was completely my bad…
I am using my ISPs router in Bridge mode (cannot be circumvented) and then using Google WiFi for my actual network.

I forwarded the ports on my Google WiFi, but not on my ISPs router. Turns out both is needed and this immediately fixes the issue.