• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Browse by IP behavior

G

Gorgon@

Guest
Hi folks,

I've noticed a behavior and I'm curious if anyone knows how or why. I have a site setup with it's own exclusive IP. I have done this several times for other customers. Some of the customers with exclusive IPs can be viewed by using the IP in the URL:

http://XXX.XXX.XXX.XXX

and I get their content. But with other exclusive IP sites, the IP URL gives me the default plesk page.

When looking at the httpd.include file in /etc/httpd/conf, I see that the sites where the IP URL works, the Include statement for their site specific configuration is at the top of the file. But for the sites where the IP URL does not work, the Include statement for their site specific configuration is at the bottom of the file. For example, httpd.include looks something like this:

  • NameVirtualHost declarations
  • Some IfModule and Directory statements
  • First round of Includes to site configurations
  • VirtualHost statements
  • Second round of Include statements (the majority of them)
  • VirtualHost statements for redirects

Now if I edit httpd.include and move the site in question to the first round of Includes, it all works great. But this isn't a fix b/ Plesk will overwrite this file eventually.

So, why are their 2 sets of Include statements? Shouldn't all of the exclusive IP sites be at the top so they'll 'override' the default settings? Can anyone suggest a fix for this? Maybe setting a new 'default' in the sites vhost.conf file?

As far as I can tell this working as expected until I upgraded to 7.5.3. But maybe there is some sort of 'limit' that's not documented.

Any pointers are greatly appreciated.

Thanks,
mikeS
 
Back
Top