Plugin Inconsistent with NGINX Reverse Proxied to Apache
Does anyone have problems with this awesome plugin when running on NGINX as a reverse proxy? It runs really well on Apache, but there seems to be a confusion when running NGINX on the front end. I’m also using w3tc as well. It seems to work on Apache servers, but with an NGINX frontend, the performance is mixed. I’ve disabled caching through NGINX, it worked for a while, now it doesn’t.
AMTS 1.5 (pro)
I’m using the old WPTap with W3TC user agents enabled, it works for now. I just love the flexibility of AMTS.
- The topic ‘Plugin Inconsistent with NGINX Reverse Proxied to Apache’ is closed to new replies.