Custom Query (2296 matches)
Results (4 - 6 of 2296)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #2623 | invalid | nginx is reporting a Status=000 on port 443 when sending large queries | ||
| Description |
We're having difficulties getting a large query though nginx setup as a load balancer. The packets are rejected on ingress, and nginx posts to the logfile: Apr 2 14:43:54 Myserver Myserver nginx: RemoteAddr=xxx.xxx.xxx.xxx;HostPort=443;Status=000;User-Agent=-;error_log/var/log/nginx/error.logdebug I can not find any documentation that states what a Status=000 is. The frame with the large query we are sending is approximately 0x2a70 bytes. And it is to an HTTPs port. We're able to simulate this using curl. Everything looks okay (using trace mode) up to the very last part, which is included below. A few of our config settings that we are using: worker_connections 1024; client_max_body_size 10M; large_client_header_buffers 10 64K proxy_ignore_client_abort on; proxy_buffering off; We're tried to change the client_max_body_size and large_client_header_buffers to many different settings, but none work. Last part of Curl trace: <= Recv SSL data, 5 bytes (0x5) 0000: 17 03 03 00 4a ....J <= Recv SSL data, 1 bytes (0x1) 0000: 16 . Info: TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):<= Recv SSL data, 57 bytes (0x39) 0000: 04 00 00 35 00 00 01 2c 1f 96 2c 58 08 00 00 00 ...5...,..,X.... 0010: 00 00 00 00 00 00 20 e7 66 7e 4e e2 f7 02 36 f8 ...... .f~N...6. 0020: f0 51 f4 02 88 90 74 d5 c4 92 0e ba a3 a6 0d 35 .Q....t........5 0030: e7 74 93 13 b5 3a fe 00 00 .t...:... <= Recv SSL data, 5 bytes (0x5) 0000: 17 03 03 00 4a ....J <= Recv SSL data, 1 bytes (0x1) 0000: 16 . Info: TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):<= Recv SSL data, 57 bytes (0x39) 0000: 04 00 00 35 00 00 01 2c f3 f0 af e3 08 00 00 00 ...5...,........ 0010: 00 00 00 00 01 00 20 9c 7b a9 d4 6a 73 fd 9c 69 ...... .{..js..i 0020: 01 5d d9 4a d8 38 0f 52 b9 2e c4 b5 34 9b fa c6 .].J.8.R....4... 0030: d0 dd 33 6a bc 80 79 00 00 ..3j..y.. Info: old SSL session ID is stale, removing<= Recv SSL data, 5 bytes (0x5) 0000: 17 03 03 00 42 ....B <= Recv SSL data, 1 bytes (0x1) 0000: 17 . Info: Connection state changed (MAX_CONCURRENT_STREAMS == 128)!=> Send SSL data, 5 bytes (0x5) 0000: 17 03 03 00 1a ..... => Send SSL data, 1 bytes (0x1) 0000: 17 . <= Recv SSL data, 5 bytes (0x5) 0000: 17 03 03 00 22 ...." <= Recv SSL data, 1 bytes (0x1) 0000: 17 . <= Recv SSL data, 5 bytes (0x5) 0000: 17 03 03 00 13 ..... <= Recv SSL data, 1 bytes (0x1) 0000: 15 . Info: TLSv1.3 (IN), TLS alert, close notify (256):<= Recv SSL data, 2 bytes (0x2) 0000: 01 00 .. Info: Empty reply from serverInfo: Closing connection 0=> Send SSL data, 5 bytes (0x5) 0000: 17 03 03 00 13 ..... => Send SSL data, 1 bytes (0x1) 0000: 15 . Info: Connection state changed (MAX_CONCURRENT_STREAMS == 128)!=> Send SSL data, 5 bytes (0x5) 0000: 17 03 03 00 1a ..... => Send SSL data, 1 bytes (0x1) 0000: 17 . <= Recv SSL data, 5 bytes (0x5) 0000: 17 03 03 00 22 ...." <= Recv SSL data, 1 bytes (0x1) 0000: 17 . <= Recv SSL data, 5 bytes (0x5) 0000: 17 03 03 00 13 ..... <= Recv SSL data, 1 bytes (0x1) 0000: 15 . Info: TLSv1.3 (IN), TLS alert, close notify (256):<= Recv SSL data, 2 bytes (0x2) 0000: 01 00 .. Info: Empty reply from serverInfo: Closing connection 0=> Send SSL data, 5 bytes (0x5) 0000: 17 03 03 00 13 ..... => Send SSL data, 1 bytes (0x1) |
|||
| #2622 | fixed | nginx-quic is down | ||
| Description |
Is Nginx QUIC site is down? Below is site details https://hg.nginx.org/nginx-quic [Error 503] Am i missing anything here? |
|||
| #2616 | worksforme | apt upgrade fails. | ||
| Description |
Hi, I can't upgrade to the 1.24.0 stable version which is offered to me by apt. nginx was set up using the stable version and preferring the nginx repository rather than the distribution one as described here: https://nginx.org/en/linux_packages.html#Ubuntu This worked perfectly. Now apt is offering to upgrade to 1.24.0. The following is happening: $ sudo apt upgrade nginx Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies:
E: Broken packages What can be done? |
|||
