Can't access HA after migrating to Proxmox

Hi, I have been using HAOS on a Raspberry pi for several years, and would access it normally using DuckDNS, e.g. mydomain.duckdns.org

I recently setup a new mini PC with Proxmox and installed HAOS using the helper script, then restored from my last backup from the Raspberry pi. This is also on a new network & router.

I am unable to access the HA web interface by local IP or the duckdns URL, and not sure how to proceed.

I know that HA is running because I started getting push notifications from some automations of mine.
When I go to the duckdns URL I get a “Loading data” spinner with the HA logo so it seems like it’s partially working, but eventually it times out.

I see in Proxmox that the HA VM has an IP, and from another computer on the same network I can successfully ping that IP as well as homeassistant.local.

nmap from the proxmox shell shows that 8123 should be open:

PORT     STATE SERVICE
8123/tcp open  polipo

I unfortunately don’t really remember how I had setup SSL/external URL before so I’m unsure what to try to undo/reset in order to be able to access by local IP even, any suggestions/advice welcome :slight_smile:

I tried using a VM in Proxmox and installed HAOS on it once… one of the issues I had was that HAOS didn’t seem to pick up the external network interface IP I had assigned it from Proxmox. I forget what the commands are, but you should look up what the HAOS CLI commands are to show the IP address that HAOS is using - if it’s different, you’ll need to change it.

You can not connect to it, but it can send notifications?

It sounds like you have set up a NAT routed network instead of a bridged network.

Thanks - I realized that on my previous router I had forwarded ports for HA. With my new router & ISP it doesn’t seem to work, trying to figure out why.

In the meantime I was able to get local access by disabling SSL in configuration.yaml from the cli

Check your Proxmox firewall config too - just in case it’s not your router blocking things. You could also try (very briefly, since it’s a bit risky) putting the VM’s IP in to your router’s DMZ just to see if that lets you access it externally.

Turns out my ISP is using NAT so port forwarding doesn’t work for me anymore.

Set up a Cloudflare tunnel and it’s working well now (though I need to go and update the domain everywhere)