munin after install: 403 forbidden

[Christian Matt]

Binary package hint: munin

After installing Lucid and doing a "sudo apt-get install munin", I tried to get Munin working on my servers.

On the first machine:
Upgrade from 9.10 to 10.04 via update-manager. I kept the Apache- and Munin-Configurations at default values.
Munin is running and reachable with e.g. w3m over ssh (the default adress localhost/munin).
Trying to reach the site from outside (means the same network, but an other computer) with IP/munin results in an Apache-Error 403.

Second machine:
New installation of 10.04. Meanwhile I confugred Apache with virtual hosts and Munin with a new Web-Directory, but from the beginning on I get the same 403-Error-page.
(Maybe caused by my configurations?) I cannot reach the Munin-page via localhost on this machine.

Obviusly I'm not the only one having this problem, e.g. http://ubuntuforums.org/showthread.php?t=1469102
But none of the tips worked for me.

both times:
Release: 10.04
munin: Installed: 1.4.4-1ubuntu1

[Clint Byrum (clint-fewbar)]

Hi Christian, thank you for reporting this bug and working with us to make ubuntu better!

The NEWS.Debian file does in fact mention this problem:

munin (1.4.0-1) unstable; urgency=low

    Move htmldir to /var/cache/munin/www. Note that we currently don't
    have a proper upgrade mechanism in place. When upgrading from a
    previous version of munin, you'll need to change /etc/munin/munin.conf
    htmldir parameter, from /var/www/munin, to /var/cache/munin/www.

So, when upgrading, you do need to do some manual reconfiguration. Adding this capability would be nice, and is probably worthy of a separate wishlist bug explaining exactly what you would expect to see on upgrade.

The package does, by default, restrict access to 127.0.0.1 only, so you should see it when hitting http://localhost from the machine itself. More complex access controls will require you to define exactly what you want.

For the rest of it, I suspect your configuration is the problem, and so I'm marking this incomplete. Please post your apache configuration files so we can ascertain what might be causing the 403. Also you may want to look in /var/log/apache2/error.log for some clues.

[Christian Matt (cmf)]

This is my third try to write a reply. Startet writing and solved the problem on my first machine. Then I wrote about the other machine and solved the problem there.
It was just misconfiguration by myself in (both) /etc/munin/apache.conf.

Thank you for (indirectly) guiding me to the solution :)