Intermittent TLS “connection reset by peer”

Hello, I’m new to the forum but I’ve been using the MusicBrainz API in iOS 26 for a few weeks without any issue. But after the power outage that the Internet Archive had last week I’ve had Intermittent TLS “connection reset by peer” errors. I’ve also been testing this in the Terminal on macOS using curl (I’ve been using this: curl -vIL https://coverartarchive.org/release/fef8b229-ee77-4e63-a07f-222c1ad56c97).
Sometimes the request works and I get the expected 307 redirect and then the JSON from archive.org; other times the TLS connection to coverartarchive.org is reset immediately after the ClientHello. Here is an example of what it returns (I tried forcing IPv4 to confirm it wasn’t an IPv6 issue):
curl -4 -vIL https://coverartarchive.org/release/fef8b229-ee77-4e63-a07f-222c1ad56c97

  • Host coverartarchive.org:443 was resolved.
  • IPv6: (none)
  • IPv4: 142.132.240.1
  • Trying 142.132.240.1:443…
  • Connected to coverartarchive.org (142.132.240.1) port 443
  • ALPN: curl offers h2,http/1.1
  • (304) (OUT), TLS handshake, Client hello (1):
  • CAfile: /etc/ssl/cert.pem
  • CApath: none
  • Recv failure: Connection reset by peer
  • LibreSSL/3.3.6: error:02FFF036:system library:func(4095):Connection reset by peer
  • Closing connection
    curl: (35) Recv failure: Connection reset by peer

Is this happening with anyone else? Am I possibly doing something wrong on my end, or is there something that happened during the power outage at the Internet Archive that could possibly be causing this?

If there is anything else I can add to help troubleshoot this please let me know!

1 Like

I have definitely seen those several times the last days when using Picard. So it’s not only you, I’m sure this is somewhere on the Internet Archive side.

Thank you for confirming, I really appreciate it!

Is this something I should try and now make Internet Archive aware of separately you think? Maybe they don’t even know if no one has reported to them… I’ll look into this as well

I’m aware of this issue, but I didn’t had time to investigate yet.

MeB admins will have a look very soon. Thanks for the report.

7 Likes

this has been driving me crazy, thought something was wrong on my end! happy to see someone else encountering this too. thanks for looking into it!

2 Likes

I’m encountering an identical intermittent issue with ListenBrainz. Given the timing and identical IP, I suspect it’s affecting many services and may not be the fault of the Internet Archive. It affects non-API domains, but I’ve never had an issue on my browser, perhaps because it retries and/or keeps the session open.

$ curl -4 -vIL "https://listenbrainz.org" "https://api.listenbrainz.org"

Output
*   Trying 142.132.240.1:443...
* Connected to listenbrainz.org (142.132.240.1) port 443
* ALPN: curl offers h2,http/1.1
* (304) (OUT), TLS handshake, Client hello (1):
*  CAfile: /etc/ssl/cert.pem
*  CApath: none
* Recv failure: Connection reset by peer
* LibreSSL/3.3.6: error:02FFF036:system library:func(4095):Connection reset by peer
* Closing connection
curl: (35) Recv failure: Connection reset by peer
*   Trying 142.132.240.1:443...
* Connected to api.listenbrainz.org (142.132.240.1) port 443
* ALPN: curl offers h2,http/1.1
* (304) (OUT), TLS handshake, Client hello (1):
*  CAfile: /etc/ssl/cert.pem
*  CApath: none
* Recv failure: Connection reset by peer
* LibreSSL/3.3.6: error:02FFF036:system library:func(4095):Connection reset by peer
* Closing connection
curl: (35) Recv failure: Connection reset by peer

Several downstream applications which neglect to retry requests on failure have encountered issues:

List of GitHub issues

I take back the above: even trying with a single album I’m getting the issue each and every time now.

Seeing this issue as well. Definitely intermittent, but seems to generate on imports that take longer.