• The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    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. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Problems with accessing domains from localhost

eveslage

New Pleskian
After upgrading to 11.5.30 on my Ubuntu 12.04.2 i have problems to access the domains from a shell on localhost.

the command called from a shell where the websites und plesk are hosted:

curl http://sub.domain.tld

always return the default plesk webpage. the same command from a different host presents the proper webpage.

Any ideas to fix this problem? i need this to trigger some updates through cron on the host.
 
i digged a little deeper and found the problem:

the vhosts config files for the different domains have sections for <VirtualHost PUBLIC_IP:7080> but not for <VirtualHost 127.0.0.1:7080>

when you manually add this section as a copy of the section with the public IP, then the access to the virtual hosts from localhost works again. but the manual edit only holds until the files are regenerated.
 
Can anybody confirm this problem? it would be nice to find out if there is something broken in Plesk generally.
 
If you know public server IP, then why not just use:

# curl --interface PUBLIC_IP http://sub.domain.tld

It's a little inconvenient, yes, but surely solves the problem.

Also, if you're using nginx, why are you concerned with Apache port?
 
This helps with curl. But sone web apps like specific wordpress plugins rely on the access to the domain from localhost. there i can't change the sourcecode.
is this a new problem with plesk 11.5? or am i the only one with the problem? can anybody please check his server installation?

i am not concerned with apache ports. but this is the way to teach apache to listen on localhost for the vhosts. nginx is only a proxy to channel the traffic from port 80 to port 7080 of the apache.
 
i just installed MU #13. Still no resolution for my problem. why isn't there an official statement.

the webserver config is broken und the parallels support team doesn't even show any interest.
 
Back
Top