Topic: server-manager no longer accessible.

[JT!]

I tried to add range 0.0.0.0 / 255.255.255.255 to the list of allowed addresses. The server now cannot be accessed for management.

Which file is it that holds this config error i made?

What steps can i take to remove my entry, or even to 'reset' the server-manager to out-of-box config?

Thanks.
_______________________________________________________

500 intenal server error:
_______________________________________________________

Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, admin and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.

[bpivk]

You should start by explaining just what you did.

Most of the parameters are templated so try with a signal-event post-upgrade and signal-event reboot commands.

And you sohuld NEVER open your server like you wanted to.

[Chaney]

I see about 30 topics concerning the server-manager, so I'll just bump one of the newest.

I haven't installed anything new, the only "thing" I did, is that I looked up .my.cnf in /root , I needed it's password to fill in the config for PhpMyAdmin; which I installed by copying it to an ibay and editing the config.inc.php.
I made the information bay right before, ofcourse, and then closed the server-manager
About 2 hours later, I tried to go the server-manager again and got the error.
I checked about every post I found with the Search function, however I hardly found the same situation, as I didn't really install anything.

It might be interesting to add that, when I go to the "regular link" (http://192.168.1.85/server-manager), the page that gives me the error message is located here: https://192.168.1.85/server-common/cgi-bin/login?back=http%3a%2f%2f192.168.1.85%2fserver-manager

I checked about all the logs too, and the most informative one resembles the link I gave above this line.

Thanks in advance.

And here, the famous error message:

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, admin and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.

[bpivk]

More information about this error may be available in the server error log.

Did you check the log?

And if you suspect this as a bug use this link http://bugs.contribs.org/ and report it so the devs help you.

[mmccarn]

Errors starting or running server-manager should be in /var/log/httpd/admin_error_log

I tried to add range 0.0.0.0 / 255.255.255.255 to the list of allowed addresses. The server now cannot be accessed for management.

Can you tell us exactly what you did to try to "add range 0.0.0.0 / 255.255.255.255 to the list of allowed addresses"?  If you're seeing no errors in /var/log/httpd/admin_error_log then you've probably modified the iptables rules to deny traffic from everywhere -- and the fix would be easier to figure out if we knew exactly what had been done...

The range you've indicated - 0.0.0.0 / 255.255.255.255 - doesn't match *any* hosts.  "0.0.0.0 /0.0.0.0" will match every host on the planet, and "a.b.c.d / 255.255.255.255" will match any single specific host...

iptables info is logged to /var/log/iptables/current, but I don't know if blocked access is logged there by default.