• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

exclusive IP default plesk page and httpd.include

G

Gorgon@

Guest
Hi folks,

Running v7.5.4 on RHEL4.

I know I've seen this before and for the life of me, I cannot remember how to fix it.

I had a site which initially was using a shared IP. I added an exclusive and then assigned it to this site. We need to access this site by the IP address for a short while so we cannot make use of host headers here.

When we try to access the site via IP, we get the Plesk default page; the one when it does not know what to do with the domain name since it's lacking host headers.

Now if I edit /etc/httpd/conf/httpd.include and move the line:

Include /var/www/vhosts/baertmarine.com/conf/httpd.include

To a section near the top and reload apache, the site comes up fine. But as you know this is not a fix since the master httpd.include file gets rewritten by plesk.

I've checked the local httpd.include file and it's all correct. For some reason, the postion of the Include directive causes plesk to see things incorrectly.

As I mentioned, I'm pretty sure I ran across this before and fixed it. I've gone through forums again but was not able to find the answer.

Does this sound familiar to anyone? Any suggestions?

Thanks,
mikeS
 
More info: a breakdown of /etc/httpd/conf/httpd.include.

1) Starts off with the NameVirtualHost declarations

2) Next some <Directory> statements, logging, etc.

3) First round of Include statements. All of these sites have an exclusive IP.

4) Next is a VirtualHost statement that sets up the default. This statement applies to all IPs assigned to the server (shared or exclusive). This is the page displayed if the Host Header doesn't match, etc, etc.

5) The next section is pretty big. Like above, it defines VirtualHost blocks but this time for port 443 for all of the IPs. This is the page displayed if the Host Header doesn't match for SSL, etc, etc.

6) Next block defines the webmail section for all sites. First for port 80 then for port 443.

7) Next block defines the mailman section for all sites. First for port 80 then for port 443.

8) Now we get into the section where there is an Include statement for each of the sites on this server; except for the handful that are in section #3. Note, that some of these have exclusive IPs too, though most use a shared IP.

9) The last section is for sites that are redirects.

10) End of /etc/httpd/conf/httpd.include


Okay, that being said, here is the problem we're seeing again.

When I originally added the site, it's Include statement was in section #8. Not unusual. I changed its IP from share to exclusive and the Include line stays where it is. Still not unusual. I have exclusive sites in section #8 that work fine.

Yet when I go to the exclusive IP in a browser, I get the default plesk page. Very strange.

If I edit /etc/httpd/conf/httpd.include and move the site's Include statement from section #8 to section #3, and reload Apache, everything works!!!!

Why does it matter where the Include statement is in httpd.include? Why do some exclusive IP sites seem to need to be in section #3 while others work fine in section #8?

As I mentioned in my original post, I cannot manually move the the Include statement to section #3 b/ Plesk will overwrite httpd.include the next time a site is added/removed, etc.

Anyone see something like this before? Am I just being a dummy here an missing the obvious?

Thanks,
mikeS
 
Lol,

This is the same problem that we are having. Plesk will go in and fix it, but not tell us what we need to do to fix the problem.

We are still researching it and have a trouble ticket open. Maybe one day a Plesk rep could chime in and see what we are doing wrong.

Dedicated IP setup for the domain, but still defaults to the plesk home page.
 
I guess I should note that this is Plesk version 8.2.1 on CentOS / latest apache.
 
Back
Top