Jump to content

Mikegn

Forum Members
 View Profile  See their activity

  • Posts

    1

  • Joined

  • Last visited

Equipment

  • Keenetic
    KN-1810

Mikegn's Achievements

Newbie

Newbie (1/5)

0

Reputation

  1. Mikegn
    Mikegn joined the community
  2. Mikegn
    After update my keenetic ultra i have an issue with http proxy - all requests by KeenDNS to my local servers return 502 response * Connected to xxx.xxx.keenetic.pro (x.x.x.x) port 80 (#0) > GET / HTTP/1.1 > Host: xxx.xxx.keenetic.pro > User-Agent: curl/7.81.0 > Accept: */* > * Mark bundle as not supporting multiuse < HTTP/1.1 302 Moved Temporarily < Server: Web server < Date: Thu, 09 Nov 2023 16:41:31 GMT < Content-Type: text/html < Content-Length: 143 < Connection: keep-alive < Location: https://xxx.xxx.keenetic.pro/ < * Ignoring the response-body * Connection #0 to host xxx.xxx.keenetic.pro left intact * Clear auth, redirects to port from 80 to 443 * Issue another request to this URL: 'https://xxx.xxx.keenetic.pro/' * Trying x.x.x.x:443... * Connected to xxx.xxx.keenetic.pro (x.x.x.x) port 443 (#1) * ALPN, offering h2 * ALPN, offering http/1.1 * CAfile: /etc/ssl/certs/ca-certificates.crt * CApath: /etc/ssl/certs * TLSv1.0 (OUT), TLS header, Certificate Status (22): * TLSv1.3 (OUT), TLS handshake, Client hello (1): * TLSv1.2 (IN), TLS header, Certificate Status (22): * TLSv1.3 (IN), TLS handshake, Server hello (2): * TLSv1.2 (IN), TLS header, Finished (20): * TLSv1.2 (IN), TLS header, Supplemental data (23): * TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8): * TLSv1.2 (IN), TLS header, Supplemental data (23): * TLSv1.3 (IN), TLS handshake, Certificate (11): * TLSv1.2 (IN), TLS header, Supplemental data (23): * TLSv1.3 (IN), TLS handshake, CERT verify (15): * TLSv1.2 (IN), TLS header, Supplemental data (23): * TLSv1.3 (IN), TLS handshake, Finished (20): * TLSv1.2 (OUT), TLS header, Finished (20): * TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1): * TLSv1.2 (OUT), TLS header, Supplemental data (23): * TLSv1.3 (OUT), TLS handshake, Finished (20): * SSL connection using TLSv1.3 / TLS_CHACHA20_POLY1305_SHA256 * ALPN, server accepted to use h2 * Server certificate: * subject: CN=xxx.keenetic.pro * start date: Sep 20 19:31:06 2023 GMT * expire date: Dec 19 19:31:05 2023 GMT * subjectAltName: host "xxx.xxx.keenetic.pro" matched cert's "*.xxx.keenetic.pro" * issuer: C=US; O=Let's Encrypt; CN=R3 * SSL certificate verify ok. * Using HTTP2, server supports multiplexing * Connection state changed (HTTP/2 confirmed) * Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0 * TLSv1.2 (OUT), TLS header, Supplemental data (23): * TLSv1.2 (OUT), TLS header, Supplemental data (23): * TLSv1.2 (OUT), TLS header, Supplemental data (23): * Using Stream ID: 1 (easy handle 0x556cd8004550) * TLSv1.2 (OUT), TLS header, Supplemental data (23): > GET / HTTP/2 > Host: xxx.xxx.keenetic.pro > user-agent: curl/7.81.0 > accept: */* > * TLSv1.2 (IN), TLS header, Supplemental data (23): * TLSv1.3 (IN), TLS handshake, Newsession Ticket (4): * TLSv1.2 (IN), TLS header, Supplemental data (23): * TLSv1.3 (IN), TLS handshake, Newsession Ticket (4): * old SSL session ID is stale, removing * TLSv1.2 (IN), TLS header, Supplemental data (23): * Connection state changed (MAX_CONCURRENT_STREAMS == 128)! * TLSv1.2 (OUT), TLS header, Supplemental data (23): * TLSv1.2 (IN), TLS header, Supplemental data (23): < HTTP/2 502 < server: Web server < date: Thu, 09 Nov 2023 16:41:36 GMT < content-type: text/html < content-length: 155 < <html> <head><title>502 Bad Gateway</title></head> <body> <center><h1>502 Bad Gateway</h1></center> <hr><center>Web server</center> </body> </html> * Connection #1 to host xxx.xxx.keenetic.pro left intact After downgrade os version and dont change anything http proxy work normally * Connected to xxx.xxx.keenetic.pro (x.x.x.x) port 80 (#0) > GET / HTTP/1.1 > Host: xxx.xxx.keenetic.pro > User-Agent: curl/7.81.0 > Accept: */* > * Mark bundle as not supporting multiuse < HTTP/1.1 302 Moved Temporarily < Server: Web server < Date: Thu, 09 Nov 2023 16:37:01 GMT < Content-Type: text/html < Content-Length: 143 < Connection: keep-alive < Location: https://xxx.xxx.keenetic.pro/ < * Ignoring the response-body * Connection #0 to host xxx.xxx.keenetic.pro left intact * Clear auth, redirects to port from 80 to 443 * Issue another request to this URL: 'https://xxx.xxx.keenetic.pro/' * Trying x.x.x.x:443... * Connected to xxx.xxx.keenetic.pro (x.x.x.x) port 443 (#1) * ALPN, offering h2 * ALPN, offering http/1.1 * CAfile: /etc/ssl/certs/ca-certificates.crt * CApath: /etc/ssl/certs * TLSv1.0 (OUT), TLS header, Certificate Status (22): * TLSv1.3 (OUT), TLS handshake, Client hello (1): * TLSv1.2 (IN), TLS header, Certificate Status (22): * TLSv1.3 (IN), TLS handshake, Server hello (2): * TLSv1.2 (IN), TLS header, Finished (20): * TLSv1.2 (IN), TLS header, Supplemental data (23): * TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8): * TLSv1.2 (IN), TLS header, Supplemental data (23): * TLSv1.3 (IN), TLS handshake, Certificate (11): * TLSv1.2 (IN), TLS header, Supplemental data (23): * TLSv1.3 (IN), TLS handshake, CERT verify (15): * TLSv1.2 (IN), TLS header, Supplemental data (23): * TLSv1.3 (IN), TLS handshake, Finished (20): * TLSv1.2 (OUT), TLS header, Finished (20): * TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1): * TLSv1.2 (OUT), TLS header, Supplemental data (23): * TLSv1.3 (OUT), TLS handshake, Finished (20): * SSL connection using TLSv1.3 / TLS_CHACHA20_POLY1305_SHA256 * ALPN, server accepted to use h2 * Server certificate: * subject: CN=xxx.keenetic.pro * start date: Sep 20 19:31:06 2023 GMT * expire date: Dec 19 19:31:05 2023 GMT * subjectAltName: host "xxx.xxx.keenetic.pro" matched cert's "*.xxx.keenetic.pro" * issuer: C=US; O=Let's Encrypt; CN=R3 * SSL certificate verify ok. * Using HTTP2, server supports multiplexing * Connection state changed (HTTP/2 confirmed) * Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0 * TLSv1.2 (OUT), TLS header, Supplemental data (23): * TLSv1.2 (OUT), TLS header, Supplemental data (23): * TLSv1.2 (OUT), TLS header, Supplemental data (23): * Using Stream ID: 1 (easy handle 0x5557ee97c550) * TLSv1.2 (OUT), TLS header, Supplemental data (23): > GET / HTTP/2 > Host: xxx.xxx.keenetic.pro > user-agent: curl/7.81.0 > accept: */* > * TLSv1.2 (IN), TLS header, Supplemental data (23): * TLSv1.3 (IN), TLS handshake, Newsession Ticket (4): * TLSv1.2 (IN), TLS header, Supplemental data (23): * TLSv1.3 (IN), TLS handshake, Newsession Ticket (4): * old SSL session ID is stale, removing * TLSv1.2 (IN), TLS header, Supplemental data (23): * Connection state changed (MAX_CONCURRENT_STREAMS == 128)! * TLSv1.2 (OUT), TLS header, Supplemental data (23): * TLSv1.2 (IN), TLS header, Supplemental data (23): < HTTP/2 404 < server: Web server < date: Thu, 09 Nov 2023 16:37:01 GMT < content-type: application/json < content-length: 22 < * TLSv1.2 (IN), TLS header, Supplemental data (23): * Connection #1 to host xxx.xxx.keenetic.pro left intact
×
×
  • Create New...