Lemmy.ca Support / Questions

488 readers

7 users here now

Support / Questions specific to lemmy.ca.

For support / questions related to the lemmy software itself, go to [email protected]

founded 3 years ago

MODERATORS

[email protected]

A couple of mod related issues (lemmy.ca)

submitted 5 months ago* (last edited 5 months ago) by [email protected] to c/[email protected]

5 comments fedilink hide all child comments

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

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.
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:

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.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 1 points 5 months ago* (last edited 5 months ago) (3 children)

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

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

[–] [email protected] 1 points 5 months ago (1 children)

Are you still having these issues?

Yes, 2. No, 3. No

[–] [email protected] 1 points 5 months ago (1 children)

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?

[–] [email protected] 1 points 5 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.

load more comments (1 replies)