Home assistant not listening on 8123. I Apr 13, 2021 · However after booting there’s nothing running on port 8123. 1. The Nextcloud server runs on port 80 is already configured with https by adding the certificates in the Apache configuration. If you’re new to Home Assistant, you’ll want to create a new directory for this purpose. 168. 9 KB. I started getting stuck in the look with the CLI won’t start If I do get is started. I think it has something to do with the ip address not being assigned properly. 2 on my TrueNAS installation in VMWare environment, then didn't bother configuring it as I was too lazy to mi Mar 22, 2023 · I think the problem lies with the installation not setting up listening ports. I can’t see my ha ip on my router’s network map. I would enter the local IP address in any browser and the pages would load securely. Dec 9, 2018 · Hi all, I have a very strange problem here. By following the steps outlined in each section, you can diagnose and resolve network, system, and configuration-related problems. On the host, I could access hass via 172. Screenshot 2022-06-06 1820131437×82 10. I checked the logs when Dec 6, 2022 · Hello everyone, New to the community, I have been trying to install homeassistant into docker for a while. Dec 19, 2024 · All of the sudden I can’t reach the interface via port 8123 anymore (perhaps installing 2024. Portainer won’t show ports, because every port is open. 83, port TCP/8123 is not listening. Jan 2, 2025 · I’ve also seen where the Observer page shows everything is online, but a rogue Add-On or Integration is making Home Assistant so busy that I don’t get any response from the :8123 web page. This Dec 25, 2022 · I will first check is home assistant listening to port 8123. 99 8123 Trying 192. SSH’ing into the device; netstat -l suggests that the device is NOT listening to Jun 6, 2022 · In Portainer I can see that it’s running, but I can’t assess the localhost:8123 This is how it looks in Portainer, and I’m curious because it’s the only container without IP/Ports but I don’t know what to do. Apr 29, 2022 · My Supervised HA has been loading pages securely from day 1 over 18 months ago just using the default 8123 port and inbuilt config. This is not a firewall issue or routing issue. I knew nothing about security certificates and had not done anything beyond initial default config. The given command in the scenario maps ~/homeassistant on the host to /config in the container, so make sure this directory exists: Home Assistant is open source home automation that puts local control and privacy first. So set that back to the hassio network. The update to 2024. At first I wanted to forward 8123 port in my router over to my Raspberry PI running hass. I. 0 killed insteon… Thought and prayer would be appreciated. It says that all is fine on the Raspberry Pi. Oct 2, 2023 · Set Up the Configuration Directory Home Assistant stores its configuration in a directory, which you will map to a volume in your Docker container. 9. If it isn’t listening then probably is docker container not started or exited. Anyone be able to help troubleshoot? Sep 18, 2022 · Hi there. Apr 23, 2025 · If http://homeassistant. e. docker log : s6-rc: info: service Dec 30, 2018 · When I do a fresh start of home assistant (on mac mini), I can’t open the local page using port 8123 yet. Host networking mode opens every port between the host and the home assistant container, and removes any network isolation between home assistant and the host. 2. io. jellyfin) - so I’m confident that’s not the issue. I’m able to access my home network remotely and port forwarding is set up correctly for several other services on other pis (eg. Nov 28, 2018 · Hi guys, I’m a bit lost here right now… I’ve installed Home Assistant using the venv method and it worked quite fine for I think two months now. A few days ago I wanted to make a small change to an ESPHome device yaml Aug 26, 2017 · For some reason my ISP forced my router over to IPV6 overnight and same day Home assistant stopped connecting via internet (only via LAN). 0 and core 2024. 12. I wouldn’t expect that from a newly installed instance though. 04 and freshly installed docker engine and docker desktop. I did a quick check an ran the default docker/getting-started and that one worked as… Sep 18, 2024 · Ok I am running HA in a Linux Virtual Machine run on a Mac OSX hot (sonoma). 8123 is blocked all of the sudden. Aug 12, 2020 · I have recently tried to access home assistant running on my Raspberry Pi 3B but I receive the following error in my browser: This site can’t be reached homeassistant ’s server IP address could not be found. Powered by a worldwide community of tinkerers and DIY enthusiasts. 33. local:8123? Learn how to troubleshoot mDNS issues and get connected. Firewall on Proxmox is turned off for testing. I am also able to ping the IP address of the Pi from my Windows computer on the cmd and received replies. From what I can tell it seems docker is not publishing the port. 30. Still, it hangs on “Starting Home Assistant” and it is not accessible on port 8123 via web browser. If it is listening check your ip, firewall, the common suspects. local. However, none of these ports are up and in listen mode. 1 -p 8123 | grep 8123 and may be try a few times, then nmap shows the port to be open: Home Assistant is open source home automation that puts local control and privacy first. Jan 2, 2025 · Struggling to access Home Assistant using http://homeassistant. I want to run Home Assistant on my M1 Mac mini with Docker. But the Observer URL on port 4357 seems to be fine. The automation still works perfectly well, but the web interface is completely dead and the app stops working. 29. sudo netstat -tunlp | grep 8123 And will take it from there. Yesterday, I sort of played with my router’s settings to add a private Adguard Home DNS server. root@pve:~# telnet 192. I know that sounds obvious, but I didnt think of it and I had success on the one but not the other. The observer URL doesn't show any issues. I can not access via port 8123. 0:8123, but the supervisor was still not available. When deploying HA with v0. Since HA is not listening on port 8123 it refuses any http connection for the GUI. I turn off the ufw firewall Mar 27, 2021 · Hi, I’m struggling to find a solution to my problem where my Home Assistant running on a Pi4 works perfectly well after reboot, but after 3d-2w or so, it completely stops responding to api requests. local:8123’ uri, try the IP:8123. Today however, I updated my systems dependencies using apt upgrade (running Ubuntu 18. Perfect to run on a Raspberry Pi or a local server. but I can observe via port 4357. Sep 15, 2022 · So I guess that starting Home Assistant over a previous session is probably a bad idea. I also have the problem that I can’t access HA by Jan 18, 2024 · For typical operation I would expect on top of the above the following open ports 1400 (I think this is used for Sonos) and of course 8123 that is used for the GUI. Assuming the request it I tried to change the homeassistant container to the host network, and that exposed port 8123 - great, but then the supervisor and all the other things in hassio network containers aren't accessible. local:8123 doesn't work, try http://homeassistant:8123. 4 did something?). Jun 24, 2025 · Hi there, I’m not great at things like this - but I’ve read every thread identifying similar issues and can’t find a solution that works for me! Running HA-OS on a Raspberry Pi 5. You can do this by ssh to ha and. I can get the the Supervisor page of port 4357, and I can ping in/out of the VM so I know it’s not a networking issue. The current setup is HA OS 13. The installation was successful however I cannot access homeassistant when using port 8123 when network mode is host, I can only access it if I change it to port 8123. Meaning HA does not work at all. 99… Mar 16, 2023 · Upon rebooting my Home Assistant instance, I see that the UI on port 8123 doesn’t work. 04) and after a restart, my assistant just wouldn’t listen to Port 8123 anymore Jan 23, 2025 · This article provides a comprehensive troubleshooting guide for resolving common issues with accessing Home Assistant via homeassistant. ( ‘can’t read website xxx:8123’ ) When I do some port scanning using nmap, like nmap -T Aggressive -A 127. 0 (145265) is currently the newest version available. I have it working fine when I run the container in network mode bridge and exposing port 8123, but with that configuration I was not able to use the HomeKit integration (I also tried to expose the default port for the HomeKit integration, 21603). Is probably related with the HA VM not Describe the issue you are experiencing Hi all, Odd issue here - I recently installed 9. local:8123. After looking around topics in the community it seems like I have to run the Feb 10, 2024 · The assistant URL said it was getting ready and would take around 20 mins but after a while this just stopped responding. 8123 I can access my ha through the ha ip. May 11, 2024 · After a brand new installation of image: “Package home-assistant · GitHub” looking at Alternative - Home Assistant no problem in booting, but unable to connect to port 8123. From hypervisor I can reach the observer via port 4357, can SSH via port 22, no problem. Yesterday, I updated to the newest version, which also worked just fine. Available for free at home-assistant. I am running the latest ubuntu 22. Mar 8, 2023 · Add one more thing - the posters here are very good - if you get stuck on the ‘homeassistant. However, that didn’t help. After some time I figured that the issue maybe with hass listening for tcp6 port I ran: netstat -tln with this response Active Internet Nov 30, 2024 · I’m having trouble accessing my ha via the web at homeassistant. 0. With the update to 2024. If that does not help, you may be able to find the IP address of Home Assistant Green on your router. where to go to dig into the logs to get a clue of the problem? I’m on Mac and netstat | grep 8123 is empty Docker Desktop 4. The HA server runs on the default port 8123, but it is not secured via SSL, although I am using the same IP and domain for it. Aug 3, 2021 · I have a setup with Home Assistant Supervised and a Nextcloud server on the same device. jnqem mopjj bhbg ewqt uklkze adnr cavosfy enzziiw xnylon ewsrq