Default Apache Page on All Domains

Code: [Select]

Apache PHP info:
PHP 5.6.37 (cli) (built: Jul 20 2018 06:10:33)
Copyright (c) 1997-2016 The PHP Group
Zend Engine v2.6.0, Copyright (c) 1998-2016 Zend Technologies

Apache start script check:
grep: /etc/init.d/httpd: No such file or directory

CWP Admin check:
/usr/local/cwpsrv/htdocs/admin

CWP version:
0.9.8.967
I don't know how all my domains are showing default Apache page.... I tried everything on available on google but wasn't able to figure it out what the issue is actually!

Contents of File: /usr/local/apache/conf/httpd.conf   

ExtendedStatus On
Include /usr/local/apache/conf/sharedip.conf
Include /usr/local/apache/conf.d/*.conf
------------------------------
Contents of File: /usr/local/apache/conf.d/vhosts.conf

IncludeOptional /usr/local/apache/conf.d/vhosts/*.conf


I cannot reinstall CentOS because it will destroy everything!

systemctl status httpd

in CWP -> WebServers Settings -> Webservers Main COnfig
Check Rebuild all Vhosts and click save

systemctl status httpd

in CWP -> WebServers Settings -> Webservers Main COnfig
Check Rebuild all Vhosts and click save

When will people finally understand that this is not working? It never worked for me and people not answering to this makes the problem everlasting.

Has anyone thought that some maybe using nginx and varnish in their setup? What then? You wait for 10 hour long ticket response i quess.

By the way for the people who are looking for the answer is that they forgot to properly handle all instanses of the httpd so i think you should try the following at the command prompt.

killall httpd
/usr/local/apache/bin/httpd -k start

systemctl status httpd

in CWP -> WebServers Settings -> Webservers Main COnfig
Check Rebuild all Vhosts and click save

When will people finally understand that this is not working? It never worked for me and people not answering to this makes the problem everlasting.

Has anyone thought that some maybe using nginx and varnish in their setup? What then? You wait for 10 hour long ticket response i quess.

By the way for the people who are looking for the answer is that they forgot to properly handle all instanses of the httpd so i think you should try the following at the command prompt.

killall httpd
/usr/local/apache/bin/httpd -k start

When will users realize that we can't help fix problems without information?  You also failed to reply to the original response asking for said information.  I don't have a magic wand to fix your problems, but with troubleshooting steps, and information, you would get your help.  I'm glad you discovered your issue, bit don't take out your lack of response on those trying to help you.  I personally have flagged you now as a do not help person because of your attitude.  Best of luck...

I don't care about your flags and banner on this account. I created to help the people who helplessly search for a solution after they lost all their sites because none of the developing team of CWP ever put an effort in testing the updates before they release them.

I know you wanted to help and posted what you could, with the information you had but i felt the need to intercept this because it's getting out of hand and it's been repeating it self since 2015. This is a serious reason to drop CWP all together and lose users from the lack of stability.

CWP has 6 options in the selection of the web server and if the devs don't make sure that the updates doesn't conflict with the apache that serves CWP itself i don't know what to say to that.

My attitude is what it is because of the countless hours spend on troubleshooting what happened after each update and having to explain why on earth a whole server is down after the admin had the audacity to keep them updated.

People like me are required to put a dent in a situation that keeps repeating itself. Some of us has to be the "bad guys" in order to make a change. If this offends you then you might want rethink your approach to this because you might be part of the problem.

I don't disagree that CWP has it's problems.  I don't disagree that some of them are made worse by lack of testing.  But I have 2 issues with trying to help SOME of these people.

1)  There is a Search function on this forum.  I guarantee I have answered the same questions 20 times with some of these errors.  I've also searched google for some of the NON-CWP errors people are receiving (Ex: postfix), and found the solution in the #1 result.

I'm sorry, but if your hand has to be held through the entire process, maybe, just maybe you shouldn't be running a server.

2)  When there is a serious problem, 90% of these post are "I get x error", and that is there post.  When we respond to try to get more information, they either A) Ignore use, or B) come back with some smart response as to why we aren't helping them.

So please, tell me how I'm part of the problem some more.  Don't forget that I DO NOT work for CWP. I'm here to help people just as much as your are.  Difference is, I don't berate people because the "ADVICE" they gave me didn't work.  A simple "Sorry, that's not working for me, do you have another option" would probably get you a lot farther...

I don't care about your flags and banner on this account. I created to help the people who helplessly search for a solution after they lost all their sites because none of the developing team of CWP ever put an effort in testing the updates before they release them.

I know you wanted to help and posted what you could, with the information you had but i felt the need to intercept this because it's getting out of hand and it's been repeating it self since 2015. This is a serious reason to drop CWP all together and lose users from the lack of stability.

CWP has 6 options in the selection of the web server and if the devs don't make sure that the updates doesn't conflict with the apache that serves CWP itself i don't know what to say to that.

My attitude is what it is because of the countless hours spend on troubleshooting what happened after each update and having to explain why on earth a whole server is down after the admin had the audacity to keep them updated.

People like me are required to put a dent in a situation that keeps repeating itself. Some of us has to be the "bad guys" in order to make a change. If this offends you then you might want rethink your approach to this because you might be part of the problem.

If you have been using cwp since 2015 and dont have a handle on it yet, then its time to hang it up and go back to cpanel.

I don't disagree that CWP has it's problems.  I don't disagree that some of them are made worse by lack of testing.  But I have 2 issues with trying to help SOME of these people.

1)  There is a Search function on this forum.  I guarantee I have answered the same questions 20 times with some of these errors.  I've also searched google for some of the NON-CWP errors people are receiving (Ex: postfix), and found the solution in the #1 result.

I'm sorry, but if your hand has to be held through the entire process, maybe, just maybe you shouldn't be running a server.

2)  When there is a serious problem, 90% of these post are "I get x error", and that is there post.  When we respond to try to get more information, they either A) Ignore use, or B) come back with some smart response as to why we aren't helping them.

So please, tell me how I'm part of the problem some more.  Don't forget that I DO NOT work for CWP. I'm here to help people just as much as your are.  Difference is, I don't berate people because the "ADVICE" they gave me didn't work.  A simple "Sorry, that's not working for me, do you have another option" would probably get you a lot farther...