#Nginx Proxy Manager ip change

1 messages · Page 1 of 1 (latest)

sharp marsh
#

I had Nginx proxy manger, duckdns and router port forwarding all set to handle https traffic into my home assistant (HA) server setup on a raspberry pi 5 server. It was all working for some time until I had to change internet provider and local ip address of my home assistant server(192.168.xx.xx). I made the following changes but still does not work and appears to not find my local home assistant through my domain and https.

  1. Updated the local ip address to HA ip address in nginx proxy manager Host destination ip => http://192.168.xx.xx:8123
  2. Updated my router to port forward external 443 tcp to 443 internal port to new local HA ip 192.168.xx.xx
  3. Updated HA Settings -> System -> Network -> update Local network ip to new local http://192.168.xx.xx:8123

My domain is resolving to the new internet provider ip on my new router. Nothing in logs of nginx. In browser dev tools during a call to my home assistant using https:/www.domain the original call never finishes, but it appears some JS files are downloaded from my HA server. This is the first call to fail: https://mydomain.duckdns.org/lovelace (Failed to load response data-no data found for resource with given identifier) Using a the local ip internally without https the HA works fine. I saw no place in my configuration.yaml that the old HA local ip was used.

Any ideas what I can check?

#

Here is my current configuratiion setup for http
http: use_x_forwarded_for: true trusted_proxies: - 172.30.33.0/24

abstract glacier
#

Hi there, did you forward it to https? and not http

astral stag
sharp marsh
#

Thanks for input... I checked my 443 port on above site and it is open. I also double check my port forward and I entered below 443 to my HA.
Device: Custom IP
IP address: 192.168.xx.xx (ip address of my HA)
Service: HTTPS
Internal Port: 443
External Port: 443
Protocol: TCP

abstract glacier
#

What about dns server on router(s)? Is it pointing to NPM?

sharp marsh
#

Yes, when I tracert my dns, it routes to the ip address of my router at the new provider.
This really has me stumped. I had it working for months on my old provider and original local ip. I keep thinking it has to be something with the new provider and router since that is only change other than the local ip and that should not really affect things since I updated my proxy and firewall with new ip address.

sharp marsh
#

It has always made it to the server with the following message after the provider and local ip change.

Unable to connect to Home Assistant.

Retrying in 52 seconds...

The dev tools show the url as
https://myDomainName.duckdns.org/
So it appears to be making it to my server, but it quickly errors out on this call and several others after
https://myDomainName.duckdns.org/hacsfiles/lovelace-card-mod/card-mod.js
failed to load response data.
https://myDomainName.duckdns.org/auth/token
failed to load response data.