munin
munin copied to clipboard
munin-monitoring
Refused to connect
Describe the bug Not completely sure if this is a bug or not, however, Munin Master refuses to run on port 4948, not sure if it's able to run on another port, couldn't find anything in the docs - I've whitelisted the port in the firewall as well.
To Reproduce Steps to reproduce the behavior:
- Install Munin Master (apt-get install munin).
- Try to access it on the web.
- See the error.
Expected behavior A webpage to view statistics like the demo.
Screenshots & Logs
- OS & Distribution: Ubuntu 20.04 LTS
- Browser: Google Chrome - Latest
- Munin Version: Latest
Additional context
Not available.
I guess, you are using Munin 2.0.x? The built-in webserver is only available in munin 3, which is not released as stable, yet. See munin's webserver documentation.
Do you remember, where you got the impression, that a web service should be available on port 4948? I would be happy to clarify this in the docs.
Hi, I've tried connecting to localhost/munin as well, this is where I saw that it runs on port 4948 (https://img.techout.tech/lHfse78h) which is 3 from the looks of it, however, Munin 2.0.x wasn't running on localhost/munin either.
which is 3 from the looks of it
How do you know, that it is munin 3.x? What is the output of dpkg -l | grep munin?
Munin 2.0.x wasn't running on localhost/munin either.
Did you install apache2?
See /usr/share/doc/munin/README.Debian.gz for more details, please.
Got a similar issue with "localhost/munin".
Got a "This site can't be reached" "ERR_CONNECTION_REFUSED" After installing apache2 got a 404 error page. Then I enabled the conf in apache with "sudo a2enconf munin" command.
With a fresh install if you install apache2 before munin, the "a2enconf" is not needed.
Installed it on a Debian 11 with apt. Munin version was 2.0
