7
submitted 4 months ago* (last edited 4 months ago) by LimpRimble@lemmy.ca to c/lemmy_ca_support@lemmy.ca

Not a high priority because I can still do what I need to. Might be related to the latest upgrade.

  1. When I go to reports in a /c that I mod, "Unread" gives me an unending wait, hourglass, spinny thing that doesn't time out. "All" seems to work fine so I'm not stuck.

  2. When I click on a user's name I get an error page:

Error 1033 Ray ID: 8935e13f1e7c6064 • 2024-06-13 23:32:26 UTC Argo Tunnel error

What happened?
You've requested a page on a website (lemmy.ca) that is on the Cloudflare network. The host (lemmy.ca) is configured as an Argo Tunnel, and Cloudflare is currently unable to resolve it.

Edit:

  1. I haven't been able to cross-post since the upgrade - the page comes up like it's ready to cross-post, but if I touch anything like "Select community" for example, all the fields clear and I'm left with an empty "Create a post" page.
top 5 comments
sorted by: hot top controversial new old
[-] Shadow@lemmy.ca 2 points 4 months ago* (last edited 4 months ago)

I'll do some digging this weekend. Can you try clearing your browser cache just to rule it out?

I suspect the update introduced some slow database queries again, I've run into the timeout while browsing uploads.

I think the cross post thing is a known reported bug.

[-] Shadow@lemmy.ca 1 points 4 months ago* (last edited 4 months ago)

Are you still having these issues? I can't reproduce either of them.

Crossposting: https://github.com/LemmyNet/lemmy-ui/issues/2537

[-] LimpRimble@lemmy.ca 1 points 4 months ago

Are you still having these issues?

  1. Yes, 2. No, 3. No
[-] Shadow@lemmy.ca 1 points 4 months ago

Which browser are you on? Can you try an incognito window?

Can you also check your error console (f12) for any errors when it does the spinning?

[-] LimpRimble@lemmy.ca 1 points 4 months ago

Good call on the F12. A quite locked down Firefox reports:
Content-Security-Policy: The page’s settings blocked the loading of a resource (media-src) at data: because it violates the following directive: “media-src http:”
I suspect it's the HTTP that's causing the issue because I have it set to only accept HTTPS. But that's just a guess, I'll look a little deeper when my head is clearer.

Thanks for the help.

this post was submitted on 13 Jun 2024
7 points (88.9% liked)

Lemmy.ca Support / Questions

483 readers
11 users here now

Support / Questions specific to lemmy.ca.

For support / questions related to the lemmy software itself, go to !lemmy_support@lemmy.ml

founded 3 years ago
MODERATORS