Conversation

Notices

1. Embed this notice
   SolSoCoG (solsocog@ieji.de)'s status on Monday, 14-Apr-2025 22:31:06 JST SolSoCoG

   Updated the server (including postgres) so i stopped mastodon and was doing something else that... more or less made me forget to start it back up. Crap, sorry. :schmusekadser: . I was literally like "wait, 17% cpu usage, I forgot to start something something didn't I? oof."

   • Embed this notice
     SolSoCoG (solsocog@ieji.de)'s status on Monday, 14-Apr-2025 22:59:37 JST SolSoCoG

     • Sexybiggetje🐖

     @martijn yeah :tom_scott:

   • Embed this notice
     #honobono (honobono@ieji.de)'s status on Wednesday, 16-Apr-2025 06:59:12 JST #honobono

     in reply to

     @SolSoCoG 1) Onion seems down. 2) Clearnet over Tor is less reliable than it used to be. Did you add some kind of anti-ddos, which may pre-emptively block Tor users who are doing nothing bad?

   • Embed this notice
     SolSoCoG (solsocog@ieji.de)'s status on Thursday, 17-Apr-2025 01:58:56 JST SolSoCoG

     in reply to

     • #honobono

     @honobono I did add some blocklists, but obviously left out tor exit nodes blocklist, I've started adding tor ips to a whitelist. But yeah you are right, some exit nodes are blocked for abuse.

   • Embed this notice
     #honobono (honobono@ieji.de)'s status on Thursday, 17-Apr-2025 15:24:48 JST #honobono

     in reply to

     @SolSoCoG Thanks for your helpfulness.
     Could you connect to http://iejideks5zu2v3zuthaxu5zz6m5o2j7vmbd24wh6dnuiyl7c6rfkcryd.onion/ ?
     Also, https://ieji.de/ still may time out too, though trying several exit nodes.

   • Embed this notice
     SolSoCoG (solsocog@ieji.de)'s status on Thursday, 17-Apr-2025 17:37:49 JST SolSoCoG

     in reply to

     • #honobono

     @honobono oof. I got the issue now. Didn't change the hidden service IP when we got new IPs, my bad. Fixed now.

   • Embed this notice
     #honobono (honobono@ieji.de)'s status on Friday, 18-Apr-2025 19:24:26 JST #honobono

     in reply to

     @SolSoCoG thx

   • Embed this notice
     #honobono (honobono@ieji.de)'s status on Wednesday, 30-Apr-2025 18:00:34 JST #honobono

     in reply to

     @SolSoCoG https://iejideks5zu2v3zuthaxu5zz6m5o2j7vmbd24wh6dnuiyl7c6rfkcryd.onion/ is down again ^^;

   • Embed this notice
     SolSoCoG (solsocog@ieji.de)'s status on Wednesday, 30-Apr-2025 20:37:06 JST SolSoCoG

     in reply to

     • #honobono

     @honobono then its most likely a blocked abused exit node now :|

   • Embed this notice
     SolSoCoG (solsocog@ieji.de)'s status on Wednesday, 30-Apr-2025 21:13:22 JST SolSoCoG

     in reply to

     • #honobono

     @honobono issue resolved + whitelisted all exits now.

   • Embed this notice
     #honobono (honobono@ieji.de)'s status on Wednesday, 30-Apr-2025 23:47:29 JST #honobono

     in reply to

     @SolSoCoG Working now, ty! But correct me if I'm wrong. A hidden service (.onion) is exit-node-agnostic, isn't it? A malicious node can't mess with .onion connections, unlike Tor connections over clearnet - isn't that the whole point of a hidden service?

     Besides, it's hard to abuse an onion address due to PoW, isn't it? Why do you have it if you block it (and not even sending the Onion-Location header)? Tor abusers have started giving you a hard time?

   • Embed this notice
     SolSoCoG (solsocog@ieji.de)'s status on Thursday, 01-May-2025 23:19:47 JST SolSoCoG

     in reply to

     • #honobono

     @honobono Uhm you'd think so. But i noticed that connection was aborted and the ip that was shown as exit node was on blacklist, after whitelisting it was working again. Well the thing is crowdsec works with community effort so if a thousand servers report a ip as malicious (and some other consensus magic so it can't be poisoned by bad actors false reporting) it gets blocked by all other crowdsec users. Plus i have subscribed some firehol blacklists. Not especially tor.