Re: "stream shutdown error"

In: s/Bubble

I haven't added IP logging mostly because it hasn't been required and because of the potential privacy implications. An option to enable it would be good to have, though.

In this case, someone is likely sending malformed/non-TLS data. If this is a recurring event, blocking the IP is probably the only countermeasure.

However, IP-based blocking is not supported at the moment either.

I was curious if this had happened on my Gemini capsules, and the answer is yes. Here are my error stats since November 1st:

 225  http request
 114  unsupported protocol
  49  wrong version number
  49  version too low
  30  no shared cipher
  28  no suitable key share
  17  packet length too long
  15  bad key share
  11  tlsv1 alert unknown ca
   5  protocol is shutdown
   4  ssl/tls alert unexpected message
   4  ssl/tls alert bad certificate
   1  ssl/tls alert certificate unknown

The packet length errors have been sporadic. Most of them occurred on November 19. Could just be a misbehaving crawler?

🌆 skyjake [mod, sysop]

2025-12-10 · 5 months ago

🌒 s/Bubble

🐦 roughnecks:

stream shutdown error — 2025-12-09 23:04:21 [0] -- Problem: [('SSL routines', '', 'packet length too long'), ('SSL routines', '', 'record layer failure')] stream shutdown error: [('SSL routines', '', 'shutdown while in init')] How comes logs have no remote IP address? I don't have any other clue on why/how this is happening.

💬 1 comment · 2025-12-09 · 5 months ago