Conversation

Notices

1. admin de gnusocial.net (administrator@gnusocial.net)'s status on Tuesday, 28-Feb-2023 02:27:12 JST admin de gnusocial.net

   in reply to

   • Alexandre Oliva
   @lxo Ok, you are right, it was "libresoc64". I blocked it for... you know, making too many concurrent connections.
   Try now, it should work (it your IP is not already blocked).
   • Alexandre Oliva (lxo@gnusocial.net)'s status on Tuesday, 28-Feb-2023 02:27:13 JST Alexandre Oliva
     nice, but then I wonder what it is that's blocking based on User-Agent... it's pretty clear that this is what's happening, it's entirely reproducible, and the error message is different from the one I get when an IP address is blocked, because the TLS session is actually established, then abruptly aborted, whereas IP blocking prevents it from being established
     now, I haven't even been able to make even *regular* accesses for weeks, because of this setting, and the accesses you're seeing in your logs are either normal browser-based access while I tried to figure out what was going on, or *sequential* page preloads from my scripts for offline reading and archiving, neither of which has ever got IPs blocked. but access with a modified user-agent... that amounts to an instant block on the very first connection, and only when accessing gnusocial.net.
     now, maybe it's not about GNU in User-Agent, maybe it's libresoc? or something else?
     Here's what I was using before, that stopped working a few weeks ago: "Mozilla/5.0 (X11; GNU libresoc64; rv:94.0) Gecko/20100101 Firefox/94.0"
     while what works now has 'Linux x86_64" instead of "GNU libresoc64", and the actual, current version numbers.