Discussion:
[Monitorix-general] Monitorix page: 'Not Found' after installing to Ubuntu 12.04 server on Amazon EC2 running Apache2
Christopher D. Bartels
2014-09-25 00:37:20 UTC
Permalink
Hi,



I've just installed Monitorix from the izzy repo on an Ubuntu 12.04 server
running Apache2 on Amazon EC2, & when I browse to x.x.x.x:8080/monitorix, or
x.x.x.x/monitorix, I get a 'Not Found' page instead of the control panel.



I've disabled the built-in webserver in the config file, & it didn't revert
to an Apache2-served page.



I don't see anything other than that it should work out of the box with
Apache2, so I can't confirm that it's indeed set to use the webserver
properly.



Actually, I did see 1 about setting /etc/apache2/conf.d/monitorix.conf to
allow a remote IP address, but I don't have a 'conf.d' in /etc/apache2, &
there's nothing related to Monitorix in 'conf-available' or 'conf-enabled'
to check.



How do I make this work?



Please advise.



Thanks,

Chris
Jordi Sanfeliu
2014-09-25 07:53:55 UTC
Permalink
Hi,

The latest Monitorix version (3.6.0 right now) works out-of-the-box, and
if I recall correctly, the built-in HTTP server comes also enabled by
default for Debian/Ubuntu systems.

So, right after a successful installation you should check the
'monitorix.conf' file to adapt it to your system and finally, start
Monitorix.

Please, make sure the URL <http://localhost:8080/monitorix/> works
locally in that system. You might want to use 'lynx' or 'elinks'
commands to test the local URL.

After you see that Monitorix is working locally then you can start
testing it remotely. If you have problems to access Monitorix remotely
check your firewall rules.

Regards.
Hi,
I’ve just installed Monitorix from the izzy repo on an Ubuntu 12.04
server running Apache2 on Amazon EC2, & when I browse to
x.x.x.x:8080/monitorix, or x.x.x.x/monitorix, I get a ‘Not Found’ page
instead of the control panel.
I’ve disabled the built-in webserver in the config file, & it didn’t
revert to an Apache2-served page.
I don’t see anything other than that it should work out of the box with
Apache2, so I can’t confirm that it’s indeed set to use the webserver
properly.
Actually, I did see 1 about setting /etc/apache2/conf.d/monitorix.conf
to allow a remote IP address, but I don’t have a ‘conf.d’ in
/etc/apache2, & there’s nothing related to Monitorix in ‘conf-available’
or ‘conf-enabled’ to check.
How do I make this work?
Please advise.
Thanks,
Chris
--
Jordi Sanfeliu
FIBRANET Network Services Provider
http://www.fibranet.cat
Loading...