Show all posts by user
A portal to and from the mailing list.
Re: Installed WP in a subdir, can access wp-admin, but URLs are getting re-written without the subdir PATH. Where do I set this? - 6 years ago
Hello there! > I've installed WP in a site subdir. > > I can now access wp-admin pages at the expected URL. > > Sort of. I can get there manually, but my site config keeps redirecting, stripping URLs of the subdir path to WordPress. > > My config now has > > wp-config.php > <?php > define('WP_HOME', 'https://test.example.com/blog'); > defineby ph.gras - Nginx Mailing List - English
Re: [SOLVED] Trouble with SSL connection and let's encrypt certificates - 6 years ago
Thank you Maxim! > First of all, you have to look into your nginx logs and > configuration to find out what's going on here. :/var/log/nginx# cat error.log 2018/03/24 05:18:10 24058#24058: *573 no "ssl_certificate" is defined in server listening on SSL port while SSL handshaking, client: 162.158.78.50, server: 0.0.0.0:443 2018/03/24 05:18:14 24058#24058: *574 no "ssl_certby ph.gras - Nginx Mailing List - English
Trouble with SSL connection and let's encrypt certificates - 6 years ago
Hello there, I'm running several websites with different domain names on a Debian 9 server and have problems to have a connection on port 443 for some days. Certificates are generated by let's encrypt and do the job on other services except NginX, for example : # openssl s_client -connect mailbox.fredlutaud.com:443 -showcerts CONNECTED(00000003) write:errno=0 --- no peer certificate available --by ph.gras - Nginx Mailing List - English
Re: Allow and Deny IP's - 6 years ago
Hmmm! >>> location ~* wp-login\.php$ { >> >>> 185.124.153.168 - - [05/Feb/2018:21:36:12 +0100] "GET /wp-login.php HTTP/1.1" 200 1300 "-" "Mozilla/5.0 (Windows NT 6.0; rv:34.0) Gecko/20100101 Firefox/34.0" >> >>> Me too :-( >> >> Have you any reason to believe that this location is used to handle this request? >by ph.gras - Nginx Mailing List - English
Re: Allow and Deny IP's - 6 years ago
Hi Francis, >> location ~* wp-login\.php$ { > >> 185.124.153.168 - - [05/Feb/2018:21:36:12 +0100] "GET /wp-login.php HTTP/1.1" 200 1300 "-" "Mozilla/5.0 (Windows NT 6.0; rv:34.0) Gecko/20100101 Firefox/34.0" > >> Me too :-( > > Have you any reason to believe that this location is used to handle this request? Yes, and this especiallyby ph.gras - Nginx Mailing List - English
Re: Allow and Deny IP's - 6 years ago
Hello there! location ~* wp-login\.php$ { allow 127.0.0.1; allow A.B.C.D; // My server's IP allow E.F.G.H/13; // The IP range where I am deny all; if ($http_user_agent = "-") { return 403;} if ($http_user_agent = "") { return 403;} if ($http_referer = "-") { return 403;} if ($http_referer = "") { return 403;} limit_conn limit 5; } 185.124.153.1by ph.gras - Nginx Mailing List - English
Why should I have a 307 redirect ? - 6 years ago
Hi there, can somebody tell me why I have a 307 redirect response code when I'm turning my redirect directive to https off ? # curl -I https://www.avoirun.com HTTP/1.1 200 OK Server: nginx Date: Fri, 29 Sep 2017 21:48:40 GMT Content-Type: text/html; charset=UTF-8 Connection: keep-alive X-Pingback: https://www.avoirun.com/xmlrpc.php Link: https://www.avoirun.com/; rel=shortlink # curl -I http://by ph.gras - Nginx Mailing List - English
Re: I can't access to archives of my mailman lists : - 7 years ago
Thanks Francis, > From what you have shown, if your nginx user is not "list" > or in the group "list", it will possibly not have access to > /var/lib/mailman/archives/private. # ls -lLZ /var/lib/mailman/archives/public/rs-idf-discuter/index.html -rw-rw-r-- 1 list list ? 8736 sept. 17 16:44 /var/lib/mailman/archives/public/rs-idf-discuter/index.html # ls -lLdZ /var/liby ph.gras - Nginx Mailing List - English
I can't access to archives of my mailman lists : - 7 years ago
Hello there, unfortunately I'm not able to access to archives (pipermail) of my mailman lists. I'm using Nginx with a fcgiwrap gateway interface : :/etc/nginx/sites-available# curl -I http://poste.enpret.com/pipermail/rs-idf-discuter/index.html HTTP/1.1 403 Forbidden Server: nginx Date: Sun, 17 Sep 2017 17:00:25 GMT Content-Type: text/html Content-Length: 162 Connection: keep-alive :/etc/nginx/by ph.gras - Nginx Mailing List - English
Re: Bloking Bad bots - 7 years ago
Hi there ! so I do, with 2 different ways : ============================================== if ($http_user_agent ~* MJ12bot|SemrushBot) { return 403; } if ($http_user_agent ~* bot|crawl|spider|tools|java) { rewrite ^ http://www.cnrtl.fr/definition/créole redirect; } ============================================== Regards, Ph. Gras Le 14by ph.gras - Nginx Mailing List - English
Re: Redirection problem again in new rules. - 8 years ago
Le 14 avr. 2016 à 16:03, Muhammad Yousuf Khan <sirtcp@gmail.com> a écrit : > Redirect 301 /aaaa/bbbbbbb /aaaaa/bbbbbb.html > > Now i have converted this rule in nginx like this > > location /aaaa/bbbbbbbb { > rewrite ^(.*)$ /aaaa/bbbbbbbbbb.html redirect; > } > You should use break instead redirect : http://nginx.org/en/docs/http/ngx_http_rewrite_module.html#rby ph.gras - Nginx Mailing List - English
Re: Homepage cache and cookies - 8 years ago
Hello John! I think you can do this better with sessions in NginX. I've made a script that checks if a client is a bot or not, by testing if the Google Analytics cookie is here, or not. If it is, the client can post a comment or login. If not, the server is giving a fake page. In my PHP script : ***************************************************** $host = $_SERVER['REMOTE_ADDR']; $sessionby ph.gras - Nginx Mailing List - English
 |
 |
 |
 |
|