Debian 12 cockpit addition allmon3 has stopped working

Allmon
1

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?

-cut-

If you don’t want to take the risk of that, but still want all the web experience, you can install:



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-

2

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.

3

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!

1 Like
4

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