Can be a few things:
- Username already taken (check https://lemmy.world/u/username replacint
usernamewith yours - Password too long (I'll find out what Lemmy's max currently is)
- Username too long (20 is max)
this post was submitted on 17 Jun 2023
8 points (90.0% liked)
Lemmy.World Announcements
29099 readers
4 users here now
This Community is intended for posts about the Lemmy.world server by the admins.
Follow us for server news 🐘
Outages 🔥
https://status.lemmy.world
For support with issues at Lemmy.world, go to the Lemmy.world Support community.
Support e-mail
Any support requests are best sent to [email protected] e-mail.
Report contact
- DM https://lemmy.world/u/lwreport
- Email [email protected] (PGP Supported)
Donations 💗
If you would like to make a donation to support the cost of running this platform, please do so at the following donation URLs.
If you can, please use / switch to Ko-Fi, it has the lowest fees for us
Join the team
founded 2 years ago
MODERATORS
@ruud Thanks for the quick reply! It was probably the password then (generated with password manager). Will try again
It’s possible they closed registration. That’s what happens when I tested it on my instance.
Not saying for your instance. But other random ones. It’s why I just set mine to applications only and kinda says “I’m not really open for users but shoot your best shot”
I had this, had to try later. Think server overloaded.
Server isn't overloaded. It's sleeping. ;-)
Wow, suprises me that the CPU usage it so low with a community of 30k people! Perhaps it helps that Lemmy was written in Rust (and that you have a beefy server)
Currently only the server logs shoe the errors when signing up, kind of annoying to not know whats the issue as a user.
Figured out you can't use thee same email twice by looking at my own server logs. Same of you don't match passwords perfectly, another silent fail for the user.
You can try on a different server
For me it's lemmy.ml, I can't sign up to this instance.
It’s possible they closed registration. That’s what happens when I tested it on my instance.
view more: next ›