Software - or Hardware Access Issue -?

KruseLuds · June 1, 2023, 4:55pm

I only have one possible (PITA - pain in the ass) solution to try for this and not sure if it will work, so here I am.

No longer a noob, running Hopme Assistant Supervised on a RPI 4 w/8Gig or Ram on a 1TB SSD (not even using any microsd). Tweaked to high heaven and working perfectly, running very cool with low CPU etc. All automations working no issue. I run headless and only use telnet to access the underlying OS. Installation is both supported and healthy, OS and all HA integrations as well as HACS addons and integrations all up to date. No network changes.

Today I am unable to access the HA UI - from a web browser or the Android HA App. I also cast the UI to a Google Home Nest Hub Max (or whatever that hardware is called, got it free from my ISP for switching to them). That display gives me an error message about the HA websocket API or something or other (as it has before whever there is an issue with HA which up until now was rare). Up until now has been working pretty much flawlessly for some months. No errors in the syslog, all automations still working fine - I just cannnot get to the HA front end! I can telnet to the machine.

I have tried a complete reboot and shutdown - power off, restart - also I have gone through these normal steps for the HA Supervised installation from here:

(but not replacing trhe OS, just the end stepos which has fixed my issues before):

re-download and reinstall all the required libraries
re-download and reinstall docker
re-download and reinstall the OS-agent
re-download and reinstall homeassistant-supervised.deb

and the same thing - it comes up and automations all work fine, i just still l cannot access the HA UI by any means (but can still telnet to the HA Debian 11 OS command prompt).

I do have another SSD which is an exact clone of the SSD I have been using. It was created by simply booting up the RPI on a Raspbian microsd card, then plugging both SSD’s into it and using the SD Card Copier app. The backup SSD has always worked perfectly when I shut down and restart the RPI with that one plugged in instead.

However, today, HA has the same UI access issue when running on the backup SSD instead!

I would think Ok I now have a hardware issue. But, the display is headless and access is through the network, and everything else on the network is working perfectly as well (automations,. etc.). Lastly, I have weewx running on the host outside of HA, reporting my weather station data to many websites all over the world (and I am using the ambientweather integration as wel, which is working perfectly still too). And those websites are all getting timely updates from my weather station via weewx runing on the RPI as well. So it seems not to be a hardware issue if it is related to networking.

I am thinking I can do my next attempt (the PITA attempt mentioned in the beginning of this message) reinstall everything from scratch (the OS, etc.) on one of the SSD’s and then if I can get into HA I can easily restore the HA config from a backup - but will that work - if the backup SSD which was working fine does not work either?

I use duckdns for access and went to their site, that seems to be up…

HALP! (Pulling out hair) Thoughts before I try the drastic starting from scratch (which might not work as the backup ssd doesn’t work)?

Thoughts?

dbs · June 2, 2023, 4:25am

Any chance that the UI port (8123 default) is now being blocked by something on your network or that there is a time issue that has messed up the certificate (if you’re using HTTPS)?

KruseLuds · June 2, 2023, 4:39am

Thank you for your help! As I am primarily self taught - I am not sure how to check either… Yes, I do use https. Both are possible. How do I check both?

WallyR · June 2, 2023, 9:40am

Try to do a netstat -ln on the Debian to see what ports are in use.

Also try to access the observer on port 4357 to see what it says.

KruseLuds · June 2, 2023, 1:14pm

sudo apt install net-tools

then:

