sh.itjust.works Main Community

8510 readers

10 users here now

Home of the sh.itjust.works instance.

founded 3 years ago

MODERATORS

TheDude@sh.itjust.works

manifex@sh.itjust.works

biela@sh.itjust.works

imaqtpie@sh.itjust.works

otter@lemmy.ca

oldsh.itjust.works Not Working? (sh.itjust.works)

submitted 2 weeks ago by Kanzar@sh.itjust.works to c/main@sh.itjust.works

5 comments fedilink hide all child comments

Hi folks, anyone else noticed that https://oldsh.itjust.works/ doesn't work anymore or is it just me? Doesn't work for me at work or at home and they're on different setups...

top 5 comments

sorted by: hot top controversial new old

[–] threelonmusketeers@sh.itjust.works 0 points 2 weeks ago

I'm getting a 502: Bad gateway error.

[–] Bluescluestoothpaste@sh.itjust.works 0 points 2 weeks ago

Oh wow, I never knew that was a thing lol, now i really want to try it but it is 502 lol

[–] TheDude@sh.itjust.works 0 points 2 weeks ago (1 children)

Hey all,

We identified bot abuse on this endpoint and temporarily took it down until I can implement some bot restriction on it. I'll bring it back online shortly.

[–] Kanzar@sh.itjust.works 0 points 2 weeks ago

Thanks, greatly appreciated. :)

[–] WolfLink@sh.itjust.works 0 points 2 weeks ago* (last edited 2 weeks ago)

502 typically means something along the lines of the app serving the website wasn’t up when nginx started. Sometimes this is simply a case of programs starting in the wrong order, and restarting nginx will fix the issue. It could also mean the app serving the website is broken.

Whatever the issue is, it’s something for the admin to fix.