this post was submitted on 08 Feb 2024
21 points (86.2% liked)

Lemmy.world Support

3158 readers
3 users here now

Lemmy.world Support

Welcome to the official Lemmy.world Support community! Post your issues or questions about Lemmy.world here.

This community is for issues related to the Lemmy World instance only. For Lemmy software requests or bug reports, please go to the Lemmy github page.

This community is subject to the rules defined here for lemmy.world.

To open a support ticket Static Badge


You can also DM https://lemmy.world/u/lwreport or email report@lemmy.world (PGP Supported) if you need to reach our directly to the admin team.


Follow us for server news ๐Ÿ˜

Outages ๐Ÿ”ฅ

https://status.lemmy.world



founded 1 year ago
MODERATORS
 

Up until yesterday, this problem didn't exist but today when I was connected to a VPN, I couldn't post either a text or image post. I got this error: SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data

After I disconnected from my VPN, the error went away. What gives?

top 9 comments
sorted by: hot top controversial new old
[โ€“] scrubbles@poptalk.scrubbles.tech 41 points 7 months ago (1 children)

Not an admin of lemmy.world, but have been dealing with a lot of the same crap recently.

Users have been uploading CSAM material behind VPNs. That sort of material can get any of our lemmy instances taken down and us admins are personally liable.

So in short, those very few ruined it for everyone else. My instance also now blocks vpns and tor networks.

[โ€“] mmababes@lemmy.world 25 points 7 months ago

Users have been uploading CSAM material behind VPNs.

Yikes! I understand now, thanks.

[โ€“] ichimokuclown@lemmy.world 7 points 7 months ago

When connected to my VPN, which I am as much as possible, I can not vote, save posts or comment (presumably I can't post either) on lemmy.world. I can understand the admins' motivations given recent troubles, but it isn't a reasonable, privacy-considerate solution.

[โ€“] wesker@lemmy.sdf.org 0 points 7 months ago* (last edited 7 months ago) (1 children)

With zero context, that error doesn't look intentional, let alone targeted at VPN users. I believe it is the result of a malformed JSON payload.

[โ€“] stevestevesteve@lemmy.world 18 points 7 months ago (2 children)

It's the result of the webservice returning an html error page instead of a json response.

[โ€“] solrize@lemmy.world 4 points 7 months ago (1 children)

It would be preferable to return an error response in a json string, if that's feasible.

[โ€“] stevestevesteve@lemmy.world 2 points 7 months ago

Of course it would but I'm just saying what I'm seeing

[โ€“] wesker@lemmy.sdf.org 2 points 7 months ago* (last edited 7 months ago) (1 children)
[โ€“] TootSweet@lemmy.world 6 points 7 months ago

Lemmy-UI's error reporting leaves... much to be desired. It's better than it used to be, but not as good as it could be.