# Debian 12 cockpit addition allmon3 has stopped working
**URL:** https://community.allstarlink.org/t/debian-12-cockpit-addition-allmon3-has-stopped-working/23588
**Category:** AllStarLink
**Tags:** new-users
**Created:** [August 9, 2025, 3:05pm UTC](https://community.allstarlink.org/t/debian-12-cockpit-addition-allmon3-has-stopped-working/23588 "2025-08-09T15:05:56Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@VE7MXU](https://community.allstarlink.org/u/VE7MXU)
#### Post date: [August 9, 2025, 3:05pm UTC](https://community.allstarlink.org/t/debian-12-cockpit-addition-allmon3-has-stopped-working/23588/1 "2025-08-09T15:05:56Z")
I had allmon3 working but decided to experiment and added the unsupported addition of cockpit. Now I have no web connectivity. Any ideas where to start troubleshooting?
> **[Debian 12 Appliance - AllStarLink Manual](https://allstarlink.github.io/install/debian/deb-appliance/)**
>
> AllStarLink Manual
-cut-
If you don’t want to take the risk of that, but still want all the web experience, you can install:
```auto
```
```auto
sudo apt install cockpit cockpit-networkmanager cockpit-packagekit \
cockpit-sosreport cockpit-storaged cockpit-system cockpit-ws \
python3-serial firewalld
```
Which should give you an unbranded, uncustomized `Cockpit` environment.
Again, doing the above is **experimental and not generally recommended** , but you are welcome to give it a try, and perhaps provide feedback on issues and changes to help push the development of a Debian 12 Appliance image along!
-cut-
---
### Author:  [@VE7MXU](https://community.allstarlink.org/u/VE7MXU)
#### Post date: [August 9, 2025, 9:21pm UTC](https://community.allstarlink.org/t/debian-12-cockpit-addition-allmon3-has-stopped-working/23588/2 "2025-08-09T21:21:36Z")
OK
- Diagnostics from the asl-menu all is good.
- allmon3 restarts with no errors when a status is run.
- apache2 restarts with no errors when a status is run.
- copied working nodes /var/www/html/_\*.\* and replicated permissions._
Still isn’t working over http or https by local dns name or ip address.
---
### Author:  [@VE7MXU](https://community.allstarlink.org/u/VE7MXU)
#### Post date: [August 10, 2025, 1:47pm UTC](https://community.allstarlink.org/t/debian-12-cockpit-addition-allmon3-has-stopped-working/23588/3 "2025-08-10T13:47:40Z")
**Sharing My Experience – Cockpit, SSL, and Allmon Setup**
I’ve learned a few things during my setup process that I hope will help others who might be running into similar issues.
First off, I’m new to using **Cockpit** , and I initially misunderstood its purpose—I thought it was a component of AllStarLink. Turns out, it’s actually a general-purpose Linux management tool. Because of that assumption, I wasn’t able to get it working properly at first.
On a related note, I successfully generated **self-signed SSL certificates** , which was another challenge I hadn’t mentioned earlier. Thankfully, those components are functioning as expected.
To troubleshoot, I went through the process of **uninstalling and reinstalling** each component. That helped me uncover a few things, but I’m still stuck trying to get **Allmon** to work. I haven’t yet pinpointed where the issue lies within **Apache2** , and that’s been a bit of a roadblock.
At this point, I’ve spent quite a bit of time just doing reinstalls. So now I’m taking a more methodical, **step-by-step approach** , which is helping things make more sense. My **primary node is running fine on a Raspberry Pi 3B+** , so this setup is more of a **learning experience** than a production-critical need.
Hope this helps someone else out there who’s navigating similar waters!
---
### Author:  [@VE7MXU](https://community.allstarlink.org/u/VE7MXU)
#### Post date: [August 12, 2025, 5:03am UTC](https://community.allstarlink.org/t/debian-12-cockpit-addition-allmon3-has-stopped-working/23588/4 "2025-08-12T05:03:13Z")
OK, so I cooked up a node without a radio got everything running really well and I pretty much documented everything step-by-step so this thread can be closed