I had a complete mental collapse, as well as some legal troubles that lead me to completely delete all of my Lemmy accounts. I was formerly jawa21, and decided to get an upgrade to jawa22. Like it or not, I am back for good and I am currently working on more edits to post here.

  • Admiral Patrick@dubvee.orgEnglish
    5·
    3 days ago

    On my instance?

    The only issue I’m aware of is the hosted instance of Tesseract I run (for anyone to use) was down yesterday evening / last night because the hosting provider had a DC migration go terribly wrong. My main UI and API are hosted in a different DC and shouldn’t have been affected.

    Just curious b/c if there’s a problem I want to fix it lol

    • jawa22@lemmy.blahaj.zoneOP
      4·
      3 days ago

      I tried for a solid 20 minutes to get beyond the captcha. It three an error every time saying it was incorrect, but not a normal "failed " type error. It was completely broken. And yes your instance

      • Admiral Patrick@dubvee.orgEnglish
        4·
        3 days ago

        Huh. I do show the HTTP 400 responses in the logs for the registration attempts, but not sure why. Maybe my rate limit got triggered? (it’s set pretty low, but hasn’t changed in over a year and have had successful signups since then). I don’t show that it even created the local user, which means it didn’t even process the request.

        AFAIK, nothing in my infra relies (exclusively) on my assets in the NYC DC that was down.

        FWIW, I just did a test signup, and it worked.

        So only things I can think of is:

        1. It failed to send the verification email (I think Lemmy fails if it’s configured to send an email for a specific operation and the email server doesn’t respond).
        2. Rate limit (which you’d think would have been HTTP 429 from the API, but wouldn’t be the first HTTP standard the lemmy devs didn’t adhere to).

        Either way, I’ll keep an eye on it (thanks for letting me know), and again, welcome back.