Trying to login with the MLMYM interface just goes to a blank screen for me. Is anybody else having issues with it? Is there anything I can do to get it working?

Edit: I have no idea why a simple help post is getting this many upvotes / downvotes

  • AwesomeLowlander@lemmy.dbzer0.comOP
    1·
    5 months ago

    What would you need from me? I’m on Firefox, Linux Mint. Logging in from the front page does nothing, I end up at the same page again while remaining unlogged in. Going to the login / registration screen and logging in from there takes me to a blank page.

    • Unruffled [he/him]@lemmy.dbzer0.comEnglish
      1·
      5 months ago

      Hmm, ok, I’m on Ubuntu Firefox and was just able to log out and then back in no problem. Just trying to narrow down the issue in case it was a browser thing. I’d suggest next to try logging in using a private browser window so all your extensions are disabled and see if it works then.

      • AwesomeLowlander@lemmy.dbzer0.comOP
        2·
        5 months ago

        Still happens. Console has the following errors (and nothing else) when I login via https://old.lemmy.dbzer0.com/login

        Cookie “ShowNSFW” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite login

        NS_ERROR_FILE_NOT_FOUND: 10

        • Unruffled [he/him]@lemmy.dbzer0.comEnglish
          2·
          5 months ago

          Hmm interesting. The NS_ERROR_FILE_NOT_FOUND error

          I can think of a few more things to try:

          1. Can you try clearing cookies and site data and then try login again?

          1. Try creating a new profile in Firefox. If there is some profile corruption this may fix the issue.
          2. Go to page about:support and then you should see the option to refresh firefox or enter troubleshooting mode.
          3. Try a different browser such as Edge or Chrome, just to see if problem persists.
          4. Try creating a new account on lemmy.dbzer0.com and then login with that account. If that works that would tell us if it’s something to do with your lemmy profile settings.
          5. Try installing a fresh copy of Firefox via a different method (e.g. snap package or flatpack, or deb). The file not found error suggests it could possibly be linked to a file permissions or storage issue, so this may help.

          Obviously, you will lose your current Firefox settings with some of these actions, so caution is advised.

          Sorry I can’t be more specific, it’s hard to know specifically what’s causing the issue since I can’t replicate.

          • AwesomeLowlander@lemmy.dbzer0.comOP
            1·
            5 months ago
            Can you try clearing cookies and site data and then try login again?

            No dice.

            Try creating a new profile in Firefox. If there is some profile corruption this may fix the issue.

            No dice.

            Go to page about:support and then you should see the option to refresh firefox or enter troubleshooting mode.

            Didn’t want to lose my settings, didn’t try. Probably doesn’t matter anyway, since…

            Try a different browser such as Edge or Chrome, just to see if problem persists.

            Chrome doesn’t work either.

            Try creating a new account on lemmy.dbzer0.com and then login with that account. If that works that would tell us if it’s something to do with your lemmy profile settings.

            Awaiting verification.

            Try installing a fresh copy of Firefox via a different method (e.g. snap package or flatpack, or deb). The file not found error suggests it could possibly be linked to a file permissions or storage issue, so this may help.

            Probably not, since Chrome is having the same issue.