getting HTTP 500 status code while fetching assets on the ripe.net
IceCodeNew opened this issue · comments
IceCodeNew commented
[user@xxx ~]# asn=AS55095 && curl -vIL "https://stat.ripe.net/data/ris-prefixes/data.json?list_prefixes=true&types=o&resource=${asn}"
* Trying 193.0.6.150:443...
* Trying 2001:67c:2e8:22::c100:696:443...
* Immediate connect fail for 2001:67c:2e8:22::c100:696: Network is unreachable
* Connected to stat.ripe.net (193.0.6.150) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* CAfile: /etc/pki/tls/certs/ca-bundle.crt
* 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, Certificate Status (22):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS header, Certificate Status (22):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS header, Certificate Status (22):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS header, Certificate Status (22):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS header, Finished (20):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS header, Certificate Status (22):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS header, Finished (20):
* TLSv1.2 (IN), TLS header, Certificate Status (22):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN, server accepted to use h2
* Server certificate:
* subject: CN=stat.ripe.net
* start date: Dec 9 05:09:16 2022 GMT
* expire date: Mar 9 05:09:15 2023 GMT
* subjectAltName: host "stat.ripe.net" matched cert's "stat.ripe.net"
* issuer: C=US; O=Let's Encrypt; CN=R3
* SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* 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, Unknown (23):
* TLSv1.2 (OUT), TLS header, Unknown (23):
* TLSv1.2 (OUT), TLS header, Unknown (23):
* Using Stream ID: 1 (easy handle 0x588e70e45560)
* TLSv1.2 (OUT), TLS header, Unknown (23):
> HEAD /data/ris-prefixes/data.json?list_prefixes=true&types=o&resource=AS55095 HTTP/2
> Host: stat.ripe.net
> user-agent: curl/7.76.1
> accept: */*
>
* TLSv1.2 (IN), TLS header, Unknown (23):
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
* TLSv1.2 (OUT), TLS header, Unknown (23):
* TLSv1.2 (IN), TLS header, Unknown (23):
* TLSv1.2 (IN), TLS header, Unknown (23):
< HTTP/2 500
HTTP/2 500
< server: nginx
server: nginx
< date: Sat, 31 Dec 2022 06:11:25 GMT
date: Sat, 31 Dec 2022 06:11:25 GMT
< content-type: application/json; charset=utf-8
content-type: application/json; charset=utf-8
< content-length: 652
content-length: 652
< vary: Cookie, Accept-Encoding
vary: Cookie, Accept-Encoding
< access-control-allow-origin: *
access-control-allow-origin: *
<
* Connection #0 to host stat.ripe.net left intact
未名。 commented
同样遇到了..
IceCodeNew commented
The upstream seems back to normal.