Re: Port numbers in the access or error logs ?

Thank you this worked perfectly. I used both server and remote ports in the logs. Many thanks! On Tue, Sep 13, 2022 at 11:48 AM Lucas Rolff wrote: > Yes, it’s documented in > http://nginx.org/en/docs/http/ngx_http_core_module.html#variables > > $remote_port is probably what you’re after. > > On

Re: Port numbers in the access or error logs ?

Yes, it’s documented in http://nginx.org/en/docs/http/ngx_http_core_module.html#variables $remote_port is probably what you’re after. On 13 Sep 2022, at 20:24, Michael Williams mailto:michael.glenn.willi...@totalvu.tv>> wrote: Is there a way to include the request port number in each line of

Port numbers in the access or error logs ?

Is there a way to include the request port number in each line of the access logs? I'm on Debian 11, using free NGINX downloaded. Many thanks, Michael [image: linkedin] ___ nginx mailing li

Re: Real client IP in the error logs when a server is behind a reverse proxy

Thank you for your answers, Matthew, I use Openbsd Nanaya, I tried your solution and it worked. I had to readapt a bit my configuration (removed xforwardedLog) so that my access_log is formated without duplicate IPs. Regards Le jeudi 30 juin 2022 à 17:17:01 UTC+2, nanaya a écrit : Hello,

Re: Real client IP in the error logs when a server is behind a reverse proxy

Hello, You need to set the reverse proxy ip in the www server: https://nginx.org/r/set_real_ip_from Also note this will replace $remote_addr with the value from X-Real-IP header (the original value is in $realip_remote_addr). On Thu, Jun 30, 2022, at 21:56, Mik J via nginx wrote: > Hello, > >

Re: Real client IP in the error logs when a server is behind a reverse proxy

What linux distro is NginX running on? PEREGRINE IT Signature *Matthew J BLACK*   M.Inf.Tech.(Data Comms)   MBA   B.Sc.   MACS (Snr), CP, IP3P When you want it done /right/ ‒ the first time! Phone: +61 4 0411 0089 Email: matt...@peregrineit.net Web:www.pe

Real client IP in the error logs when a server is behind a reverse proxy

