Question Subdomain showing default Plesk page

[marvin]

Server operating system version

Centos 7

Plesk version and microupdate number

Plesk Obidian 18.0

I have a static HTML page set up as a placeholder while I'm developing a CMS-enabled site so that the client can edit content as required.

I've set up a subdomain for the new site (new.clientdomain.com) and uploaded my content into my main httpdocs directory. I've set up new database and linked to site.

I thought I'd covered all the bases:

• .htaccess files in place pointing to index.php
• Domain register includes wildcard (*.clientdomain.com) that points to VPS IP address
• Domain register also includes specific record (new.clientdomain.com) that points to VPS IP address

I'm still seeing the default Plesk page.

Are things in the wrong place? Have I missed anything?

First time I've set this up as a Subdomain in Plesk... ??

 

[kpushkarev]

Not sure if I understood what are you trying to do. Please provide more information about your directory tree and configs (.htaccess).

Did you put the files into the correct directory? A subdomain has its own document root. You can find it by opening your subdomain's file manager in Plesk.

 

[MarkM]

So with a default page, that generally indicates DNS is correct, and it's an apache config issue. First thing I would do is restart apache. If that doesn't work, I would run "plesk repair web" as explained here; Plesk Repair Utility: Web which will rebuild the configuration.

 

[marvin]

Hi people, back again to try to resolve this:

@kpushkarev -- at the moment I have everything in the /httpdocs/ directory. The CMS I am using is Silverstripe. A .htaccess file in the root directory (httpdocs) points to a /public directory where resource files for the installation are kept. Are you saying I should have a sub-directory with the Silverstripe CMS install within /httpdocs/?

@MarkM -- I've restarted Apache and run 'plesk repair web' utility. This fixed an issue I was unaware of (great!) but sorry to say it didn't fix the issue. Still seeing default Plesk page.

 

[marvin]

Interesting. I reviewed things in Plesk interface and can see new.clientdomain.com with all my files inside it. Database is pointing to this web address. I can't see this directory in my FTP client?

And now I'm getting a 500 error... ??

 

[marvin]

According to my logs:

AH00124: Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace.

 

[kpushkarev]

I suggest a simple check if requests are routed correctly. Put some static file like test.txt on new.clientdomain.com, then request it with the curl -v command and post the result. Also, post how this request will be reflected in Apache and nginx logs.

 

[Peter Debik]

AH00124: Request exceeded the limit of 10 internal redirects due to probable configuration error.

A typical symptom for mismatches in configuration between webserver, .htaccess configuration or other locations in the website that define the URL where the website is located. For example, if you have set a specific spelling in Web Hosting Settings (e.g. always use www. type spelling of URL), but in .htaccess you redirect to the non-www type spelling of the URL, requests will end up in infinite ping-pong-loops. The same applies to http/https configurations. A first step to resolve it is to set the web hosting configuration to no preferred domain spelling.