If your website is hosted using NGINX, you can proxy requests from your domain (e.g. yourdomain.com/partner-ecosystem/) to your PartnerPage-hosted directory while keeping the user on your own domain.
This guide shows how to proxy a specific path and forward the necessary headers for PartnerPage compatibility.
✅ Requirements
Your web server is running NGINX
You want to proxy a path like /partner-ecosystem/... to your PartnerPage directory
Your know your PartnerPage base URL (e.g. https://<your-id>.directory.sites.partnerpage.io or <yourcompany>.partnerpage.io)
1. NGINX Reverse Proxy Configuration
Add the following block to your NGINX configuration file (usually in /etc/nginx/nginx.conf or a site-specific config inside /etc/nginx/sites-available/):
location ^~ /partner-ecosystem/ {
proxy_method GET;
proxy_set_header PartnerPage-Client-IP $remote_addr;
proxy_set_header PartnerPage-Reverse-Proxy "true";
proxy_set_header Host <your-partnerpage-subdomain>.directory.sites.partnerpage.io;
proxy_ssl_server_name on;
proxy_pass_request_headers on;
proxy_pass_request_body on;
proxy_pass https://<your-partnerpage-subdomain>.directory.sites.partnerpage.io;
}Make sure to replace all instances of
<your-partnerpage-subdomain>.directory.sites.partnerpage.io
With your actual PartnerPage domain (you can find this in your PartnerPage admin or onboarding instructions).
2. Review your configuration
To successfully set up a reverse proxy with NGINX, ensure:
✅ You configure a location block for the relevant path (e.g. /partner-ecosystem/)
✅ You use proxy_pass to route traffic to your full PartnerPage domain
✅ You set these headers:
PartnerPage-Client-IP
PartnerPage-Reverse-Proxy
Once deployed, your users will see your PartnerPage content at a branded path on your domain, with no redirects or loss of functionality
Need help configuring NGINX? Reach out to PartnerPage support.