When I first got the app there were timeout errors happening occasionally but in the past few days they’ve gotten to a point that has made the app unusable.

I post a lot. A week ago I’d be able to post anything. Now? I have to hit “Post” about 10-15 times before it’ll go through. Each time it cycles and then says “Error Uploading Image”. When it eventually gets around to uploading it, it will suddenly say “timeout”. Often times that means it’s posted but it will frequently double post the image.

If I’m trying to load my profile or anyone else? 30 second loading time that ends in a timeout. It takes usually 3 attempts to be able to see my own profile. Deleting posts from my profile is utterly impossible and I’ve been forced to use an alternate app for deleting the duplicate posts.

Trying to load any specific community instead of looking at the home screen? Timeout. I tried doing it 7 times on this community before giving up and just attempting to post this without even seeing the community.

Messages also have the same issue. They’ll take forever to load and frequently time out.

I’m going to uninstall and reinstall to see if that helps. Just figured I’d report the issues considering they’re relatively extreme. Wondering if anyone else is having the issue or if it’s just me.

Edit: The install cycle seems to have helped. Everything loaded a lot faster and I was able to see my profile immediately. For anyone who may have the same issue.

Edit 2: Nope. I take it back. If anything the problem has gotten worse. The front page is now showing a timeout and I cannot open anything in the app at all.

Edit 3: Apparently there has been issues with a couple of other people using a different app so, yea. Probably my server or some other fediverse problem. Ignore me and my dumbass.

  • Traister101@lemmy.today
    link
    fedilink
    English
    arrow-up
    13
    ·
    1 year ago

    I think your instance is screwy. Trying to look at it on web browser and it’s timing out for me. Boost just like with Reddit doesn’t host anything itself. On Lemmy you mostly talk to the instance you log into from what I understand so any timeouts or network issues are likely a problem with your instance.

    • Stamets [Mirror]@startrek.websiteOP
      link
      fedilink
      English
      arrow-up
      1
      arrow-down
      4
      ·
      edit-2
      1 year ago

      Not likely. While the server is having an issue at the moment the problem has been pervasive for days, well before any issues with the server started cropping up. Moreover, other apps are able to do the exact same things with zero resistance. At the moment the Connect app is struggling but yesterday the same problems were happening and Connect was gliding like there was no issue.

      • platypus_plumba@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        1 year ago

        Timeouts can’t be caused by the client. The client is making the connection to the server, the server response is taking longer than it should. This is a server side problem.

  • OminousOrange@lemmy.ca
    link
    fedilink
    English
    arrow-up
    9
    ·
    1 year ago

    Sounds like more of an instance issue than a Boost issue. The only time I’ve experienced a timeout was when I forgot my instance had planned maintenance.

  • frogfruit@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    8
    ·
    1 year ago

    Did your instance upgrade to an unstable release because my old one did that and that’s what happened. It’s been broken ever since so I switched

  • Night Monkey@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    4
    ·
    1 year ago

    Maybe clearing the cache would help but since you deleted the app and restarted it, I guess it’s the same thing but more extreme

    • Stamets [Mirror]@startrek.websiteOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      When it reinstalled my login information was all still plugged in so I don’t think it did actually. That’s a good point. I should try that.