I am no longer able to log in or view any content with wefwef. I deleted the app and tried to navigate to the website with my phone.

I am technically able to access the website, but any attempts to login in say “connection error”. Any attempts to view posts say “problem fetching posts”. I have tried multiple instances and none of them work.

Is anyone else having this issue? I am an android user. Thanks.

    • dingus@lemmy.worldOPEnglish
      4·
      11 months ago

      Actually the fix seems to be the same for Android. I first simply deleted the PWA and tried reinstalling, but that didn’t work. I then went into my browsers settings (in thie case Brave), found the site data for wefwef and deleted it like you said. Then I was able to reinstall just fine!

      I don’t understand exactly what happened in the first place to create this error though.

    • Deemo@lemmy.fmhy.mlEnglish
      1·
      11 months ago

      Android assuming the pwa is installed from chrome uninstalling the pwa should auto fox.

      If not opening wefwef from chrome and clearing website data will fix

      Although I haven’t personally experienced any issues iOS and Android

  • wavymoney@lemmy.worldEnglish
    2·
    11 months ago

    For me, it was because I had NextDNS enabled but it worked fine with it on up until now. Wonder what happened. Replying from iOS.

    • dingus@lemmy.worldOPEnglish
      1·
      11 months ago

      What is NextDNS? I’m curious to know what made it stop working as well, although I don’t have any special settings I’ve fiddled with on my phone to my knowledge.

      • wavymoney@lemmy.worldEnglish
        1·
        11 months ago

        DNS is what translates www.website.com into an IP address that allow clients to load content from those websites. Most people use the DNS that come with their ISP. NextDNS is an alternate “translator” with built in Firewall/Adblock options (like a Pi-Hole). I figured after the Clear Safari Data trick didn’t work for me, it was because of NextDNS blocking something that required wepwep to function. I think it was related to that CORS and wepwep proxy thing that was fixed a while ago, but I switched it back on after reinstalling wepwep and it’s all good!

  • skepticalifornia@lemmy.worldEnglish
    1·
    11 months ago

    I was having issues replying - the error told me to set my language in my Lemmy instance. I did that (it was mysteriously blank} and then it started working.

    • dingus@lemmy.worldOPEnglish
      1·
      11 months ago

      I had that issue some time ago, but this one was different. I couldn’t log in or even view content.

    • alexius@lemmy.worldEnglish
      1·
      11 months ago

      I have that same issue, and it’s persistent to the point of not knowing if this comment is gonna post or not.

  • BowtiesAreCool@lemmy.worldEnglish
    1·
    11 months ago

    I had the same issue, I reinstalled the PWA and it seemed to fix it but now I’ve got the safari top and bottom stuck so it’s actually less seamless than even on normal browser