Ever since upgrading to 1.8.0 I get the following report from Cron: /etc/cron.daily/logrotate: error: error running shared postrotate script for '/var/log/nginx/*.log ' error: error running shared postrotate script for '/var/ www.example.com/logs/*.log ' run-parts: /etc/cron.daily/logrotate exited with return code 1 Contents of /etc/logrotate.d/nginx: /var/log/nginx/*.log { weekly missiby openletter - Nginx Mailing List - English
My logs have been inundated with hits at example.com/?anything, though in the actual logs 'anything' is a very long string of characters. Log entry: "GET /?anything HTTP/1.1" 200 581 "-" "Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko" (note there is no location for 'anything') I didn't even know this was possible. I'm still not sure what ngiby openletter - Nginx Mailing List - English
It seems like way back in the olden days, when I restarted nginx ('sudo service nginx restart'), if there was a configuration issue in nginx.conf, I would get a warning telling me such and, IIRC, nginx would boot using the last known valid configuration. It doesn't seem to happen that way any more. Did I unknowingly change a configuration setting, or was there a change to nginx? Thanks! Paul _by openletter - Nginx Mailing List - English
Did you try putting 'allow <your ip address>;' above 'return...' line in if block? _______________________________________________ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginxby openletter - Nginx Mailing List - English
Hi Francis, and again thanks for your help in this matter. I would have responded sooner but the day I was planning to resolve this issue I had an unseasonably long power outage. On Wed, Oct 23, 2013 at 11:41 AM, Francis Daly <francis@daoine.org> wrote: > On Wed, Oct 23, 2013 at 11:32:33AM -0700, Paul N. Pace wrote: >> On Wed, Oct 23, 2013 at 9:49 AM, Francis Daly <francis@daoinby openletter - Nginx Mailing List - English
Thank you, Francis. On Wed, Oct 23, 2013 at 9:49 AM, Francis Daly <francis@daoine.org> wrote: > If you don't like regex, don't use regex. > > You probably want another location{} to "deny", and that might be > "location ~ php$ {}", or it might be that nested inside > > location ^~ /installdirectory/ {} > > depending on what else you want in theby openletter - Nginx Mailing List - English
Hello- I am trying to allow only the PHP files required for a given PHP package to function correctly, then deny access to all other PHP files to prevent people from snooping on the site's configuration. I have created the location block, but I'm not so good with regular expressions and the block is assembled mostly through copy & paste. location /installdirectory/ { # from nginx pitfallby openletter - Nginx Mailing List - English
Dear Mr. or Ms. mex, Could you please contact me paulnpace@gmail.com regarding this very useful guide you have created? I have some specific questions and I would also like to help out, if I can. Thanks! Paul On Thu, Sep 12, 2013 at 11:36 AM, mex <nginx-forum@nginx.us> wrote: > Hi Valentin, > >> >> In your section about BREACH requirements: >> > > correct(eby openletter - Nginx Mailing List - English
We had a discussion on this list recently about using gzip in the SSL block. On Aug 17 Igor Sysoev wrote: >You have to split the dual mode server section into two server server sections and set "gzip off" >SSL-enabled on. There is no way to disable gzip in dual mode server section, but if you really >worry about security in general the server sections should be different. On Sby openletter - Nginx Mailing List - English
Thank you for your responses! On Tue, Aug 20, 2013 at 2:44 PM, Francis Daly <francis@daoine.org> wrote: > On Mon, Aug 19, 2013 at 02:53:36PM -0700, Paul N. Pace wrote: > > Hi there, > >> I am trying to set up a conf file for Piwik installations and I'm >> hoping a second set of of eyes can help: > > In nginx one request is handled in one location. The rules forby openletter - Nginx Mailing List - English
I have recently discovered this wonderful includes directive and I am using it to clean up my server blocks. Doing this has forced me to evaluate some of my configurations. I am trying to set up a conf file for Piwik installations and I'm hoping a second set of of eyes can help: location /piwik/ { location /js/ { allow all; } location ~ /js/.*\.php$ { include /by openletter - Nginx Mailing List - English
On Sun, Aug 18, 2013 at 12:31 PM, Paul N. Pace <paulnpace@gmail.com> wrote: > Igor said: >>You have to split the dual mode server section into two server server sections and set "gzip off" >>SSL-enabled on. There is no way to disable gzip in dual mode server section, but if you really >>worry about security in general the server sections should be different. &gby openletter - Nginx Mailing List - English
Igor said: >You have to split the dual mode server section into two server server sections and set "gzip off" >SSL-enabled on. There is no way to disable gzip in dual mode server section, but if you really >worry about security in general the server sections should be different. Adie said: >This is why Igor recommends you to split the server config for SSL and non-SSL, and pby openletter - Nginx Mailing List - English
On Thu, Jul 25, 2013 at 10:29 AM, Valentin V. Bartenev <vbart@nginx.com> wrote: > On Tuesday 23 July 2013 12:24:38 JackB wrote: >> openletter Wrote: >> ------------------------------------------------------- >> >> > If you are using the apt-get upgrade or aptitude upgrade commands, the >> > service will be restarted for you. >> >> This mightby openletter - Nginx Mailing List - English
On Mon, Jul 22, 2013 at 10:13 AM, howard chen <howachen@gmail.com> wrote: > I am upgrading nginx to latest 1.4.1 using PPA. repository. > > 1. After install, do I need to restart it manually, or it is restarted > automatically? > 2. Is reload enough for the nginx upgrade? Or do I need to restart or > stop/start? If you are using the apt-get upgrade or aptitude upgrade commby openletter - Nginx Mailing List - English
I have a server that I set up to run several domains from and it has worked great and without issue for about 6 months. I have another server that I had set up and was only running one domain from it and I just added a second domain. For some reason, this second server does not want to serve two domains, and I can find no substantial differences in the configuration files (nginx.conf and sites-avby openletter - Nginx Mailing List - English
Thank you Steve for nginx -t, and Sajan was correct, I had a syntax error in a server block. However, while I was troubleshooting I noticed my log files getting rather huge. I keep the access_log and error_log files in the directories for each site. How can I keep these log files to a reasonable size without losing the data? (I use Piwik to analyze access logs, so I don't want to lose any data).by openletter - Nginx Mailing List - English
This Ars Technica article is where I learned how to use nginx. Lee Hutchinson does a good job explaining all that. http://arstechnica.com/gadgets/2012/11/how-to-set-up-a-safe-and-secure-web-server/ On Mon, May 13, 2013 at 4:02 AM, Shohreh <nginx-forum@nginx.us> wrote: > I found a work-around: Reading "/var/log/nginx/error.log" includes a warning > that Nginx can't find &quoby openletter - Nginx Mailing List - English
On Thu, May 2, 2013 at 1:21 PM, Francis Daly <francis@daoine.org> wrote: > On Thu, May 02, 2013 at 01:05:29PM -0700, Paul N. Pace wrote: > > Hi there, > >> Other than that, I tried to follow both guides to the letter. When I >> go to http://lists.example.com I get redirected to >> http://lists.example.com/mailman/listinfo (on Chrome and FF, but not >> IE)by openletter - Nginx Mailing List - English
I am trying my first install of Mailman. I have a working Postfix/Dovecot/MySQL mail server running Ubuntu 12.04 and nginx stable 1.2.7. I am following the ngnix Mailman wiki article http://wiki.nginx.org/Mailman and the Ubuntu Official Documentation for setting up Mailman. https://help.ubuntu.com/12.04/serverguide/mailman.html I had to install thttpd from the deb file because starting with 1by openletter - Nginx Mailing List - English
On Wed, May 1, 2013 at 2:07 PM, Maxim Dounin <mdounin@mdounin.ru> wrote: > Hello! > > On Wed, May 01, 2013 at 11:17:10AM -0700, Alder Network wrote: > >> Just for clarity, I want to be listening on both IPv4 and IPv6 on the same >> port. > > You have to write > > listen 80; > listen [::]:80; > > to listen on both IPv4 and IPv6. Doesn't thby openletter - Nginx Mailing List - English
Steve, you are a Linux genius, and I am but a humble plebe, forever in your debt. On Sun, Apr 21, 2013 at 1:09 PM, Steve Holdoway <steve@greengecko.co.nz> wrote: > At a guess, /var or /var/www isn't readable by www-data > > Steve > > On 22/04/2013, at 7:50 AM, "Paul N. Pace" <paulnpace@gmail.com> wrote: > >> I have set up a server on Rackspace using Uby openletter - Nginx Mailing List - English
I have set up a server on Rackspace using Ubuntu 12.04 and the nginx stable PPA. Using the default root location of /usr/share/nginx/html the index.html file is displayed when I call the public IP address of the server. If I change the root location to my own /var/www/example.com/public the index.html file is not displayed. Output of ll on /var/www/example.com/public: drwxrwsr-x 2 www-data wwwby openletter - Nginx Mailing List - English
I am setting up a server that will be for a B2B business, and I want the whole site to be served as https://www.example.com/ I have gotten a certificate and https://www.example.com runs just fine, but I can't figure out how to require https://www.example.com when a user tries to go to https://example.com. In reading through the nginx.org site, it seems like rewrites and if statements are disby openletter - Nginx Mailing List - English