Most interesting: the problem had only been happening on MS Edge on my laptop. I have been using safari on my phone without issue. Just a bit ago, i refreshed the page and now every time I revisit the site, I have to log back in, just like on Edge. It’s like the old session expired and the new ones aren’t sticking. I’ll try FF on my phone.
Note: even in the time I started typing this reply to when I hit the “add comment” button, I got logged out
This annoys me about the fediverse - people take a chance on coming here and then repeatedly get left in the dark when their instance is shut down. That's why I was so very happy when you and others helped me get fedia.io back to healthy.
I moved fedia.io away from fastly. I have a nagging feeling it has something to do with fastly. Can you let me know if you continue to see this?
It really is great and we’re very lucky to have the mbin team that we do. I sincerely appreciate them, as should everyone on fedia.io and the other mbin instances.
I’ve had quite a lot of experience in interacting with the mbin team and I can definitely say they are kind and compassionate people who have a passion for this project and have shown nothing but helpfulness and grace to me and many other people.
If you can, please try again. If you still have problems, shoot me an email to jerry@infosec.exchange and I'll troubleshoot the issue
ok - there was a problem with the mbin queues on fedia - I think that may have caused the problem with registrations. Can you give it another shot? Also, if that doesn't work for whatever reason, please shoot me an email to jerry@infosec.exchange so I can debug the issue.
Mbin has some rough edges still but I like the interface much better than lemmy (I also run a lemmy instance so feel ok comparing them)
I activated your account. I will figure out email when I get back home in about 90 minutes.
Can you shoot me an email at jerry@infosec.exchange and I’ll track it down for you? My apologies for the trouble.
I have so many errors in prod.log that it's hard to tell for certain, but when I try to filter out those that are associated with failed federation events, that seems to be when I'm left with. I am trying again to see if I can confirm