I was finally able to get this to work by using php5-fpm instead of php5-cgi. First I removed the php5-cgi package via sudo apt-get autoremove –purge php5-cgi Then I installed php5-fpm via: sudo apt-get install php5-fpm After tweaking my server definition in Nginx a bit, the problem went away. Update I suspect this had more … Read more
The difference between mainline and stable is explained here: NGINX 1.6 and 1.7 Released A graphical summary: Among other differences: Note that stable does not mean more reliable or more bug-free. In fact, the mainline is generally regarded as more reliable because we port all bug fixes to it, and not just critical fixes as … Read more
sudo nginx -s stop && sudo nginx
we found the solution: There were deleted Pages and/or Posts with the same title. We removed them and now everythings works!
You don’t. That’s the simple answer, anyway — you don’t need it. uWSGI is itself a capable server. However, other servers like nginx have been around longer and are (probably, anyway) more secure, as well as having additional features not supported by uWSGI — for example, improved handling of static resources (via any combination of … Read more
Well, these two directives are slightly functional different because you do not use exact match in the latter case. So, /robots.txt1111 will match your second location too. location =/robots.txt { root /home/www/static/; } is an exact functional equivalent of your first directive.
Remove ‘/m’ from ‘/m/index.php?$args;’
First, you shouldn’t use root directive inside the location block, it is a bad practice. In this case it doesn’t matter though. Try adding a second location block: location ~ /some/path/(?<section>.+)/index.html { proxy_pass http://192.168.1.24/$section/index.html; proxy_set_header Host $host; } This captures the part after /some/path/ and before index.html to a $section variable, which is then used … Read more
You should try the Rewrite plugin as mentioned in this post “Nginx rewrite rule conflict with WordPress permalinks rule“, it could help solve the issue. If not, we’ll have to dig deeper, let me know.
Old question, but the issue is because the parent location is a regex location while the nested locations are prefix locations. When a parent location is defined by a regex, any nested locations must also be defined by regexes: location ~ ^/(a|b) { location ~ ^/a { … } location ~ ^/b { … } … Read more