Hello,
I am trying to access gitea.com from my home network and I am unable to do so from any device or browser. I was able to access it normally a few days ago, but yesterday I got this error for the first time and since then I wasn’t able to connect. The error is really strange, I haven’t seen it before. This is what Firefox says:
And when I try curl -v https://gitea.com, I get
* Trying 34.217.253.146:443...
* Connected to gitea.com (34.217.253.146) port 443 (#0)
* ALPN: offers h2,http/1.1
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* CAfile: /etc/ssl/certs/ca-certificates.crt
* CApath: /etc/ssl/certs
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_128_GCM_SHA256
* ALPN: server accepted h2
* Server certificate:
* subject: CN=gitea.com
* start date: Nov 24 15:08:18 2025 GMT
* expire date: Feb 22 15:08:17 2026 GMT
* subjectAltName: host "gitea.com" matched cert's "gitea.com"
* issuer: C=US; O=Let's Encrypt; CN=E8
* SSL certificate verify ok.
* using HTTP/2
* h2h3 [:method: GET]
* h2h3 [:path: /]
* h2h3 [:scheme: https]
* h2h3 [:authority: gitea.com]
* h2h3 [user-agent: curl/7.88.1]
* h2h3 [accept: */*]
* Using Stream ID: 1 (easy handle 0x55556c7f95b0)
> GET / HTTP/2
> Host: gitea.com
> user-agent: curl/7.88.1
> accept: */*
>
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* HTTP/2 stream 1 was not closed cleanly: INTERNAL_ERROR (err 2)
* Connection #0 to host gitea.com left intact
curl: (92) HTTP/2 stream 1 was not closed cleanly: INTERNAL_ERROR (err 2)
Connecting from my cellular data or through a VPN works. I tried to investigate a bit, changed DNS, tweaked the MTU of my network interface etc., but it didn’t solve the issue. It seems the server just doesn’t respond. My best guess now is that the cause is some kind of IP or rate limit rule / block. This is unfortunate, as I have just started using my Gitea account.
Thank you in advance.