Tried that, unless something didn't stick it didn't work for me. went back to 11.24.2 and seems fine
Though this is not a problem solution but it's started when cPanel upgraded to 11.25 and this solution was given by a cPanel member itself somewhere on the forum unless the issue is fixed with other available cPanel trees i.e. stable, release.
The solution I mentioned worked for me on 2 servers and everything is working fine.Sled151 said:
If this issue is being experienced please submit a support request/ticket referencing this thread; this will help most to properly diagnose the issue as well as to verify corrective measures by allowing us to investigate directly. We would like to gather more verbose information by inspecting an affected server configuration and check for any other related details that may be involved.
For reference, a ticket submission may be initiated via the links in my forums signature or via WHM: Main >> Support >> Support Center >> Contact cPanel. When available, please PM me your ticket ID number so I may follow-up internally; both old and new tickets are of interest and should help with the investigation process. Thank you in advance.
For reference, a ticket submission may be initiated via the links in my forums signature or via WHM: Main >> Support >> Support Center >> Contact cPanel. When available, please PM me your ticket ID number so I may follow-up internally; both old and new tickets are of interest and should help with the investigation process. Thank you in advance.
New cPanel 11.25.0 Installation Apache configuration syntax errors
The release of 11.25.0-RELEASE_42399 and 11.25.0-CURRENT_42399 introduced a configuration issue that may cause Apache configuration syntax errors on servers with no accounts when the mod_userdir tweak is enabled. The condition will present itself upon addition of the first account to the server. This issue is quickly addressed by rebuilding the Apache configuration file.
Symptoms:
The following error can be seen in the cpanel error_log and when attempting to restart Apache:
UserDir "enable" keyword requires a list of usernames
Newly created websites would be sent to defaultwebpage.cgi instead of the
appropriate document root.
Resolutions:
1) New builds, 11.25.0-CURRENT_42400 and 11.25.0-RELEASE_42400, have been published to address the issue. This issue will not be present on subsequent new installations. Upgrading a currently affected system will resolve this issue.
2) Rebuilding the Apache configuration after the addition of the first account will permanently resolve this issue.
From the command line:
/scripts/rebuildhttpdconf
/scripts/restartsrv_httpd
or
/scripts/autorepair userdir_enable_fix
/scripts/restartsrv_httpd
From the WHM:
Service Configuration -> Apache Configuration -> Global Configuration -> Save -> Rebuild Configuration and Restart Apache
Note:
The Apache configuration may be rebuilt as a result of other changes made in the WHM. Your new installation may not experience this issue as a result the the Apache configuration being rebuilt automatically.
The above information has been released on the news mailing list information on joining please see below:
_______________________________________________
News mailing list
[email protected]
- cPanel Inc.
The release of 11.25.0-RELEASE_42399 and 11.25.0-CURRENT_42399 introduced a configuration issue that may cause Apache configuration syntax errors on servers with no accounts when the mod_userdir tweak is enabled. The condition will present itself upon addition of the first account to the server. This issue is quickly addressed by rebuilding the Apache configuration file.
Symptoms:
The following error can be seen in the cpanel error_log and when attempting to restart Apache:
UserDir "enable" keyword requires a list of usernames
Newly created websites would be sent to defaultwebpage.cgi instead of the
appropriate document root.
Resolutions:
1) New builds, 11.25.0-CURRENT_42400 and 11.25.0-RELEASE_42400, have been published to address the issue. This issue will not be present on subsequent new installations. Upgrading a currently affected system will resolve this issue.
2) Rebuilding the Apache configuration after the addition of the first account will permanently resolve this issue.
From the command line:
/scripts/rebuildhttpdconf
/scripts/restartsrv_httpd
or
/scripts/autorepair userdir_enable_fix
/scripts/restartsrv_httpd
From the WHM:
Service Configuration -> Apache Configuration -> Global Configuration -> Save -> Rebuild Configuration and Restart Apache
Note:
The Apache configuration may be rebuilt as a result of other changes made in the WHM. Your new installation may not experience this issue as a result the the Apache configuration being rebuilt automatically.
The above information has been released on the news mailing list information on joining please see below:
_______________________________________________
News mailing list
[email protected]
- cPanel Inc.
Please submit a support request for this issue as this will require a more thorough inspection via direct SSH access to the system. When available, please PM me referencing this thread and your new ticket ID number so I may follow-up internally. For reference, the links in my forums signature may be used to initiate a ticket submission, such as via one of the following (Support Options & Additional Support Options).
This morning (after last night's run of scripts/upcp) I was able to add the Add-On domain successfully.
I can only guess that something was fixed during the automatic run of scripts/upcp that wasn't quite right when I did the manual upgrade yesterday.
i am too having same issues with one domain after changing its ip address, its now going to
http://174.123.xxx.xx6/cgi-sys/defaultwebpage.cgi
when i type
http://174.123.xxx.xx6/
thanks god this is brand new server and we are still not using it. will create ticket asap.
EDIT: FIXED. for me it was happening because host name of the server was part of domain of which i was changing ip. example host name was venus.xxxxxx.com and i was changing ip for xxxxx.com.
but this should not happen right ?
i now upgraded cpanel to release version and changed host name to something else and now after changing ip it seems working fine.
will switch to stable version and see if it still works.
http://174.123.xxx.xx6/cgi-sys/defaultwebpage.cgi
when i type
http://174.123.xxx.xx6/
thanks god this is brand new server and we are still not using it. will create ticket asap.
EDIT: FIXED. for me it was happening because host name of the server was part of domain of which i was changing ip. example host name was venus.xxxxxx.com and i was changing ip for xxxxx.com.
but this should not happen right ?
i now upgraded cpanel to release version and changed host name to something else and now after changing ip it seems working fine.
will switch to stable version and see if it still works.
Last edited:
check IP in /var/cpanel/users/user file and in DNS records: /var/named/domain.db Thay must be same. Likely problem in this.
Still happening to me - after going to EDGE, rebuilding httpd.conf
The server I manage hosts several .DK domain names.
Somehow over this past weekend, many of the site visitors - both from Denmark and the US, suddenly started getting the redirect to /cgi-sys/defaultwebpage.cgi ... Some would get it after browsing one of the websites for a while, all of the sudden to be redirected to the default cpanel page.
The main server IP is shared across 10-12 websites, the secondary is dedicated to a single domain name (running ssl).
This is very frustrating. I know many time, hitting on the main IP of the server directly forwards to the default page - so I have adjusted my httpd.conf file so that instead of the default server (1st <virtualhost > block for each IP) pointing at /usr/local/apache/htdocs - it points at the 2 primary websites hosted on this server.
This seems to have helped - so they can go directly to the IP and get the correct website.
however there are still a few straglers getting the defaultwebpage.cgi (based on the web logs in /usr/local/apache/domlogs).
I have even went as far as creating an index.shtml file and placing it in /usr/local/cpanel/htdocs .... this will set a hostname variable (hard coded IP address) based on $HTTP_HOST and then do a meta refresh to that IP address. Again - helped for some, but there are still a few people getting defaultwebpage.cgi ...
87.56.100.115 - - [05/Feb/2010:18:02:58 -0500] "GET /cgi-sys/defaultwebpage.cgi HTTP/1.1" 200 3477 "http://mydomain.dk/" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/532.5 (KHTML, like Gecko
WTF? Cpanel -- this is really becoming unacceptable. I am ready to tear the server down and have them install Plesk!!!
The server I manage hosts several .DK domain names.
Somehow over this past weekend, many of the site visitors - both from Denmark and the US, suddenly started getting the redirect to /cgi-sys/defaultwebpage.cgi ... Some would get it after browsing one of the websites for a while, all of the sudden to be redirected to the default cpanel page.
The main server IP is shared across 10-12 websites, the secondary is dedicated to a single domain name (running ssl).
This is very frustrating. I know many time, hitting on the main IP of the server directly forwards to the default page - so I have adjusted my httpd.conf file so that instead of the default server (1st <virtualhost > block for each IP) pointing at /usr/local/apache/htdocs - it points at the 2 primary websites hosted on this server.
This seems to have helped - so they can go directly to the IP and get the correct website.
however there are still a few straglers getting the defaultwebpage.cgi (based on the web logs in /usr/local/apache/domlogs).
I have even went as far as creating an index.shtml file and placing it in /usr/local/cpanel/htdocs .... this will set a hostname variable (hard coded IP address) based on $HTTP_HOST and then do a meta refresh to that IP address. Again - helped for some, but there are still a few people getting defaultwebpage.cgi ...
87.56.100.115 - - [05/Feb/2010:18:02:58 -0500] "GET /cgi-sys/defaultwebpage.cgi HTTP/1.1" 200 3477 "http://mydomain.dk/" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/532.5 (KHTML, like Gecko
WTF? Cpanel -- this is really becoming unacceptable. I am ready to tear the server down and have them install Plesk!!!
Without having direct access to the system it is impossible to know with certainty what circumstances are creating the reported behavior; please submit a support request so that we may assist with investigation and more accurately determine the cause of your unique situation. When available, let me know the ticket ID number of your support request (e.g., via a PM) so that I may follow-up internally. For reference, the links in my forums signature may be used to initiate a ticket submission, such as via one of the following: (Support Options & Additional Support Options).
Don
This is a colo server @ theplanet - do you provide support or do I have to go through theplanet -- my previous contact with theplanet was "we cannot reproduce it ..." (so nothing is wrong) ...
Normally the license provider is one of the first in line to assist. If the data center, The Planet, provides your license, I recommend asking them to submit a ticket on your behalf as this will ensure it receives higher priority. If there is any difficulty in receiving further assistance you are welcome to escalate the issue by submitting a support request to us directly; the Additional Support Options page will help in this regard.
The fix is included in the latest builds of cPanel 11.25; please ensure the system is up-to-date and using the latest cPanel version for the configured build tree (e.g., RELEASE, CURRENT). For reference, the latest cPanel/WHM build and version information may be checked via the following two resources:
cPanel Downloads - Latest cPanel/WHM Builds
cPanel Change Log
The full cPanel version and build number may be obtained using the following command via SSH access:
Code:
# cat /usr/local/cpanel/version && echo
Code:
# /scripts/upcp --forceI have the latest version and it is still an issue...
Code:
[email protected] [~]# cat /usr/local/cpanel/version && echo
11.25.0-RELEASE_43286I'm having a similar issue on a brand new cpanel installation.
It's not the www subdomain that's the problem though, it's the cpanel subdomain.
If I try to access http://cpanel.domainname.tld/ I'm redirected to cgi-sys/defaultwebpage.cgi.
But http://www.domainname.tld/cpanel/ works fine.
EDIT
----
Found the solution here - http://forums.cpanel.net/f5/fresh-install-wont-show-default-apache-page-141965.html
It's not the www subdomain that's the problem though, it's the cpanel subdomain.
If I try to access http://cpanel.domainname.tld/ I'm redirected to cgi-sys/defaultwebpage.cgi.
But http://www.domainname.tld/cpanel/ works fine.
EDIT
----
Found the solution here - http://forums.cpanel.net/f5/fresh-install-wont-show-default-apache-page-141965.html
Last edited:
I just wanted to follow up on my particular error.
Mine was a little bit of a weird case, where my secondary DNS provider had "accidentally" updated zone records. My assumption on how DNS works has always been that the primary (ns1.) is ALWAYS used and ns2 only comes into play if ns1 is down.
Some of the people were seeing the BAD IP from ns2 zone file for the first "hit" (on /usr/local/cpanel/htdocs/index.html) - this default page redirects to cgi-sys/defaultwebpage.cgi. The WEIRD part was that the second "hit" (on defaultwebpage.cgi) came to the IP listed in the ns1. zone file.
Fixed the DNS and all is well in cPanel land.
BTW -- It was cPanel support who pointed out the incorrect dns info using intoDNS: checks DNS and mail servers health
Please escalate the issue via a support request so that the symptoms may be investigated; the links in my forums signature may be used to initiate a ticket submission. When available, please let me know the ticket ID number (e.g, via a PM) so I may follow-up internally.I have the latest version and it is still an issue...
Code:[email protected] [~]# cat /usr/local/cpanel/version && echo 11.25.0-RELEASE_43286
Same problem on 2 servers at the latest rev
I was installing a new server and planning to move an account and website from old server A to server B.
I went on server A to look (only look!!!) at my easyapache configuration and options
I went at the same time into easyapache on server B to install the modules needed.
Then, I lost BOTH my sites!!!
They both now are redirected to http://<home>/cgi-sys/defaultwebpage.cgi
with url as well as IP.
I need a fix. Why don;t you publish what is wrong and a fix so that we can at least manually get back online?
it looks like the error is in the httpd.conf file, but I am at a loss to find and fix it.
I tried all the suggestions, but without success.
I was installing a new server and planning to move an account and website from old server A to server B.
I went on server A to look (only look!!!) at my easyapache configuration and options
I went at the same time into easyapache on server B to install the modules needed.
Then, I lost BOTH my sites!!!
They both now are redirected to http://<home>/cgi-sys/defaultwebpage.cgi
with url as well as IP.
I need a fix. Why don;t you publish what is wrong and a fix so that we can at least manually get back online?
it looks like the error is in the httpd.conf file, but I am at a loss to find and fix it.
I tried all the suggestions, but without success.