Hi there.
It is development. I’ve been running 1024 for over 10 years and now there’s a
restriction on 256 workers, and I don’t know why. It seems to be set quite
low. Given the fact this is a new warning, developers that have increased this
setting have been wrong all this time?
I’ll take a
Trying to get nginx working in Big Sur. Upon trying to start the server
(nginx.conf test passes fine), I get this:
nginx: [error] invalid PID number “” in “/opt/homebrew/var/run/nginx.pid”
The file is there, but it seems empty. Given that homebrew now chooses that
location, and is set in ngin
Big Sur has a warning that 1024 exceeds open file resource limit of 256.
Is this normal, considering I’ve set my worker_connections to 1024 in
nginx.conf?
Also, is this a package manager designation?
Cheers, Bee
___
nginx mailing list
nginx@ng
> On Jul 12, 2020, at 3:08 PM, Ian Hobson wrote:
>
> This is not correct, see
> https://nginx.org/en/docs/http/ngx_http_core_module.html#server where it says
>
> Syntax: server { ... }
> Default: —
> Context: http
> Sets configuration for a virtual server. There is no clear sep
> On Jul 12, 2020, at 9:43 AM, dorafmon wrote:
>
> I am trying to host multiple web apps on the same machine and they are all
> SSL enabled. I am trying to put an Nginx server in front of them to redirect
> incoming requests to different ports.
The domain carried forward is what nginx uses to
I think he’s saying that there’s more to this than posting code and saying “no
worky”.
State what you want, what you have, what you’ve tried, and what you think might
be going wrong. Simply posting your code and expecting other troubleshooters
to solve your issue, is the wrong approach.
H
Look at logrotate, as it will reduce file size.
> On Mar 27, 2020, at 12:51 PM, waqas9980 wrote:
>
> Hi,
> I am using Java application with NGINX. When my request have large size
> response body, nginx truncates that logs in access.log file. I have used
> proxy_buffering off; but that didn't w
Notice the double // before webspace
> On May 5, 2019, at 10:33 AM, spraguey wrote:
>
> "/usr/share/nginx//webspace/mydomain.com/log/access.log" failed (2: No such
> file or directory) while logging request, client: X.X.X.X, server:
> www.mydomain.com..."
Cheers, Bee
>
> On Apr 12, 2019, at 10:24 PM, Software Info wrote:
>
> Any ideas on how to do this? Any help would be appreciated.
How about a subject?
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
It’s fixed. Thank you
> On Sep 28, 2018, at 11:48 AM, Bee.Lists wrote:
>
> I often clear the cache and restart nginx.
Cheers, Bee
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
I often clear the cache and restart nginx.
> On Sep 28, 2018, at 11:19 AM, Reinis Rozitis wrote:
>
> If you are testing just with a browser make sure you've cleaned the cache (or
> disable it, or use some other tools which don't have cache (like wget for
> example)).
>
> If by chance you op
I have a test server up with 3 domains.
First domain redirects port 80 to ssl 443.
Second domain is just port 80.
Third domain is just port 80.
Second domain isn’t showing up, pointing to first domain. Third domain is
working. Why would this happen?
nginx.conf:
# user
Hi there. My question is about using a proper user.
This directive was initially blank, then Passenger (nginx on FreeBSD) threw an
error:
env: bash: No such file or directory
uid=65534(nobody) gid=65534(nobody) groups=65534(nobody)
PWD=/usr/local/www/pneb
HOME=/nonexistent
SHELL=/usr/sbin/no
13 matches
Mail list logo