HA doesn't connect remotely since provider update

Hi All,

I’m at a bit of a loss as to what is happening here with HA not connecting remotely after having upgraded the connection and moved across to another provider. So the previous configuration was as follows:

  • NBN connection to UDM Pro via provider 1
  • DNS configured to point to the allocated IP address
  • Port forwarded to NGINX (using a proper certificate)
  • Redirected to the HA box

Now, my only change was to have the NBN fibre installed (FTTP) and pluigged into another port on the UDM, configured DNS to point at the new IP address and was able to resolve correctly on the new provider.

Now I’m finding that I seem to be able to hit the HA server in some respects as the HA logo comes up with the message “Unable to connect to Home Assistant”

Confusing as there are no changes to the HA config and the issue seems to be beyond the router.

Thanks,
Paul

The HA logo is probably cached. Does your new provider use CG-NAT?

Checked, yes they do implement cgnat

Currently 37 in queue to have it disabled :stuck_out_tongue_closed_eyes:

So there’s your issue.

Will see, still not able to connect however I’ll check it tomorrow when I have a minute. I was supposed to have been disabled, and I’ve restarted the modem as requested so hopefully it’s just taking its sweet time.

OK, all issues resolved . . .

  1. I didn’t realise that CG-NAT was configured to a specific IP address range that changes when disabled. Fixed by updating DNS.

  2. It was advised that incoming ports were not blocked however on checking it seemed they were, this can also be controlled via their web portal.