-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Naxsi or Proxy_Cache causing issues with ManageWP for WordPress #32
Comments
I noticed these hits in my
|
@AnoopAlias This is a pretty major issue for me so I hope you can SSH in and help me get this resolved once you get to your desk! Thanks! |
@brianjking learning=1 in the NAXSI_FMT: log entry tells that NAXSI is just logging this up and doing no blocking etc. You should use the default proxy (not caching ) as caching proxies can cause issues without a sufficient cache_purge logic . By default nginx will not cache dynamic pages (pages with cookies etc) but some plugins etc may remove cookies etc and trick nginx into caching . If you need high performance and the app is wordpress. use PHP backend and use the High performance wordpress template. https://support.sysally.net/projects/ndeploy/wiki/High_Performance_Wordpress_setup This does caching in fastcgi( rather than proxy) and has the cache_purge logic because of the nginx-helper plugin loaded in wordpress |
@AnoopAlias I switched to httpd + wordpress firewall, however, it's still showing the same details for the proxy configuration. I can't seem to get the reset option to appear... |
@brianjking please pass on the servername/main ip and the domain having issue at support@sysally.net . |
@AnoopAlias Sent. I'm on Skype if you would like to chat as well. |
ndeploy_watcher service was not running causing the config generation to fail. |
Hello,
I have used ManageWP (http://managewp.com) for years, even while using nDeploy and 99.9% of the time it works great with and without nDeploy.
However, it appears that either Naxsi or Proxy_Cache when using the PROXY backend setup is causing ManageWP to report a 503 error when attempting to connect to the sites on my server.
Please help!
The text was updated successfully, but these errors were encountered: