Late to the party but if anyone finds this as a result of a search. this will have been auto-created when you installed Ithemes security. By default, it will create an Nginx.conf file in the site public_html folder you can change the location of this file in the settings. If it is on apache it … Read more
No, sorry, that isn’t going to be possible. Assuming the user connects to your server at https://www.sub.domain.com with HTTPS, the sequence of events will be: the user’s client makes a connection and initiates an SSL negotiation; they will send SNI (= server name indication) that they’re connecting to www.sub.domain.com the server can use the SNI … Read more
The nginx equivalent of RewriteCond %{REQUEST_URI} ^.*wp-content/uploads/restricted/.* RewriteRule ^wp-content/uploads/(restricted/.*)$ dl.php?file=$1 [QSA,L] will be the location ~ ^/wp-content/uploads/(?<file>restricted/.*) { rewrite ^ /dl.php?file=$file last; } If you want to apply this to several folders under /wp-content/uploads, use location ~ ^/wp-content/uploads/(?<file>(?:restricted1|restricted2|restricted3)/.*) { rewrite ^ /dl.php?file=$file last; } I don’t think there can be any other solution for nginx … Read more
You should use the ^~ prefix on the location statement, change the alias statement to root /var/www;, and change the last parameter of the try_files statement. For example: location ^~ /blog/ { autoindex on; root /var/www; index index.php; try_files $uri $uri/ /blog/index.php?$args; location ~ \.php$ { include snippets/fastcgi-php.conf; fastcgi_param SCRIPT_FILENAME $request_filename; fastcgi_pass unix:/var/run/php/php7.4-fpm.sock; } }
When you use W3TC with Nginx, it wants to write a nginx.conf file into your server root, do you have that file in place, writable by the nginx user? Also, did you add an include directive in your primary nginx config to pull that file in? For example, in my /etc/nginx/sites-enabled/dougal.gunters.org config file, I’ve got … Read more
Sometimes a plugin changes WordPress’ internal rewrite rules during an update, an installation or deactivation. If the plugin’s update happens to run after your taxonomy registration it may just wipe out the custom rules for the taxonomy. To inspect the currently active rewrite rules use the plugin Monkeyman Rewrite Analyzer. See this answer for details. … Read more
Based on your comment, here’s the solution for an Nginx-Apache stack with “disk: enhanced” page cache method in W3 Total Cache plugin… location / { error_page 418 = @cachemiss; recursive_error_pages on; if ($request_method = POST) { return 418; } if ($query_string != “”) { return 418; } if ($request_uri ~* “(\/wp-admin\/|\/xmlrpc.php|\/wp-(app|cron|login|register|mail)\.php|wp-.*\.php|index\.php|wp\-comments\-popup\.php|wp\-links\-opml\.php|wp\-locations\.php)”) { return 418; } … Read more
I received a response with code that fixed the issue from rtcamp.com Add this code to the nginx site configuration for the domain has the issue with not all 404 requests being handled by WordPress: if (!-e $request_filename) { rewrite ^/(.+)$ /index.php?q=$1 last; }
WordPress doesn’t care much about IP address, it is mostly sensitive to domain name it is accessed by. In your case you can access the test site if you make your local machine resolve domain to its IP (ignoring “actual” IP DNS would resolve it to). You can accomplish that with hosts file or software … Read more
Changing proxy_set_header Host $host; to proxy_set_header Host $http_host; fixed the issue. (source)