Hello everyone. I just set up a webserver along with Nagios to use for our institute. Everything went fine (I followed the guide at http://www.debianhelp.co.uk/nagiosinstall.htm, using a Debian system) so far. However, if I try to access the webinterface via http://IP-adress/nagios, after logging in with the nagiosadmin account, the browser will download a [random-name].part file, which contains the following HTML code:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Frameset//EN" "http://www.w3.org/TR/html4/frameset.dtd";> <html> <head> <meta name="ROBOTS" content="NOINDEX, NOFOLLOW"> <title>Nagios</title> <link rel="shortcut icon" href="images/favicon.ico" type="image/ico"> </head> <frameset cols="180,*"> <frame src="side.php" name="side" frameborder="0"> <frame src="main.php" name="main" frameborder="0"> <noframes> <!-- This page requires a web browser which supports frames. --> <h2>Nagios</h2> <p align="center"> <a href="http://www.nagios.org/";>www.nagios.org</a><br> Copyright (c) 1999-2009 Ethan Galstad<br> </p> <p> <i>Note: These pages require a browser which supports frames</i> </p> </noframes> </frameset> </html> This was tested via Epiphany and Firefox in Debian and Firefox in Windows XP. I have not come across this problem in any documentation or the mailing list archives, so I hope someone can help me here. Best regards, -- Simon Dehne Institut f?r Turbomaschinen und Fluid-Dynamik (TFD) Gottfried Wilhelm Leibniz Universit?t Hannover Appelstr. 9 30167 Hannover Tel.: +49 511/762-17753 web: http://www.tfd.uni-hannover.de eMail: de...@tfd.uni-hannover.de ------------------------------------------------------------------------------ This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd _______________________________________________ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
