this post was submitted on 29 Jun 2021
8 points (100.0% liked)

Lemmy

12680 readers
1 users here now

Everything about Lemmy; bugs, gripes, praises, and advocacy.

For discussion about the lemmy.ml instance, go to [email protected].

founded 4 years ago
MODERATORS
[email protected]
8
Weird issue - timeout when accessing lemmy in firefox (lemmy.ml)
submitted 3 years ago by [email protected] to c/[email protected]
14 comments fedilink hide all child comments
 

For some days now, I get server timeouts when trying to access Lemmy.ml in Firefox.

Weird thing is that I can ping Lemmy.ml from the CLI.

I've got various add-ons installed, mostly privacy focused. How would I debug this?

Thanks

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 4 points 3 years ago* (last edited 3 years ago) (1 children)

Does private mode (plugins disabled) give you the same result? You can also try restarting Firefox in Safe Mode using

Help > Restart with Add-ons Disabled to achieve this.

[–] [email protected] 2 points 3 years ago (2 children)

Yes, private mode with ublock, cookie auto delete, localcdn and deactivated noscript gives me the same result.

I don't have the "restart without addons" option but would also like to try something else first if possible

[–] [email protected] 2 points 3 years ago (2 children)

And it works fine on other browsers?

[–] [email protected] 3 points 3 years ago (1 children)

It works fine on qutebrowser! Pinging works also without issues

[–] [email protected] 2 points 3 years ago (1 children)

Hrm, then ya it has to be either a plugin or cookie issue. I run ublock origin and a few others, so I'm not sure what it could be.

[–] [email protected] 4 points 3 years ago

I agree, maybe just go to about:profiles and create a new "clean" profile and try it there

[–] [email protected] 2 points 3 years ago (3 children)

This is a reasonably weird situation. I had lemmy.ml working on FF yesterday but it stopped when I tried to reply to a post.

Then it didn't work on qutebrowser either, giving me a no server response.

Then it worked again. Sometimes with delay.

Just now I had this message on qutebrowser:

"Error while loading resource https://dev.lemmy.ml/pictrs/image/Q5Xs7Yu8kq.png?format=webp&thumbnail=96 on page https://lemmy.ml/: Server's certificate does not match the URL. Consider reporting this to the website operator, or set content.tls.certificate_errors to ask-block-thirdparty to always block invalid resource loads. Do you want to ignore these errors and continue loading the page insecurely?"

After going the insecure way, the page loaded.

I'm on FreeBSD 13 and behind a VPN. So I dare say it's probably me that's causing the issue..... but thought I'd share anyway. Mostly seems to work at the moment.

[–] [email protected] 2 points 3 years ago

I'll see if I can fix these urls.

[–] [email protected] 2 points 3 years ago

Mmmk those dev.lemmy.ml ones shouldn't exist anymore.