Re: Incorrect log location error

2019-05-05 Thread spraguey
I was able to resolve this, but I am not sure exactly why. To simplify my post, I removed the code that sets a variable for the base path. That's where the problem is. set $homedir /webspace/mydomain.com; root ${homedir}/www; access_log ${homedir}/log/access.log; The root works, but access_log di

Re: Incorrect log location error

2019-05-05 Thread Bee.Lists
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

More than one host

2019-05-05 Thread Julian Brown
I am having a problem and not sure which side of the ocean it is on (Nginx or Apache). I am internally setting up an Nginx reverse proxy that will eventually go public. I have two domains I want Nginx to proxy for, both go to different machines. The second domain is for a bugzilla host, bugzilla

Re: Capture clear text with Nginx reverse proxy

2019-05-05 Thread Peter Booth via nginx
Mik, I’m not going to get into the openbsd question, but I can tell you some of the different things that I have done to solve this kind of problem in the past. Your environmental constraints will impact which is feasible: 1. Use tcpdump to capture packets 2. Use netcat as an intercepting proxy

Incorrect log location error

2019-05-05 Thread spraguey
I can't seem to get past an error when specifying the log location for a website. In my site.conf for the website... access_log /webspace/mydomain.com/log/access.log; The /webspace/mydomain.com/log folder definitely exists at that location. access.log is not created there. In my error.log file.

Re: after upgrade to nginx 1.16.0, $realpath_root returns incorrect path ?

2019-05-05 Thread PGNet Dev
On 5/5/19 2:41 AM, A. Schulze wrote: Am 05.05.19 um 07:14 schrieb PGNet Dev: Dropping back to 1.15 branch, all's working again -- with the var. For example, the diff between 1.15.12 and 1.16.0 is *only* the changed version number. So, be precise about which 1.15 version is working for you.

Re: after upgrade to nginx 1.16.0, $realpath_root returns incorrect path ?

2019-05-05 Thread A. Schulze
Am 05.05.19 um 07:14 schrieb PGNet Dev: > Dropping back to 1.15 branch, all's working again -- with the var. For example, the diff between 1.15.12 and 1.16.0 is *only* the changed version number. So, be precise about which 1.15 version is working for you. Andreas

Re: Capture clear text with Nginx reverse proxy

2019-05-05 Thread Mik J via nginx
Thank you for your answer Stuart. I'm on an Openbsd platform and it's not available for it. It seems to me a bit complicated because I'll have to insert it between the Nginx reverse proxy and the end server. Have you used it ? Le dimanche 5 mai 2019 à 04:01:54 UTC+2, Andrew Stuart a écr