• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Question Can vhost template in Plesk be configured to wildcard IPs?

GrZeCh

New Pleskian
Server operating system version
CentOS Linux 7.9
Plesk version and microupdate number
18.0.56
Hello,

I'm planning to put my Plesk installation behind pfSense firewall where pfSense will hold external current Plesk IP and perform NAT translation on pfSense and pass traffic to Plesk using local IP address. I wanted to make nice transition and move all vhost configuration from specific IP address (external one) to have vhost handle traffic to all IPs (*:80 and *:443) and my question is:

Can vhost template which Plesk is using be updated to use:

Code:
<VirtualHost *:80>

and

Code:
<VirtualHost *:443>

instead of specific IP address?

Whenever I've tried to modify one website configuration on:

Code:
/var/www/vhosts/system/SOMETESTWEBSITE/conf/httpd.conf

to use *:80 I can't access website data and default Plesk website is being shown (from /var/www/vhosts/default/htdocs).

Thanks
 
Back
Top