▲ 6 ▼ infosec.pub down (update: back online; was due to anti-bot experiments) (lemmy.sdf.org) submitted 2 weeks ago by evenwicht@lemmy.sdf.org to c/isitdown@infosec.pub 5 comments fedilink hide all child comments “This site can’t be reached” And because infosec.pub is down, I wonder who else can see this post. Surely sdf people will see it, but since infosec.pub is offline then I suppose all other nodes will not see this post in !isitdown@infosec.pub.
[–] jerry@infosec.pub 7 points 2 weeks ago (4 children) It is very much not down. What are you seeing on your end? permalink fedilink source hideshow 4 child comments replies: [–] Pomal@sh.itjust.works 3 points 2 weeks ago (2 children) Jerry’d 😂 permalink fedilink source parent hideshow 2 child comments replies: [–] jerry@infosec.pub 5 points 2 weeks ago (1 child) I implemented some perhaps overly ambitious firewalling in an attempt to keep the ai scrapers at bay, so I suspect it does appear to be down. And I clearly have to find and fix whatever is causing that. permalink fedilink source parent hideshow 1 child comment replies: [–] Pomal@sh.itjust.works 3 points 2 weeks ago Nothing like tearing ACLs in the morning. Are there enumerable patterns for the traffic, have a tcp/app traffic dump you’d be willing to share? permalink fedilink source parent [–] evenwicht@lemmy.sdf.org [S] 1 point 2 weeks ago It works now, but what I was seeing is in the OP (“This site can’t be reached”), which came after a long delay, similar to a firewall dropping packets. permalink fedilink source parent
[–] Pomal@sh.itjust.works 3 points 2 weeks ago (2 children) Jerry’d 😂 permalink fedilink source parent hideshow 2 child comments replies: [–] jerry@infosec.pub 5 points 2 weeks ago (1 child) I implemented some perhaps overly ambitious firewalling in an attempt to keep the ai scrapers at bay, so I suspect it does appear to be down. And I clearly have to find and fix whatever is causing that. permalink fedilink source parent hideshow 1 child comment replies: [–] Pomal@sh.itjust.works 3 points 2 weeks ago Nothing like tearing ACLs in the morning. Are there enumerable patterns for the traffic, have a tcp/app traffic dump you’d be willing to share? permalink fedilink source parent
[–] jerry@infosec.pub 5 points 2 weeks ago (1 child) I implemented some perhaps overly ambitious firewalling in an attempt to keep the ai scrapers at bay, so I suspect it does appear to be down. And I clearly have to find and fix whatever is causing that. permalink fedilink source parent hideshow 1 child comment replies: [–] Pomal@sh.itjust.works 3 points 2 weeks ago Nothing like tearing ACLs in the morning. Are there enumerable patterns for the traffic, have a tcp/app traffic dump you’d be willing to share? permalink fedilink source parent
[–] Pomal@sh.itjust.works 3 points 2 weeks ago Nothing like tearing ACLs in the morning. Are there enumerable patterns for the traffic, have a tcp/app traffic dump you’d be willing to share? permalink fedilink source parent
[–] evenwicht@lemmy.sdf.org [S] 1 point 2 weeks ago It works now, but what I was seeing is in the OP (“This site can’t be reached”), which came after a long delay, similar to a firewall dropping packets. permalink fedilink source parent