Is this a singular occurrence for me, or is it prevalent across the instance?
It keeps saying that my account is not in a ready state.
It also does this for Lemmy ML and Blahaj Zone.
Anyone heard of them being DDOS’d? This certainly sounds like ongoing DDOS and protections kicking in (assuming that by “verify my account” you mean “having to solve a captcha”).
By that, I mean that I can’t check my inbox or look at my profile, only my feed. It doesn’t bring up any captchas.
Lemmy.world has been under repeated attack recently though, and the behaviors you’ve described match what I see when th service is down. You can see current status and the history of frequent incidents at https://lemmy-world.statuspage.io/.
To relate to your statement about what fails and how, I can say I’ve seen the failure-modes change as they adapt the setup, and it’s a more complex stack than other lemmy instances in order to deal with the attacks and large scale. It degrades in complex ways that are hard to fully reason about unless you’re pretty deeply familiar with how things are out together.
I suspect you’re seeing a combination of “lemmy world is broken sometimes”, “Cloudflare gives weird errors sometimes”, and “clients cache things or degrade to unauthenticated connections sometimes”. But in any case, seeing lemmy.world be flaky is not weird, it’s having a heckuva time.
Don’t know about the other 2 but .world has been enduring an on/off ddos attack for over a week, then yesterday had a non ddos related db issue.
They have something that the cyberterrorists want, so they must be doing it right.
I noticed Jerboa saying something about my account being verified on lemmy.world in between 502s and other network errors. I’ve never seen that before, but looks like it’s not exclusive to you.
As long as it’s universal it’s… better? lol
Yeah same with me.
Odd.
Atleast now we know that it’s not user specific.
As an instance owner I can say lemmy.world is a bit of a troublemaker as it will constantly halt and resume federation activities in a very bursty way and cause momentary spikes in resource usage. I have now upgraded the instance enough that it’s not really a problem, just an annoying observation.
Having said that - feel free to test run my instance! The only problem I am currently aware of - gmail outright refuses to accept email from it, so verification is impossible. Thanks, Google! Have not had any reports about other providers, though!
What is your instance?
Is it not visible next to my username?
I didn’t see it im your previous comment.
My instance uses Gmail just fine. Did you setup an app password?
I’m not using Gmail to send email. Gmail refuses to receive email from my instance.
Are you running your own mail server?
Yes, of course! In the spirit of the federation!
Most mail services will block self hosted mail servers because you have no IP reputation or if you’re using a VPS could have an IP that previously ended up on a blacklist.
Yes, but that block is normally in a form of being marked as spam. This is different. Mail gets dropped without ever reaching the recipient’s mailbox.
As an aside, I have been running my own mailserver for years and it’s been working fine since the beginning. Getting marked as spam here and there, but for the most part - fine. I’ll shift the mail setup at some point to have proper dkim support, but for now all I can say is - avoid gmail.
old man shouting at clouds
I understand how spam was a problem and why, at a glance, it seemed like a great idea to simply block any email that does not come from a previously known/trusted IP. However, in my opinion, all this has achieved are two things:
- Massive centralisation of email - nobody can host their own easily anymore. You have to pay to get any semblance of guaranteed delivery
- Dumbing down of the general populace - “you don’t need to understand how any of this works! Here, use our service and it will just work!” Which also makes people complain to me about something as free (liberty) as email not being set up on google or aws. Screw those guys, I want my free internet.
Interesting. I don’t really want to get into troubleshooting, but general curiosity has me wondering a few things since my server gets delivered to Gmail but only marked as spam for a new domain for the first couple weeks.
Is there a hard spf fail? Is your IP or domain on any blacklists? Is it a digital ocean or similar vps provider using their IP pool? Do you get any bounce back from Gmail with a reason or is it silently dropping?
Most mail service will not outright block email. Most seem to be configured to follow a handful of blacklists and build a reputation.
They might start you marked as spam, but few outright block based solely on IP. Spam filters are far more mature than that these days.
As a potential workaround, have a look at a comment I made a while back in a similar context: https://sopuli.xyz/comment/1603292
I am also in nine other instances. But I have some communities on this instance that I don’t know how to move into other instances in case this one goes kaput.
You might want to set-up a backup community on another instance. Then you make a sticky on your current community: if LW goes down, we meet there.
I may do that.
