• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

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