Title: Problem purging cache when website behind reverse proxy
Last modified: May 23, 2024

---

# Problem purging cache when website behind reverse proxy

 *  [redwiregareth](https://wordpress.org/support/users/redwiregareth/)
 * (@redwiregareth)
 * [2 years ago](https://wordpress.org/support/topic/problem-purging-cache-when-website-behind-reverse-proxy/)
 * Hi,
 * My client’s website is accessed via a reverse proxy. Consequently there are two
   domain names in use:
    - External domain name (users and the plugin see) e.g. [http://www.mywebsite.com](http://www.mywebsite.com)
    - Internal domain name (Varnish sees) e.g. internal.mywebsite.com
 * The plugin is trying to purge the external domain name, however due to the reverse
   proxy directing traffic to the server, Varnish is a caches pages with the internal
   domain name. Consequently the plugin cannot purge the cache as the domain name
   is incorrect.
 * Would it be possible to update the plugin so that we can set an alternative domain
   name via a constant?
 * Thanks,
 * Gareth

The topic ‘Problem purging cache when website behind reverse proxy’ is closed to
new replies.

 * ![](https://ps.w.org/varnish-http-purge/assets/icon-256x256.png?rev=3027185)
 * [Proxy Cache Purge](https://wordpress.org/plugins/varnish-http-purge/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/varnish-http-purge/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/varnish-http-purge/)
 * [Active Topics](https://wordpress.org/support/plugin/varnish-http-purge/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/varnish-http-purge/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/varnish-http-purge/reviews/)

## Tags

 * [reverse proxy](https://wordpress.org/support/topic-tag/reverse-proxy/)

 * 0 replies
 * 1 participant
 * Last reply from: [redwiregareth](https://wordpress.org/support/users/redwiregareth/)
 * Last activity: [2 years ago](https://wordpress.org/support/topic/problem-purging-cache-when-website-behind-reverse-proxy/)
 * Status: not resolved