Topic: Help! I've buggered up server-manager!

[russs]

I foolishly fiddled with my 'httpd.conf' folder in /etc/httpd and can no longer get access to the server-manager page, all I get is:
Proxy Error
The proxy server received an invalid response from an upstream server.

The proxy server could not handle the request GET /server-manager.

Reason: Could not connect to remote machine: Connection refused

I have tried accessing by IP address or hostname and with or without HTTPS to no avail.
My intranet and phpmyadmin pages still work on the machine and I can still access it normally in other ways. Basically everything works apart from 'server-manager', 'user-password' etc.

I turned SSLengine to on on the main server name section. I quickly turned it back off again but it still doesn't work. please ehlp as it's a bit embarrassing. (Damn, must start reading up on Aapche more!!)

Thanks all.

[ergozd]

You could try re-gerenating your httpd.conf files with

Code: [Select]

# /sbin/e-smith/xpand-template /etc/httpd/conf/httpd.conf
# /sbin/e-smith/expand-template /etc/httpd/admin-conf/httpd.conf

Re-start then both httpd and httpd-admin

Code: [Select]

# /etc/init.d/httpd restart
# /etc/init.d/httpd-admin restart

Hope it helps

[stefan24]

# /sbin/e-smith/xpand-template ...

Indeed it is

Code: [Select]

/sbin/e-smith/expand-template ...

[russs]

Thank-you to both of you, however, before I do this will it affect my existing setup, my egroupware intranet for example?

Thanks again

[stefan24]

I do not know, what you have changed in your /etc/httpd/conf/httpd.conf, but you must have found this header:

Code: [Select]

#------------------------------------------------------------
# DO NOT MODIFY THIS FILE! It is updated automatically by the
# SME Server software. Instead, modify the source template in
# an /etc/e-smith/templates-custom directory. For more
# information, see http://www.e-smith.org/custom/
#
# copyright (C) 1999-2003 Mitel Networks Corporation
#------------------------------------------------------------


If you have installed your eGroupware the same way by editing this conf file by hand, it is very likely, that you will kill the eGroupware setup, too.

However, if you used a setup or installation Howto specifically for SME, this would certainly restore a working version.
But why do you not backup the existing conf file, use the above expand-template command and compare the new conf file to find the difference between both of them?
You can do this while running SME, if you do not restart the httpd daemon.

[russs]

If only I'd backed the conf file up in the first place before touching it I wouldn't have had the trouble! If I had a Euro for every novice Linux user who has not done this first I'd be a Millionare I guess!
Thanks very much for your help Stefan I ran the smeplus.sh script and this has solved it and not harmed my eGroupware. I will bare your tips in mind for the future though.
Thankyou