Search results

I have noticed that the default installation of Plesk came with tls v1 and tls v1.1 activated by default. In /etc/nginx/conf.d/ssl.conf, I deleted the text related to those TLS so, now i have: ssl_protocols TLSv1.2 TLSv1.3; I guess that if we turn off ssl_prefer_server_ciphers, it should...

I just wanted to say that I get the same results to display a wordpress page. FastCGI delivers content faster thant php-fpm. Additionnally, I have noticed that the pageload when using fastcgi was more stable than when using php-fpm. UFHH01 said it was useless to use an apache benchmark test on...

I wanted to share a very bad thing that I found in my log today. A modsecurity rule of OWASP (WAF) was triggered on visits of Googlebot. I mean come on, if OWASP is not able to make the difference between an attacker and Googlebot, it makes no sense to install OWASP. This is really something...

I have found that my ttf files were returned with mime type octet-stream instead of font/ttf Then, I have found the config file for mime types under /etc/nginx/mime.types No mime types are configured for ttf (trutypes fonts) So, i have added font/ttf ttf; to mime.types...

@Cike76 You did an impressive job. Can you tell me what is your time to first byte when a page is cached? (Inspect > Network > reload page). It would be kind to mention how far you are located from your server. (in miles or kilometers) so that i can compare to my situation.

Thank you, i get it now. I have tried the try_files without any luck in the past. This explains everything.

If you want to add other regex directives with it, you must add the following: location / { #add location regex here location ~* "^/(.+)(!wp-admin|wp-login|wp-content|wp-includes)/$" { if (!-e $request_filename) { rewrite ^/(.+)/$ /index.php last; } } }

Problem was solved by using the regex in a context like this: location / { location ~* "^/page/[\d]+/$" { return 410; } } In nginx additional settings

Thank you so much , it was not exactly what I needed but it helped me a lot to find the solution. In fact I wanted to block wordpress pages like /page/124443/ /page/22334/ So, I didn't want to block a filename or an extension in particular. Consequently, here is the solution that worked for my...

I decided to take my pilgrim staff and go up the Plesk mountain. My first stop was at /etc/nginx/plesk.conf.d/vhosts/inadoo.com.conf (my test domain) I used location ~* "^/page/[\d]+/$" {return 410;} to see whether it worked. I haved added the location block with regex at the end of the...

I have checked and this one worked on my nginx test server (1.19) but it does not work on PLesk location ~* "^/page/[\d]+/$" {return 410;} (to return a 410 for domain.com/page/2/ domain.com/page/23/ domain.com/page/14) ...)

Hi, I have a problem with additional nginx directives. Some location blocks are ignored by Nginx. "Location =" does work but location (regex) (when involving a folder) does not work. I have performed some test on my test domain inadoo.com I have entered the following code in additional nginx...

I have the same problem: location blocks are ignored. For instance this one is ignored in additional nginx directives with proxy mode off location ~ ^/page/[0-9]+/? { return 404; } Everytime I want to set a locatin block it does not work. After unchecking Proxy mode, in Apache & nginx...

I have a similar issue, in additional nginx directives the following does not work: location ~ ^/page/[0-9]+/?$ { return 404; } It is like nginx does not "see" the location blocks.

Problem was solved by adding if (!-e $request_filename) { rewrite ^/(.*)$ /index.php; } At the end of nginx additional settings

thank you so I added then I called the URL And unfortunately, after visiting the logs, the problem is still there. and by the way, it happens with all my domains using nginx on my server. Here is how to repeat the problem: 1. Install wordpress on a domain using Plesk 2. Disable Apache by...

Hi, After installing wordpress and disabling Apache, I have found that while URLs are accessible it returns an error in the Nginx error logs. For some reasons, the code add the index file at the end of the URI. Here is a log example returned after visiting https://inadoo.com/cest-un-nombre/ //...

I looked into the cache folder of wp super cache and found that the file was not index.html. There are two files. Wp super cache chooses the file depending on whether you ticked Compress pages so they’re served more quickly to visitors. (Recommended) or not So since i ticked compress pages...

I have tried to add the following nginx directives to Additional nginx directives I only use nginx and I want to use WP super cache in expert mode with Nginx. The following code create the $cache_uri variable, then it checks some exception. Then at the end, it checks if there is an existing...

I think it would be important to add some code to the redirection to prevent nginx to return a HTML BODY in the 301 redirect. By default nginx returns the following: <html> <head><title>301 Moved Permanently</title></head> <body> <center><h1>301 Moved Permanently</h1></center>...