After discovering the exact problem in this case, the request headers being too large because ServerSideRender sending too many attributes in a GET request, I opened a ticket on the Gutenberg development repository proposing a few possible solutions for this issue. And the issue had actually already been addressed because I wasn’t the first one … Read more
Your server does not have mod_rewrite enabled Or you do not have AllowOverride set correctly to allow your .htaccess file to operate correctly. You will need AllowOverride set to at least FileInfo. I’d bet on the latter, as mod_rewrite is pretty ubiquitous. Based on your edit, the issue is that Nginx doesn’t use .htaccess files. … Read more
Ok some wise guy deleted my last post. The answer, which the above member (@etc) gave to me on another forum, and is working quite fine, is as follows: # Rewrites for Bedrock Multi-Site Subdomain Setup rewrite /wp-admin$ $scheme://$host$uri/ last; rewrite ^/(wp-.*.php)$ /wp/$1 last; rewrite ^/(wp-(content|admin|includes).*) /wp/$1 last; He revised his answer but did not … Read more
Create a file specifically for W3 Total Cache configuration for your site, in a location Nginx/PHP-FPM can write to. Include this file in your site’s Nginx server configuration. Then on the General Settings page, under Miscellaneous provide the full path to this file in the “Nginx server configuration file path” field. W3TC will then know … Read more
I ended up changing location ~ ^/.*\.php$ { try_files $uri = 404; fastcgi_pass unix:/var/run/php5-fpm.sock; fastcgi_index index.php; include fastcgi_params; } to location ~ ^/.*\.php$ { try_files $uri $uri/ /index.php?$args; fastcgi_pass unix:/var/run/php5-fpm.sock; fastcgi_index index.php; include fastcgi_params; } It now works, but I feel that is a security issue now.
Sounds like your expires headers are set to far in the future. The following rules can be added to your .htaccess Expires rules can be added to your Nginx server file to shorten the expires time down to 180 seconds. location ~* \/[^\/]+\/(feed|\.xml|.html|.HTML)\/? { expires 180; } I would also suggest installing the Nginx Proxy … Read more
Both servers are listening to the same port. You have Nginx set to listen to 80 and nothing is set for Apache unless it’s in your ports.conf. Your also proxy passing to Apache port 80 in your Nginx conf. In the Nginx conf change proxy_pass http://127.0.0.1:80; to proxy_pass http://127.0.0.1:9000; change listen XXX.XXX.XXX.XXX:80; to listen 80; … Read more
It turns out that the nginx config that W3 Total Cache inserts if Disk Enhanced mode is enabled will break permalinks, but only if you restart nginx after W3 Total Cache injects the config for Disk Enhnaced mode. Based on birgire’s suggestion, I turned off all plugins and checked the site, which started working correctly. … Read more
From doing some research, I’d recommend trying out this plugin: Redirection. This plugin allows you to manage 301 redirections. I played around with the settings and they allows regular expressions which could do the following: http://some.site/hashtag?tag=some-tag/ to http://some.site/tags/some-tag/ They provide documentation on how to set it up which can be found here. This is what … Read more
WordPress tries to detect the webserver’s type by peeking into the global $_SERVER[‘SERVER_SOFTWARE’] variable. The Apache check is: $is_apache = (strpos($_SERVER[‘SERVER_SOFTWARE’], ‘Apache’) !== false || strpos($_SERVER[‘SERVER_SOFTWARE’], ‘LiteSpeed’) !== false); and the Nginx check is: $is_nginx = (strpos($_SERVER[‘SERVER_SOFTWARE’], ‘nginx’) !== false); You should therefore first check out: var_dump( $_SERVER[‘SERVER_SOFTWARE’] ); to see if it’s correct. Here … Read more