pi@kruse-pi:~$ sudo netstat -ln
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State
tcp        0      0 0.0.0.0:5355            0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:8080            0.0.0.0:*               LISTEN
tcp        0      0 127.0.0.1:53            0.0.0.0:*               LISTEN
tcp        0      0 172.30.32.1:53          0.0.0.0:*               LISTEN
tcp        0      0 192.168.0.35:53         0.0.0.0:*               LISTEN
tcp        0      0 192.168.0.34:53         0.0.0.0:*               LISTEN
tcp        0      0 127.0.0.53:53           0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:1627            0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:8123            0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:8989            0.0.0.0:*               LISTEN
tcp        0      0 192.168.0.34:40000      0.0.0.0:*               LISTEN
tcp        0      0 192.168.0.35:40000      0.0.0.0:*               LISTEN
tcp        0      0 172.30.32.1:62369       0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:4357            0.0.0.0:*               LISTEN
tcp        0      0 127.0.0.1:45158         0.0.0.0:*               LISTEN
tcp6       0      0 :::5355                 :::*                    LISTEN
tcp6       0      0 ::1:53                  :::*                    LISTEN
tcp6       0      0 :::22                   :::*                    LISTEN
tcp6       0      0 :::1627                 :::*                    LISTEN
tcp6       0      0 :::8123                 :::*                    LISTEN
tcp6       0      0 fe80::e233:6f1:12:40000 :::*                    LISTEN
tcp6       0      0 :::4357                 :::*                    LISTEN
udp        0      0 0.0.0.0:56651           0.0.0.0:*
udp        0      0 0.0.0.0:48998           0.0.0.0:*
udp        0      0 0.0.0.0:40991           0.0.0.0:*
udp        0      0 127.0.0.1:53            0.0.0.0:*
udp        0      0 172.30.32.1:53          0.0.0.0:*
udp        0      0 192.168.0.35:53         0.0.0.0:*
udp        0      0 192.168.0.34:53         0.0.0.0:*
udp        0      0 127.0.0.53:53           0.0.0.0:*
udp        0      0 0.0.0.0:68              0.0.0.0:*
udp        0      0 0.0.0.0:32853           0.0.0.0:*
udp        0      0 0.0.0.0:41481           0.0.0.0:*
udp        0      0 192.168.0.34:5353       0.0.0.0:*
udp        0      0 172.30.32.1:5353        0.0.0.0:*
udp        0      0 0.0.0.0:5353            0.0.0.0:*
udp        0      0 0.0.0.0:5353            0.0.0.0:*
udp        0      0 0.0.0.0:5355            0.0.0.0:*
udp        0      0 0.0.0.0:5683            0.0.0.0:*
udp        0      0 0.0.0.0:34519           0.0.0.0:*
udp        0      0 239.255.255.250:1900    0.0.0.0:*
udp        0      0 0.0.0.0:1900            0.0.0.0:*
udp        0      0 0.0.0.0:1900            0.0.0.0:*
udp        0      0 0.0.0.0:1900            0.0.0.0:*
udp        0      0 0.0.0.0:1900            0.0.0.0:*
udp        0      0 0.0.0.0:55276           0.0.0.0:*
udp        0      0 0.0.0.0:38900           0.0.0.0:*
udp6       0      0 :::39514                :::*
udp6       0      0 :::44480                :::*
udp6       0      0 ::1:53                  :::*
udp6       0      0 :::5353                 :::*
udp6       0      0 :::5353                 :::*
udp6       0      0 fe80::e233:6f1:129:5353 :::*
udp6       0      0 :::5355                 :::*
udp6       0      0 :::1900                 :::*
udp6       0      0 :::1900                 :::*
udp6       0      0 :::35181                :::*
Active UNIX domain sockets (only servers)
Proto RefCnt Flags       Type       State         I-Node   Path
unix  2      [ ACC ]     STREAM     LISTENING     12854    /run/systemd/journal/io.systemd.journal
unix  2      [ ACC ]     STREAM     LISTENING     16283    /var/run/docker/metrics.sock
unix  2      [ ACC ]     STREAM     LISTENING     19217    /run/containerd/s/2f0d52ee5fc6c0f85586008929762afd30f67fac19dc0abea17deb878173f352
unix  2      [ ACC ]     STREAM     LISTENING     789988   /run/user/1000/systemd/private
unix  2      [ ACC ]     STREAM     LISTENING     789994   /run/user/1000/bus
unix  2      [ ACC ]     STREAM     LISTENING     789996   /run/user/1000/gnupg/S.dirmngr
unix  2      [ ACC ]     STREAM     LISTENING     789998   /run/user/1000/gnupg/S.gpg-agent.browser
unix  2      [ ACC ]     STREAM     LISTENING     790000   /run/user/1000/gnupg/S.gpg-agent.extra
unix  2      [ ACC ]     STREAM     LISTENING     790002   /run/user/1000/gnupg/S.gpg-agent.ssh
unix  2      [ ACC ]     STREAM     LISTENING     790004   /run/user/1000/gnupg/S.gpg-agent
unix  2      [ ACC ]     STREAM     LISTENING     4003     /var/run/docker/libnetwork/4342c0490abd.sock
unix  2      [ ACC ]     STREAM     LISTENING     19276    /run/containerd/s/9deb431c34d55e9ab43f10b1b3e504c0a396722d60d6ea347881242e1fd3e88d
unix  2      [ ACC ]     STREAM     LISTENING     22038    s
unix  2      [ ACC ]     STREAM     LISTENING     16592    /run/containerd/s/20878405365e2610f1250043af5dbbf1c6818bfab9babd7d279a8eff9d58e236
unix  2      [ ACC ]     STREAM     LISTENING     19376    /run/containerd/s/c1e5b97854a017cae63d81eb4eabe7a0e1589931137a6c5f07e524d6b653b633
unix  2      [ ACC ]     STREAM     LISTENING     21671    /run/containerd/s/e1dfa4b7dd4e367a4c7baa936107618500a3f10a29671e740fc6f99733287cfd
unix  2      [ ACC ]     STREAM     LISTENING     17527    /run/containerd/s/348307ad6b4a6e4119ba229687289e02f75894b1e4e2179c26b61460a8ad6d0c
unix  2      [ ACC ]     STREAM     LISTENING     21025    /run/containerd/s/d09996ab6b45281cb502f781caae33db5df1b540d6fc79a0b74b4f265988632a
unix  2      [ ACC ]     STREAM     LISTENING     14681    /run/systemd/resolve/io.systemd.Resolve
unix  2      [ ACC ]     STREAM     LISTENING     15616    /run/dbus/system_bus_socket
unix  2      [ ACC ]     STREAM     LISTENING     15618    /run/docker.sock
unix  2      [ ACC ]     STREAM     LISTENING     15620    /run/systemd-journal-gatewayd.sock
unix  2      [ ACC ]     STREAM     LISTENING     27918    /run/containerd/s/a951083fdf5d271bd3a5c9a871bd4576ca31b2436a720726b804cac0f5bf5869
unix  2      [ ACC ]     STREAM     LISTENING     18614    /run/containerd/s/f622e9a0c4109ba0b2b1736c4362184d0ae4e4ebf6d7023a0b8d7bd1ac0e52af
unix  2      [ ACC ]     STREAM     LISTENING     28030    /run/containerd/s/fc9021c52a8b66c9da1cae2b0bec1da6936c88edd40db342e71030b7a938b52b
unix  2      [ ACC ]     STREAM     LISTENING     17156    /run/containerd/s/5252d059b3ac9cd079fe5a5109372c9e3233d5275f30e71afbc2ebf3245df00e
unix  2      [ ACC ]     STREAM     LISTENING     19262    s
unix  2      [ ACC ]     STREAM     LISTENING     26448    /run/containerd/s/7d36e1a552cbfc16306f9c5aacdac9b591a715f5bcff0cb3fdd1e3a9b3d78afa
unix  2      [ ACC ]     STREAM     LISTENING     17240    /run/containerd/s/3b2a0e6fc66f22f05e8004f4ed620290abc6c4df84bf407a86f5cb0ffe65c604
unix  2      [ ACC ]     STREAM     LISTENING     12814    /run/systemd/private
unix  2      [ ACC ]     STREAM     LISTENING     12816    /run/systemd/userdb/io.systemd.DynamicUser
unix  2      [ ACC ]     STREAM     LISTENING     12817    /run/systemd/io.system.ManagedOOM
unix  2      [ ACC ]     STREAM     LISTENING     12827    /run/systemd/fsck.progress
unix  2      [ ACC ]     STREAM     LISTENING     12835    /run/systemd/journal/stdout
unix  2      [ ACC ]     SEQPACKET  LISTENING     12837    /run/udev/control
unix  2      [ ACC ]     STREAM     LISTENING     18885    /run/containerd/s/89d5e09b3b622cd197d7191c2fe8b9d725cfe5b028edb277b809ed0ec6b01176
unix  2      [ ACC ]     STREAM     LISTENING     16270    /run/containerd/containerd.sock.ttrpc
unix  2      [ ACC ]     STREAM     LISTENING     16273    /run/containerd/containerd.sock

