Reverse Proxy Setup

Last Updated -


Pagely can support reverse proxy setups on single instance WordPress sites (non multisite) for VPS and Enterprise level plans for an additional $200 a month subscription fee. This is to account for the added support costs associated with ongoing debugging, that wouldn't happen when directly pointing DNS records to Pagely.

At this time we only support IPv4. While our network can communicate with IPv6 endpoints, the X-Forwarded-For headers must contain a valid IPv4 address in order to be logged correctly. Otherwise, the IP of the remote proxy server may be logged instead of the real IP of the requestor.

Reverse proxy setups are ideally suited for sub-directory access to a WordPress installation on the same domain and not an external domain. The setup you'd typically see with a reverse proxy would be blog.example.com resolving to example.com/blog.

Note: Since WordPress installations reside at the top level of the web root, you'll see the domain listed in our system as blog.example.com. Content will be served from example.com/blog.

Before we start configuring your reverse proxy, we must first obtain enough information about the remote endpoints you will be sending traffic from in order to ensure it will be viable. The most common and easiest scenario is if you have a static IP address or IP address range on the other end that you can easily obtain and share with Pagely. Besides source IP information, the web server or content network being used can also impact viability of a properly working reverse proxy configuration:

Solution Complexity Supported Fee Required
NGINX Low Yes Yes
Sucuri Low Yes No
CloudFlare Low Yes No
CloudFront Medium Yes Yes
NodeJS Medium Varies Yes
F5 Medium Yes Yes
EZOIC High No N/A
Akamai High Yes Yes


VBurst-2 plans must first upgrade to VPS-1 or higher in order to use any of the reverse proxy configurations listed below where the fee is listed as required.

Note: There may be additional fees if there are multiple types of proxy configurations required. If you are looking to set up multiple sites but using the same reverse proxy implementation, this counts as a single fee. However, if you have two sites with two different types of remote endpoints, the fee would be assessed individually. Please contact support if you're not sure.

If the solution you are intending to use is not listed above, please contact our support team in advance to discuss further.

Setting it up requires manual setup on our end, so a support ticket needs to be submitted in order to get it working properly.


Required information

We will need from the Proxy doing to forwarding:

  • The solution you are using on the other end.
  • The "X-Forwarded-For" headers has to be passed with visitors real IP.
  • The "X-Forwarded-Proto" headers has to be passed to send http/https information.
  • The single IP address or all the IP addresses CIDR blocks that will be proxying the traffic.

These 2 headers and IP's sending the traffic are required, or it will not work.

The ticket should contain:

  • Confirmation X-Forwarded-For is forwarding the visitors IP
  • Confirmation X-Forwarded-Proto is sending the correct protocol.
  • A list of the IP or all IP's that will be sending traffic.
  • Which WordPress blog is to be forwarding & if it's to a subdirectory or not.
  • (If something isn't working, the full config contents of the reverse proxy helps us debug the issuer quicker)

Otherwise our rate-limiting that blocks spamming & abusive requests will detect that all traffic is coming from a single IP and will block it. So no visitors will be able to visit the blog if it is not setup correctly.

Example Nginx config for a proxy doing the forwarding:

  • Use case is a sub-directory WordPress install like: http://example.com/blog
location /blog {
	proxy_set_header X-Real-IP $remote_addr;
	proxy_set_header X-Forwarded-Proto $scheme;
	proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
	proxy_pass $scheme://52.0.102.250;
}
  • Red text being the existing domain with the subdirectory that will be proxied.
  • Blue text being the Pagely IP of were traffic is to be forwarded to. (Or the VPS IP)

Related Topics

  • Reverse Proxy Setup
    Pagely can support reverse proxy setups on single instance WordPress sites (non multisite) for VPS and Enterprise lev...

Pagely is the Managed WordPress Hosting Platform designed to exceed the needs of media, business, and Enterprise customers alike. We help the world's biggest brands scale WordPress.

Copyright © 2006-2016 Pagely, Inc. All rights reserved.
Pagely® and WordPress® are registered trademarks.

Pagely
Powered by Zendesk