this post was submitted on 24 Jul 2023
3 points (100.0% liked)

Programming.dev Meta

2469 readers
2 users here now

Welcome to the Programming.Dev meta community!

This is a community for discussing things about programming.dev itself. Things like announcements, site help posts, site questions, etc. are all welcome here.

Links

Credits

founded 1 year ago
MODERATORS
[email protected]
[email protected]
3
I can't log into pd in jerboa? (programming.dev)
submitted 1 year ago by [email protected] to c/[email protected]
4 comments fedilink hide all child comments
 

So, it used to work just fine. Then jerboa became basically unusable due to some bug. That was a few weeks ago. I saw an update was available, so I thought to give it another try. It's much more stable after the update, and my lemmy.one account works just fine. But when I try to log in with this account on jerboa, I get an incorrect login error. I set the instance to "programming.dev" and I know I used the right credentials because my password manager filled them in, just like it does in the browser.

Any ideas on a cause or fix? It might be a jerboa issue but I don't get why it seems to only impact this instance.

top 4 comments
sorted by: hot top controversial new old
[–] [email protected] 4 points 1 year ago (1 children)

programming.dev has been unavailable a couple of times recently, that's what is probably happening.

[–] [email protected] 3 points 1 year ago

There’s an issue out for it, but mod actions like banning users pretty much brings instances to their knees, especially when the user has done a lot, and propagating it to the fediverse causes those instances to have the problem too.

[–] [email protected] 2 points 1 year ago

I had this same problem, after clearing my Jerboa data it worked fine. Hope that helps

[–] [email protected] 2 points 1 year ago

I’m working on a client and have noticed programming.dev has issues with login fairly frequently, while other instances like lemm.ee and lemmy.world do not. It only happens per-IP address so it might have something to do with rate limiting or blocking suspicious clients that connect. Hopefully this can be fixed down the road.