NGINX serve WordPress from sub-path fails with 404, how to fix?
You can try location /review-ci { index index.php; try_files $uri $uri/ /review-ci/index.php; }
You can try location /review-ci { index index.php; try_files $uri $uri/ /review-ci/index.php; }
Showing another posts on Archive custom post type page
place this in the nginx tab of mamp pro under the try files: $uri $uri/ /index.php?q=$uri&$args;
Check your rewrites to make sure it follow this if (!-e $request_filename) { rewrite ^/[_0-9a-zA-Z-]+(/wp-.*) $1 last; rewrite ^/[_0-9a-zA-Z-]+.*(/wp-admin/.*\.php)$ $1 last; rewrite ^/[_0-9a-zA-Z-]+(/.*\.php)$ $1 last; } not this if (!-e $request_filename) { rewrite /wp-admin$ $scheme://$host$request_uri/ permanent; rewrite ^(/[^/]+)?(/wp-.*) $2 last; rewrite ^(/[^/]+)?(/.*\.php) $2 last; }
Try separating the second location block: location /blog { alias /var/www/wordpress-site/; try_files $uri $uri/ /blog/index.php?$args; } location ~ \.php$ { fastcgi_split_path_info ^(/blog)(/.*)$; include snippets/fastcgi-php.conf; include fastcgi_params; fastcgi_pass unix:/var/run/php/php7.2-fpm.sock; fastcgi_param SCRIPT_FILENAME $request_filename; } Hope this helps!
Everytime I’ve seen the thing you’re describing it was due to the browser having the redirect cached. I can’t see any reason that different browsers would behave differently in this case. You may want to try a browser/machine you haven’t used before to access this site as this will show you definitely what’s happening. You … Read more
Nginx tries the wrong file when http_cookie matches logged_in
Cannot access wp-admin without trailing slash – .htaccess configuration for WordPress behind a nginx proxy
Fixing WordPress’s Bug (failed to send buffer of zlib output compression) results in “White Screen of Death”
ERROR: No such service: nginx when building wordpress with docker [closed]