I'm having massive troubles with using lemmy.ml since around the time of the update. The website doesn't work at all, #Jerboa crashes on every start, and even in #Lemmur, some operations end in handshake (or other) errors. Furthest point to which I could debug was: When opening https://lemmy.ml and ignoring the erroneous certificate, the browser shows the content of join-lemmy.org This is from using it from Middle Europe, I've seen in another thread that it seems to work from North Americe. Maybe this helps?
this post was submitted on 24 Feb 2022
7 points (88.9% liked)
Announcements
23294 readers
1 users here now
Official announcements from the Lemmy project. Subscribe to this community or add it to your RSS reader in order to be notified about new releases and important updates.
You can also find major news on join-lemmy.org
founded 5 years ago
MODERATORS
Doesn't work for me as well. Have already reported this on the matrix channel. Both admins seem to be offline atm.
And we're back.
I hope that Lemmy will have in a future a server infrastructure like Google to rule instead the web.
I've been unable to make any posts of any kind today. Was there a server update that turned that off?
Same!
Phase 1:
Phase 2:
Phase 3:
And that's where it sticks forever. Longest test run was over an hour.
Indeed whenever I try to upload anything (including the images used in this report that I eventually had to host at imgur) I get this popping up briefly:
That might be a useful data point.
Strange, this should have nothing to do with the server upgrades. Can you check if there is any additional info in the browser console?
I have the same problem (every browser). On my console:
https://files.catbox.moe/avhei6.jpg
https://files.catbox.moe/k5px97.jpg
https://files.catbox.moe/pg0cbh.jpg
And can't upload any image, give this error:
Those dont look related to me. Does it also happen when you make a post without link?
no, without link works well: https://lemmy.ml/post/180482
Looks like this issue then, will be fixed in the next release.
I fixed it by restarting pictrs. No idea why pictrs locally stopped doing image uploads, but it was stalling things out. That timeout fix should fix it for the next release.
👍 thanks
If I were a browser console, where would I be hiding?
(I'm an embedded developer, not a web one.)
Also what would I be looking for?
Press [F12], that should bring up the developer tools, and select the console tab. Then do the action that fails and see if something gets logged in the mean time.
I fixed it now, was an issue with our picture server. Sry about that.