• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Plesk in a clustered environment with shared storage

RandellO

New Pleskian
We're trying to use Plesk in a clustered environment with multiple web nodes pulling static content and apache configuration from shared storage. We can make Plesk update the config files on the shared volume. However, Plesk creates virtual host containers for each domain or subdomain tied to a specific IP. Since each web node would be listening to its own IP, we need a way for Plesk to create virtual host containers that will be seen and read by the web nodes (possibly by using wildcards?). For example, web node 1 is listening on IP1 and web node 2 is listening on IP2. If we create a new domain in plesk, it'll have a virtual host container associated with, say, IP1. We need a way for it to associate the virtual host directives with IP2 so web node 2 can read its contents too. Is there a way to do this?
 
Using Wildcard IPs

Thanks, Igor.
Is there a way to use vhost.conf or another method to get Plesk to use wildcards in Virtual Host contaners? So instead of creating <VirtualHost 123.123.123.123:80> it'll create <VirtualHost *:80> or <VirtualHost 123.123.123.*:80>?
 
Back
Top