if I try to login anyway, I get this error:

HandshakeException: Handshake error in client (OS Error: CERTIFICATE_VERIFY_FAILED: certificate has expired(handshake.cc:393))
    • Throwaway2D@lemmynsfw.comOP
      link
      fedilink
      arrow-up
      5
      ·
      edit-2
      1 jaar geleden

      I was also thinking the same, but why is this only happening when trying to log in through an app? Visiting lemmy.ml with any browser still works

      Plus I managed to log in using Thunder on a different device, but not on this one

      • HonkyTonkWoman@lemm.ee
        link
        fedilink
        arrow-up
        2
        ·
        1 jaar geleden

        Are you able to login to that instance with a different client on the same device?

        Just curious, wish I could be more help. I went through the same thing three times before I realized I misspelled my instance.

  • AlexDrago@ani.social
    link
    fedilink
    arrow-up
    3
    ·
    1 jaar geleden

    Make sure you don’t have a extra space after the ml, I’ve had login trouble because of that a few times lol

    • Throwaway2D@lemmynsfw.comOP
      link
      fedilink
      arrow-up
      4
      ·
      1 jaar geleden

      Nope, doesn’t work. This is probably related to my device, it’s very old

      if I try to login, I get this error:

      HandshakeException: Handshake error in client (OS Error: CERTIFICATE_VERIFY_FAILED: certificate has expired(handshake.cc:393))
      

      Adding this to OP

      • u000@lemmywinks.xyz
        link
        fedilink
        arrow-up
        2
        ·
        1 jaar geleden

        This might be the openssl bug that gets triggered by certificates from letsencrypt which in addition to an up-to-date CA cert also includes a more widely trusted, but by now expired CA cert (from my understanding of it anyway)

  • BinarySystem@lemmy.world
    link
    fedilink
    arrow-up
    2
    ·
    1 jaar geleden

    What Android version are you using? I forget what the cut off version is but some of the older Android versions had their certificates expire which is what I think is causing this problem. Not sure that there is a work around for Thunder right now :/