“squat” is synonymous with “nothing” in this case. So, I’d say: Before you consider using nginx, be aware that PHP APC or a similar opcode cache with a WordPress caching plugin is going to offer significant performance improvements over just switching from Apache to nginx. If you aren’t already using a PHP opcode cache and … Read more
I experienced something similar few months ago. After a long time debugging I found out that all the problems were related to this well hidden option called: ms_files_rewriting in the wp_sitemeta table. It was active in my case, with the value 1. When active, WordPress assumes you want to use the deprecated blogs.dir structure, where … Read more
302 redirect to signup with nginx reverse proxy
how do I configure nginx for wordpress multisite, it occurs ERR_TOO_MANY_REDIRECTS
Here is what I ended up doing: // Set disable cache for certain roles add_action(‘init’, ‘add_custom_cookie_admin’); function add_custom_cookie_admin() { if ( is_user_logged_in() ) { $current_user = wp_get_current_user(); $thisrole = $current_user->roles[0]; if($thisrole !== ‘subscriber’) { setcookie(“disable_cache”, $current_user->user_login, time()+43200, COOKIEPATH, COOKIE_DOMAIN); } } } // and then remove the cookie on logout function clear_custom_cookie_on_logout() { unset($_COOKIE[“disable_cache”]); setcookie( … Read more
You should look in WordPress Codex page related to Nginx. It’s best manual for configuring nginx for wordpress I’ve seen over the internet.
I solved the problem by upgrading the way files are uploaded and displayed to the new WordPress 3.5 method. A more detailed tutorial can be found at http://halfelf.org/2012/dumping-ms-files/ but the basic steps are as follows: Move images from blogs.dir/#/files/ to /uploads/sites/#/ Change WordPress settings so it doesn’t look in /files/ but in /uploads/sites/#/ In .htaccess … Read more
Ok found the answer. You need to put this directive above the location: location ~ \.php$ { include snippets/fastcgi-php.conf; fastcgi_pass unix:/run/php/php7.0-fpm.sock; } The order apparently matters inside the nging conf file.
The problem happens because of the way AWS ALB works, or at least the way mine is setup (which seems to be quiet common practice to be fair), the Loadbalancer listens on HTTPS:443 and forwards to the target HTTP:80. The problem above err-too-many-redirects is related to an endless loop created by the target application. The … Read more
I figured out how to fix my problem. In my nginx config file (/etc/nginx/nginx.conf) I added client_max_body_size 100m; at the end of the #Basic Settings in the http {} section. I hope this answer will help some of you and please tell me if there is any better solution to this problem.