Unfortunately there is no one-size-fits-all solution that can work in everyone's unique situation. The symptom is relatively generic and may involve numerous factors; the best procedure to investigate why it is happening on your system is to escalate the issue with your license provider. Please be aware that if the domain involved is not resolving to the correct IP address (as seen in its Apache Virtual Host configuration), or if your computer is using a cached DNS record after a site IP change then you may see the default web page and this is normal; once the domain resolves to the correct IP address you should no longer see the default web page.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?
Thank you for the information; at the present time the request is still active but you are welcome to share the unique solution or other corrective measures that you found to help.Support Request Id 584906
I opened a ticket per your request.
<VirtualHost * x.x.x.x:80> ServerName server.com ServerAlias cpanel.* whm.* webmail.* webdisk.*
Here is the specific reference (per the default virtual host):[...] What arbitrates the usage of this defaultwebpage.cgi? I show no reference in Apache for it. [...]
# cat /usr/local/apache/htdocs/index.html <html><head><META HTTP-EQUIV="refresh" CONTENT="0;URL=/cgi-sys/defaultwebpage.cgi"></head><body></body></html>
To learn about how to customize the default web page please refer to the following WHM menu path, with linked documentation:[...] Please be aware that if the domain involved is not resolving to the correct IP address (as seen in its Apache Virtual Host configuration), or if your computer is using a cached DNS record after a site IP change then you may see the default web page and this is normal; once the domain resolves to the correct IP address you should no longer see the default web page. [...]
As previously described it may be normal if the account/site IP was just changed and or if the domain is not resolving to the correct IP address, matching what is in the Apache configuration and also in the applicable DNS zone. In order to properly diagnose the issue it will require direct root access to the system so the configuration may be inspected; I recommend contacting your hosting service provider, data center, or cPanel license provider. If there is any difficulty receiving support you may also contact us directly. Please see the following page for additional details: Support OptionsI have the problem described on this thread.
I did the things proposed and it does not solve the problem.
Can anyone suggest a solution?
Thanks in advance for your time,
This happens when your computer is using cached DNS entries to try to access the domain on an IP that it's no longer being served on and is normal.I just set up a WHM/Cpanel server yesterday after doing it myself for the past 2 years. I had a WHM server for 3 years previous and had minimal issues. Seems to me that this is a fairly large problem for a company who's been in the game this long.
Not happy when I paid $425 for a license for a control panel then need to manually edit httpd.conf and htaccess to get the frikken sites to work correctly.
To setup a new domain this involves configuring both an Apache virtual host as well as a DNS zone; without both DNS and Apache configurations being updated the setup will not be completed. If only a DNS zone is setup, and not the Apache virtual host, then it is expected the default web page will be displayed.I am now having this problem with subdomain I just added via Edit DNS Zone. I added a new CNAME record for an existing domain and it now directs to defaultwebpage.cgi
The main domain and www.domain work fine, but the new one does not.
The DNS zone that was edited looks just like the DNS zone of other domains I have on the same box that have CNAME subdomains listed. Both domains have CNAME only, not a full subdomain as added via user cPanel as I want the subdomain to point to the same folder as www. (my code adjusts for based on the subdomain) and do not need separate space/folder for the subdomain
The domain that was setup before upgrading to 11.25 Release is working fine and has not been edited. The domain edited with 11.25 Release is not.
httpd.conf looks fine for both domains and there is no reference to the subdomains for either account in it.
.htaccess is set on both domains
UserDir is set correctly with the usernames
I checked an external dns tool and it shows the subdomain cname listing is public and available.
The issue is that of DNS being cached; this could take place on the visitor's computer (both by the OS and in the browser), and DNS may also be cached by the visitor's ISP.does anyone know how to force client's browsers, from the server, to clear their cache when a problem like this occurs?
Even though the problem is fixed on the server, end users still see the green cPanel page. And one simply can't tell everyone who visits the website to clear their cache. They simply get the green cPanel page and think the company who's website it is, is out of business.
my domain is working fine with www but without www is redirect to cgi
to resolved this problem only is need to create a .htaccess with one line:
As the system administrator, you may minimize interruption by performing maintenance during periods of the least site activity or lowest server usage, and you may also minimize the time for DNS propagation by adjusting the SOA TTL in the applicable DNS zones at least 24 hours prior to changing the site IP address to reduce the likelihood that the old IP will be retained in your computer's DNS cache for an extended period of time.This all started by simply changing the site's IP address.
cPanel really need to fix this lame method of changing IP address and not putting a better method to do that and redirect people properly where they need to go.
upcp was of course not helpful.
If the authoritative DNS servers, i.e., those registered to an IP address at the domain registrar, are successfully responding to DNS queries for your domain, where the domain can resolve to the correct server IP address, then the web site should be accessible. Please keep in mind that cached DNS records might pose an inconvenience when testing a site after recent DNS changes; this could involve DNS queries cached by your web browser, computer, or ISP being used to test connectivity. Depending on where a DNS query was cached, it may be possible to easily flush the DNS cache and see the effect of recent changes sooner than later; however, if not readily possible in the given circumstances then it may be necessary to allow at least 24 hours for DNS propagation (and to allow time for the cached queries to expire naturally). If the difficulty persists after 24 hours from the time of setup and if you would like more in-depth assistance, you are welcome to submit a complimentary support request so that we can take a look at your existing DNS configuration and determine if there may be any issues.this is my case:
i created my account @ cpanel, added domain names, added subdomains...
checked httpd.conf (i have root access), the conf is fine, all domains listed...
then i set the IP from godaddy dns to my server...
still shown as "default web site page" till now..
and still hoping this will be resolved automatically in a few days
edit: forget to mention, both the server and the domain are new
|Thread starter||Similar threads||Forum||Replies||Date|
|T||Web site down with different domain ssl cert??||Web Servers and Applications||4|
|A||Bulk Redirecting Domain Names||Web Servers and Applications||3|
|I||Domain redirecting to default web page on DigitalOcean||Web Servers and Applications||1|
|R||SOLVED Domains redirecting to default web page||Web Servers and Applications||8|
|A||After Update in Easy Apache, Site redirecting to domain.tld/cgi-sys/default||Web Servers and Applications||1|