Hello, I have a real server placed behing my reverse proxywww server 192.168.1.10 <---> 192.168.1.20 reverse proxy <---> NAT Firewall <---> Interrnet <---> Client on Internet My configuration on my reverse proxy (192.168.1.20) looks like that location ^~ / {     proxy_pass  h

Re: SSL Handshake Failure with error:1407609B:SSL in error logs

Since your backend is already doing ssl, you should remove ssl from the listen, so that nginx will just do a simple TCP pass through: Change listen 443 ssl; to listen 443; On Wed, Jul 4, 2018 at 12:31 AM, shivramg94 wrote: > Hi, > > We are trying to configure TCP load balancing with TLS termin

Re: SSL Handshake Failure with error:1407609B:SSL in error logs

Hello! On Wed, Jul 04, 2018 at 03:31:59AM -0400, shivramg94 wrote: > We are trying to configure TCP load balancing with TLS termination. But when > we try to access the URL, we could see the below error in the nginx error > and access logs > > Nginx Error Log: > > 2018/07/04 07:16:45 [crit] 794

SSL Handshake Failure with error:1407609B:SSL in error logs

Hi, We are trying to configure TCP load balancing with TLS termination. But when we try to access the URL, we could see the below error in the nginx error and access logs Nginx Error Log: 2018/07/04 07:16:45 [crit] 7944#0: *61 SSL_do_handshake() failed (SSL: error:1407609B:SSL routines:SSL23_GET

Re: error logs

> On 19 Sep 2017, at 09:41, Deepak Pant. wrote: > > Hi All, > > I am getting below error can anyone let me know how to resolve it > > > 2017/09/02 23:26:05 [crit] 28974#0: *2333672 SSL_do_handshake() failed (SSL: > error:1408A0D7:SSL routines:SSL3_GET_CLIENT_HELLO:required cipher missing)

error logs

Hi All, I am getting below error can anyone let me know how to resolve it 2017/09/02 23:26:05 [crit] 28974#0: *2333672 SSL_do_handshake() failed (SSL: error:1408A0D7:SSL routines:SSL3_GET_CLIENT_HELLO:required cipher missing) while SSL handshaking, client: 10.210.128.122, server: 0.0.0.0:443 2

Re: Question about Error logs

On Wed, Nov 02, 2016 at 08:49:52AM -0400, pkjchate wrote: Hi there, > Is there any setting I can do, so that Nginx only logs 1 error in same file > only once in the file. I think "no", using just configuration. > The problem is I am getting a lot of same errors and the file gets large in > size

Question about Error logs

Hi, I just migrated from Apache to Nginx. I have a question error logs. Nginx now logs same error again and again in the log file, but with different request IPs. Is there any setting I can do, so that Nginx only logs 1 error in same file only once in the file. The problem is I am getting a

Re: Feature Request: write error logs when detecting duplicate http headers

thanks,recently i ran into this problem I saw you this post, help me with this problem Posted at Nginx Forum: https://forum.nginx.org/read.php?2,204689,267222#msg-267222 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/n

Re: Invalid "host" information in access and error logs

On Wednesday 28 October 2015 16:29:55 tamere22 wrote: > Thanks for your time. > So you're saying clients request www.siteA.com but rewrite packets to say > host: www.siteB.com in their http request ? > > Why would google bot do such a thing ? > > I'm still unsure because I don't see why legitim

Re: Invalid "host" information in access and error logs

Thanks for your time. So you're saying clients request www.siteA.com but rewrite packets to say host: www.siteB.com in their http request ? Why would google bot do such a thing ? I'm still unsure because I don't see why legitimate clients would do that. For you, it's ok to have in log file "

Re: Invalid "host" information in access and error logs

On Wednesday 28 October 2015 15:34:50 tamere22 wrote: > Hi, > > I'm sorry but I can't believe this is true. The random "hosts" I see in logs > are defined in other "server" blocks that have their own separate log files. You have a couple of server blocks that listens on different ports. So for e

Re: Invalid "host" information in access and error logs

Hi, I'm sorry but I can't believe this is true. The random "hosts" I see in logs are defined in other "server" blocks that have their own separate log files. Also why would the "server" information in the logs be good whereas the "host" information is completly random ? Please review configurat

RE: Invalid "host" information in access and error logs

Wrong email... I am not able to answer your query! Sorry -Original Message- From: nginx [mailto:nginx-boun...@nginx.org] On Behalf Of Valentin V. Bartenev Sent: 28 October 2015 15:47 To: nginx@nginx.org Subject: Re: Invalid "host" information in access and error logs On We

Re: Invalid "host" information in access and error logs

On Wednesday 28 October 2015 14:36:15 tamere22 wrote: > Hi, > > My message is referring to this bug report : > https://trac.nginx.org/nginx/ticket/818#comment:6 > > The person answering me told me to come talk here about this. > > I don't understand his answers, as "How nginx processes a reques

Invalid "host" information in access and error logs

Hi, My message is referring to this bug report : https://trac.nginx.org/nginx/ticket/818#comment:6 The person answering me told me to come talk here about this. I don't understand his answers, as "How nginx processes a request" page states "In this configuration nginx tests only the request’s

Re: Remove request from nginx error logs

On Thu, Sep 10, 2015 at 06:51:18PM +0530, gaurav gupta wrote: Hi there, > How can we remove request url being logged in nginx error logs. For example > it looks something like: I don't think you can control the details of what nginx writes. Perhaps you could process the logs your

Remove request from nginx error logs

Hello Folks, How can we remove request url being logged in nginx error logs. For example it looks something like: 2015/09/01 15:26:03 [error] 30547#0: *208725 upstream prematurely closed connection while reading response header from upstream, client: 123.123.50.44, server: test.example.com

NGINX + PHP-FPM error logs miss IP

Could it be that Apache 2.2 + mod_fastcgi + PHP FPM logs IP addresses to errror.log but NGINX + PHP-FPM does not? I mean not to a log file specified in error_log configuration option. [03-Sep-2014 19:37:24 UTC] {message from e.g. error_log()} *no IP address in the the line After commenting

Re: 500 error when posting, no message in error logs

On Feb 13, 2014, at 23:23 , offthedeepnd wrote: > Hi All, > > I'm running nginx 1.4.1 on OpenBSD 5.4 stable along with php and php-fpm > version 5.3.27 and mysql 5.1.70 on two systems. I'm trying to install > piwigo-2.6.1 and running into an issue on of of the systems as indicated by > the subje

500 error when posting, no message in error logs

Hi All, I'm running nginx 1.4.1 on OpenBSD 5.4 stable along with php and php-fpm version 5.3.27 and mysql 5.1.70 on two systems. I'm trying to install piwigo-2.6.1 and running into an issue on of of the systems as indicated by the subject. When I access the site initially it takes me to the set

Re: 404 not showing up in error logs (for PHP files)

We solved this problem like this: try_files $uri $uri-404; This would first check if the php file exists, and if not it would try to open that same php file but with "-404" appended to it, so the user would still get a 404 status code, but it would also log what file was called. I hope this helps