Under Server: Services, that is what I see... Web Server: Offline, even though it shows Web Server: On in the box below. If I watch the process list while I turn it off, they go away and when I turn it on they come back. That seems to work right. What seems broke is whatever tries to monitor the web server. (I'm getting sick of the emails telling me it is down, especially when I CAN open it in a browser and see the processes running) What is it looking for and how do I help it find it?
ISPConfig tries to connect to your Apache on 127.0.0.1. If your apache is configured to not run on 127.0.0.1, then ISPConfig shows that your Apache is offline even if it is running (on other IP addresses than 127.0.0.1). Please post the output of Code: netstat -tap so that I can see if this is what causes the problem.
I know that's what it is... well, at least now I do. I set the listen directive in the httpd.conf to the second ip on the interface. That certainly will stop it from responding on 127.0.0.1. I was trying to separate ispconfig from the rest of the web sites by giving ispconfig port 80 and 443 on the primary IP, and httpd 80 and 443 on the secondary ip. I guess I chose the wrong way to do it... Do you have a better solution for me? (I need to run ispconfig on 80 or 443 to get by firewalls)
You can do it like that, if you don't care about the messages from ISPConfig that tell you that your Apache is offline...
Is there a better way of doing it? Maybe a way that doesn't involve it constantly letting me know it can't find the web server? Also, wouldn't it be better if ispconfig looked for the web server on the ip that the public would be hitting it on? (just a thought...) If its a problem of figuring out what ip it is on, parsing the httpd.conf for the LISTEN directive would give it right away. Just my $.02 (You'll find I'm full of opinions and ideas... sometimes even a good one...)
I found the "better way" I was looking for! Actually, it is exactly like I had it set up before, with two small additions: 1) in the /etc/httpd/conf/httpd.conf file, the "Listen" directive is actually 2 lines long... example: Listen 1.2.3.4:80 Listen 127.0.0.1:80 Adding the line with the 127.0.0.1 keeps ISPConfig happy. 2) Do the same thing in /etc/httpd/conf.d/ssl,conf for port 443: Listen 1.2.3.4:443 Listen 127.0.0.1:443 Now that everything runs like it should (I hope) All I have to do is figure out how to administer the resellers/clients/sites. Should be fun!
additional ip addresses i don't quite understand how to add additional ip addresses. i have 1 ip address that is the DSL connected to the web. i have one webserver with the ispconfig installed on it. do i use the ISPconfig admin to add additional ip addresses that i'd like to use -- or can i just make up any ip address i want. right now all the virtual hosts are pointed at the same IP -- which is the ip of the webserver. there is only one network adapter eth0 -- i did not create a second one when installing as it was causing problems on boot. any help you may have is greatly appreciated -- i'm trying to do a port 80 redirect, but no matter what i still have to change the port that the webserver listens on. i've had many of the same problems as are described in this thread. any ideas? thanks a lot. z
Where do you want to be able to reach it from? If you will only be connecting to the second IP from the local address, you only have to add it to your local machine and to your apache config. If you want to reach if from elsewhere, you will need to ask your DSL supplier to assign you an additional IP, or you will have to run a VPN endpoint on your local network so that you can connect to the second IP from inside your local network.
