• 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!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • 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.

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