# Can’t access Houston ui

**URL:** <https://forum.45homelab.com/t/can-t-access-houston-ui/782>\
**Category:** Software & Applications\
**Created:** [December 1, 2023, 2:27pm UTC](https://forum.45homelab.com/t/can-t-access-houston-ui/782 "2023-12-01T14:27:49Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Goose](https://forum.45homelab.com/letter_avatar_proxy/v4/letter/g/5f9b8f/32.png) [@Goose](https://forum.45homelab.com/u/Goose)\
**Post date:** [December 1, 2023, 2:27pm UTC](https://forum.45homelab.com/t/can-t-access-houston-ui/782/1 "2023-12-01T14:27:49Z")

</div>

Hello  
I have gotten into the ipmi, determined my up address, but when I go to the ip address [https://192.168.1.102:9090](https://192.168.1.102:9090) I am getting site not found. Is Houston not installed. I am not familiar with rocky so not sure where to look for installed packages.

 ![IMG_3757](https://forum.45homelab.com/uploads/default/original/1X/0defc6a08420536de16bd5a9287a10db430d7cd7.jpeg)  
 ![IMG_3758](https://forum.45homelab.com/uploads/default/original/1X/a41a8f2a2daae1a0a4433f35948874864c462f4b.jpeg)

I have tried using both ports on the motherboard. And the different addresses to no avail

---

<div class="post-metadata">

**Author:** ![Goose](https://forum.45homelab.com/letter_avatar_proxy/v4/letter/g/5f9b8f/32.png) [@Goose](https://forum.45homelab.com/u/Goose)\
**Post date:** [December 1, 2023, 2:38pm UTC](https://forum.45homelab.com/t/can-t-access-houston-ui/782/2 "2023-12-01T14:38:24Z")

</div>

Rtfm! Troubleshooting at end of manual. Needed to restart cockpit service for those who have this issue

---

<div class="post-metadata">

**Author:** ![00firestar00](https://forum.45homelab.com/user_avatar/forum.45homelab.com/00firestar00/32/91_2.png) [@00firestar00](https://forum.45homelab.com/u/00firestar00)\
**Post date:** [December 1, 2023, 4:21pm UTC](https://forum.45homelab.com/t/can-t-access-houston-ui/782/3 "2023-12-01T16:21:35Z")

</div>

I had the same problem.  
You might want to make sure its enabled. `systemctl enable cockpit`  
That way it will start up automatically on boot.

---

<div class="post-metadata">

**Author:** ![pcHome](https://forum.45homelab.com/user_avatar/forum.45homelab.com/pchome/32/1207_2.png) [@pcHome](https://forum.45homelab.com/u/pcHome)\
**Post date:** [December 1, 2023, 6:54pm UTC](https://forum.45homelab.com/t/can-t-access-houston-ui/782/4 "2023-12-01T18:54:34Z")

</div>

make sure firewalld is not blocking 9090 or disabled.

I had an issue with that as I did not know that firewalld was configured.

---

<div class="post-metadata">

**Author:** ![pxpunx](https://forum.45homelab.com/user_avatar/forum.45homelab.com/pxpunx/32/45_2.png) [@pxpunx](https://forum.45homelab.com/u/pxpunx)\
**Post date:** [December 17, 2023, 5:16am UTC](https://forum.45homelab.com/t/can-t-access-houston-ui/782/5 "2023-12-17T05:16:37Z")

</div>

FYI - it’s `systemctl enable cockpit.socket`

```auto
[root@hl15 motd]# cat inactive.motd 
Activate the web console with: systemctl enable --now cockpit.socket

```

It’s also in their documentation here: [Running Cockpit — Cockpit Project](https://cockpit-project.org/running.html)

If you try to enable `cockpit`, you’ll get an error because the service config has no `[Install]` section.

`systemctl start cockpit` works fine to start Cockpit/Houston, however.