and going to this url:

:4357

gives me:

@WallyR does that help?

WallyR · June 2, 2023, 1:24pm

This indicate that HA is running as it should.
There is something listening to port 8123.

What happens if you try to connect with HTTP to the IP addess of the HA on port 8123, ie http://:8123 ?
Could you post a picture of the error page?

My guess is that something has messed up the docker configuration, so the network is not set up properly anymore. Portainer have been known to do this, but your system is supported, so you are most likely not running that.

KruseLuds · June 2, 2023, 7:14pm

You are right, I am not using Portainer. My backup clone SSD which also worked perfectly running HA supervised also now has the same issue… 192.168.0.34 is the internal address of my HA instance (on either ssd, one is a clone of the other and for backup).

Using https://192.168.0.34:8123 in a browser I can now get in (why wasn’t it working before? &(^*&). It turns out the duckdns add-on is not running and unable to start, I get this error message when I try to start it:

Image homeassistant/aarch64-addon-duckdns:1.15.0 does not exist for addon_core_duckdns

I uninstalled and reinstalled the add-on - issue resolved. Sheesh!

My UI-minimalist card files sometimes disappear as well, I just need to re-download them occassionally too. I unmounted and checked checked the health of the SSD, even defragmented it - but I had done that before as well - and those files are occasionally missing - who knows. Annoying at any rate.

Thanks for your efforts in helping!