• 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.

How to Deploy a Multi-language AI-Generated Blog Using Subdomains and Reverse Proxy Architecture

blondguerra

New Pleskian
Hi everyone,


I'm currently facing a rather complex setup challenge and could use some expert insight.


I'm trying to host an AI-generated multi-language blog structure under multiple subdomains in Plesk (e.g., en.domain.com, es.domain.com, fr.domain.com), where each subdomain fetches pre-rendered HTML content from a headless generation service deployed externally (not inside Plesk). The blog engine is detailed here: BlondGuerra


What I want to achieve:


  • Reverse proxy each subdomain to a different external endpoint (e.g., Vercel, S3, or GCP bucket) from within Plesk.
  • Enable proper caching and GZIP compression via nginx inside Plesk.
  • Maintain SSL via Let's Encrypt for all subdomains with Plesk handling renewal.
  • Avoid PHP or Node on the Plesk server – just serve as proxy and SSL terminator.

I've tried using nginx additional directives in Plesk for each subdomain, but I’m hitting issues with cache invalidation and sometimes unexpected 502 errors. Is there a reliable way to configure this cleanly in Plesk (either via Web Server Settings or through CLI configs that won’t get overwritten)?


Has anyone done something similar or encountered the same kind of hybrid setup?


Any advice or working config snippets would be greatly appreciated!
 
Back
Top