• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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