Multi-domain nginx reverse proxy on one VPS
One reverse-proxy host, many sites—common for DMCA-ignore reverse-proxy operators. The hard part is keeping nginx configs from colliding. ShieldProxy namespaces domains on your Self-Managed VPS or on Fully Managed capacity.
Fully Managed
You use shield capacity assigned to your account. Cloudflare stays yours; the VPS is operated as part of the managed plan.
Hostnames are kept unique on that shared capacity so two customers do not claim the same public name.
Self-Managed
You bring the VPS and SSH. The panel installs and updates reverse-proxy sites on your box.
You can invite basic users under your account when your plan allows it—still on infrastructure you own.
Keep reading
- Fully Managed vs Self-Managed Reverse Proxy PlansShieldProxy Fully Managed vs Self-Managed: same DMCA-ignore reverse-proxy panel; different who owns the nginx shield VPS—and who can add team users.
- DIY Nginx Reverse Proxy vs ShieldProxy PanelDIY Cloudflare + nginx reverse proxy to hide origin IP vs ShieldProxy—automate DNS, Origin CA, and teardown for DMCA-ignore and Offshore Hosting shields.
- DMCA-Ignore Reverse Proxy for Streaming & Media HostingDMCA-ignore reverse proxy for streaming and media: Cloudflare + nginx shield in front of your origin. Works with Offshore Hosting or Fully Managed shield capacity—without hosting video on the panel.
- Hide Origin IP with Cloudflare + Nginx Reverse ProxyHide your origin IP behind Cloudflare and an nginx reverse-proxy shield—for DMCA Ignored Hosting and Offshore Hosting setups. What leaks, what to lock, what ShieldProxy automates.
More in Use cases
Explore topics
- GuidesDMCA-ignore reverse proxy, DMCA-ignore VPS vs shield, nginx hide origin IP, Cloudflare Origin CA—for Offshore and Self-Managed setups.
- CompareCloudflare-only vs DMCA-ignore reverse proxy, and DIY nginx reverse proxy vs ShieldProxy automation.
- IntegrationsCloudflare DNS + Origin CA for your nginx reverse-proxy shield—no shared platform Cloudflare login.