I'm getting the ssl certificate error. The nabu casa page says the remote address is unavailable. I can't login at all to try and reboot it. It also won't login on a desktop or phone. It is haos on a pi5 (with pironman case and m.2 ssd) It's been working for quite a long time and I haven't changed any settings on any of the devices or routers.
#Can't connect to home assistant
glad wharf
When I search for the server (where it says to add a new one) it doesn't find it automatically or if i enter the remote ui url or the homeassistant.local:8123.
tough blade
Have you tried to login on Nabu-Casa ?
I've tried that since yesterday and always get the answer "Could not login, try later"
glad wharf
Yes. I can login to nabu casa. But it says no remote address
mighty ridge
Your HA server has to:
- be accessible locally in a browser
- connect out to the internet and specifically the Nabu Casa snitun server as the first step in the connection
You see an ssl error because your server isn't available.
glad wharf
It will not connect locally. Yes. It doesn't connect to the CLI. Any tips to get it connected.
mighty ridge
It will not connect locally. Yes. It doesn't connect to the CLI. Any tips to ge...
You can connect a keyboard and monitor to access the console and check logs
glad wharf
Is there anyway to recover it? Sorry fir the delayed reply. I don't get alot of free time. But appreciate any help or replies.
glad wharf
Even when I connect the pi5 to my laptop with ethernet it still says can't reach this page
glad wharf
This is what i have. Typing login doesn't work either.
glad wharf
I started the homeassistant and HASSio containers and i can now log on the web. Supervisor wont start or connect to nabu casa remotely. It says the instance is not connected
mighty ridge
you were already at the host console, but the custom HA cli/console was not loading. That should be the first thing you see after the boot is complete, with the welcome screen showing ip addresses, etc.
This could be fine if the HA CLI eventually starts but it could indicate an issue.
from the host console with the #, you can enter the command docker ps which would show you all running containers.