OK, I’ve inserted that return into the conf file. BUT, there’s an error from an entry I’ve had in there before of a master error.log. It says the path provided is no such file or directory. That path is nowhere to be found in nginx.conf or alpha.conf. Something wrong with nginx? It isn’t reading the conf file. Reported: nginx 1.21.0 Cheers, Bee > On Jun 28, 2021, at 7:27 PM, Seby daBee - Nginx Mailing List - English
I did notice that nginx.conf structure started to recognize trailing semicolons recently. I have updated to a new OS from an old box on several versions ago. Comments are allowed on the same line in nginx.conf still? Cheers, Bee > On Jun 28, 2021, at 7:08 PM, Sergey A. Osokin <osa@freebsd.org.ru> wrote: > > Well, let's see how many servers are configured, could you provide >by daBee - Nginx Mailing List - English
Ya that’s too many to report. I have a catch-all with *.conf. I can restrict it down to that main nginx.conf and the extra VHost. Same as I posted before. Same result. This has the main two in my nginx.conf, and the included one. That last one has its own conf file: include /opt/homebrew/etc/nginx/servers/alpha.conf; Cheers, Bee > On Jun 28, 2021, at 7:08 PM, Sergey A. Osokin <by daBee - Nginx Mailing List - English
Same result. Default returned. Nothing in access log nor error log. Cheers, Bee > On Jun 28, 2021, at 6:35 PM, Sergey A. Osokin <osa@freebsd.org.ru> wrote: > > Seem like curl didn't send a valid "Host: alpha.local" header for some reason, > that's why NGINX replied with an answer for default_server. > > Could you try the following request: > > curlby daBee - Nginx Mailing List - English
I have a VHost that isn’t serving up. I’ve changed nothing, and it just started defaulting to the default_server. The VHost is included in a catch-all for all the other local domains (my workstation): include /opt/homebrew/etc/nginx/servers/*.conf; I’ve even hard coded the VHost in its own include and even that isn’t working. I’ve rebooted the box, same thing. nginx.conf tests paby daBee - Nginx Mailing List - English
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 look at the OS specifics, but I’ve set that to 1024 and it didn’t take. I will have to revby daBee - Nginx Mailing List - English
Trying to get nginx working in Big Sur. Upon trying to start the server (nginx.conf test passes fine), I get this: nginx: 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 nginx.conf, how can I get this to work properly? I tried deleting it, but it just threw an error that itby daBee - Nginx Mailing List - English
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@nginx.org http://mailman.nginx.org/mailman/listinfo/nginxby daBee - Nginx Mailing List - English
> On Jul 12, 2020, at 3:08 PM, Ian Hobson <hobson42@gmail.com> 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 separation between IP-based (based on the IP address) and name-based (baby daBee - Nginx Mailing List - English
> On Jul 12, 2020, at 9:43 AM, dorafmon <nginx-forum@forum.nginx.org> 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 decipher what vhost to return. Also, both of those dby daBee - Nginx Mailing List - English
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. HE…nor anybody...doesn’t need to ask for your private code to answer your questions. Atby daBee - Nginx Mailing List - English
Look at logrotate, as it will reduce file size. > On Mar 27, 2020, at 12:51 PM, waqas9980 <nginx-forum@forum.nginx.org> 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 work. Kindly suggest. > > NGINX version :by daBee - Nginx Mailing List - English
Notice the double // before webspace > On May 5, 2019, at 10:33 AM, spraguey <nginx-forum@forum.nginx.org> 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 _______________________________________________ nginx maby daBee - Nginx Mailing List - English
> > On Apr 12, 2019, at 10:24 PM, Software Info <softwareinfojam@gmail.com> 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/nginxby daBee - Nginx Mailing List - English
It’s fixed. Thank you > On Sep 28, 2018, at 11:48 AM, Bee.Lists <bee.lists@gmail.com> wrote: > > I often clear the cache and restart nginx. Cheers, Bee _______________________________________________ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginxby daBee - Nginx Mailing List - English
I often clear the cache and restart nginx. > On Sep 28, 2018, at 11:19 AM, Reinis Rozitis <r@roze.lv> 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 opened the http://domain2 before it was added to the nginx configuration (orby daBee - Nginx Mailing List - English
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 nginx; worker_processes auto; error_log /var/log/nginx/error.log; pid /run/nby daBee - Nginx Mailing List - English
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/nologin LOGNAME=nobody USER=nobody PASSENGER_APP_ENV=production NODE_ENV=production WSGI_ENV=productionby daBee - Nginx Mailing List - English
OK, thanks for the guidance. I will go have a look. I was using two texts that somehow convinced me it was done this way. I'll read up with the online documentation. Cheers shiroweb Wrote: ------------------------------------------------------- > Hi, I'm not sure what you did, but nginx.conf file, is only used to > configure the http server, not vhosts. > > There is 2 waby daBee - Nginx Mailing List - English
Hi there. Tried 192.168.1.4 (hard assigned), 127.0.0.1, localhost and 0.0.0.0: nothing shows up. Tried netstat -ln and nothing showing "8080" in any return. Jason Woods Wrote: ------------------------------------------------------- > Try port scan your network assigned IP and not 127.0.0.1. > > If something listens on 192.168.0.10:8080 for example, which isby daBee - Nginx Mailing List - English
Hi there. This is my port scan from 8000 to 8080: Port Scan has started… Port Scanning host: 127.0.0.1 Port Scan has completed… I've never set anything up to use that port. Styopa Semenukha Wrote: ------------------------------------------------------- > You already have an application listening on port 8080. You can find > it using > netstat(1).by daBee - Nginx Mailing List - English
Hi folks. Brand new to nginx. I'm trying to run 3 vhosts on my workstation to get familiar with nginx. alpha bravo charlie I'm using bravo in the main nginx.conf pointing to /var/www/alpha/ bravo and charlie are in settings/vhosts.conf into /var/www/bravo and /var/www/charlie Upon trying to start nginx (installed via homebrew on OSX), I get the following: HQ:~ rich$ sudo ngiby daBee - Nginx Mailing List - English