new account domains will only show CWP Test page

I have been searching for a solution, found a few but nothing helped.

I have installed a clean server with CWP, when I create an account with a domainname, the domain wil keep showing the default test page.

But when I add a second, third or ... any number of extra domains and point them to the directory, they do work?

So main accounts domains will show test page
added extra domains pointed to the public directory do work and show the website.

I have been looking, any help on this would be greatly appreciated.

try to delete index.html file

Thank you for your reply,

I did remove the index.html files early on, problem persists.

Where could I check the file locations of the account domains? The added domains are quite easy to delete and reset in the UI but they seem to work ok.

Domain account is located at path

Code: [Select]

/home/yourcwpusername/public_html/The test page for each domain is located at

Code: [Select]

/home/yourcwpusername/public_html/index.html
You can change the default appearance by editing the file

Code: [Select]

/usr/local/cwpsrv/htdocs/resources/admin/tpl/new_account_tpl

Thank you for your reply.

However the problem is, there already is no index.html anymore, I've already removed it.
But the main domain is still showing the default page.

example:

I have a main account with a domainA and created 2 extra domains (DomainB and DomainC) all pointing to the same website/directory.

DomainA -> shows default page, no matter what I do it keeps showing the default page.
DomainB & DomainC -> shows the website I have installed.

Where can I find the Apache config for the main domain? Been looking but not finding. Why is it so easy to edit extra domains but not the main account domains.

Ok, found the settings and they are correct. The domain points to the exact same directory as the extra domains.

It looks like some kind of caching is causing this?

Another update.

So after testing and some trail and error, deleted an account and recreated it.

Now I noticed HTTP requests do work and show the webpage. however some main account https domains stil show the default page (while the http version does work).

Almost ready and done to try a complete reïnstall or just go back to DA.

ps: I have a CWP pro account.

probably dns delay that will fix itself in a few days

Did you manage to solve?
I've been here for 10 hours looking for a solution.

The site opens without https

http://judaismonazareno.org

With https goes to Test Page
https://judaismonazareno.org

@nzmjunior try to restart WEB servers you use (Apache, nginx, varnish).

I have the same issue. How to restart nginx or Apache?

Make sure you don't have varnish or your browser cached the old files.

You will always see the default page but after creating a website in the public_html folder you really should see your page.

Delete cached items in your browser and also restart varnish if used and CWP Cache on dashboard so you really get the actual site.

On Chrome you can open the dev console and right click on the refresh symbol beside the address bar and select hard refresh.

Hello,
I faced that issue many times using CWP PRO. It is not a CWP issue. CWP works great and the updates are fantastic. My issue was with CloudFlare where I had not properly setup the accounts SSL so the /index.php was working fine with CloudFlare's Flexible SSL.

The problem was when I used CloudFlare's Full SSL.

Hello,
I faced that issue many times using CWP PRO. It is not a CWP issue. CWP works great and the updates are fantastic. My issue was with CloudFlare where I had not properly setup the accounts SSL so the /index.php was working fine with CloudFlare's Flexible SSL.

The problem was when I used CloudFlare's Full SSL.

Damm even I am having a similar kind of issue, I have searched all over the internet and even have posted on number of threads on different forum, no solution seems to work. I am really frustrated, can anyone of you here help me resolve this issue, I am very much tired now.

If you are facing any related issues like this, just know that it is DNS propagation on process. If you configure your DNS well, just have a little patience. Just make sure that your NS and IPadress is pointed that your server