This is a new problem for me that started a couple days ago. Using Jerboa and Firefox, I’m unable to post images on this instance. I am able to post images to the same communities using a different instance account. I am getting “network error” and Java errors (I’m unable to see the full error) while using Jerboa. On Firefox, I get an “image too large” error for 12 MB (edit: not GB, that’d be a huge image) images (not sure the limit) but “SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data” at smaller image sizes. I was able to post images on this instance before this. My Jerboa app is up to date. Any solution?
Oooo I meant 12 MB for the image I was trying to upload earlier, not GB! That’d be a big image, haha.
I am still getting “network error”/“timeout” errors on Jerboa when uploading smaller images. I can deal with the limit if I know what it is. Even my smallest images (255 KB) are getting this error on Jerboa.
I have checked and I get this error too in Jerboa when uploading to Mander but not Lemmy.ml… I will investigate, thanks.
For the browser you only had the problem with the 12MB file, right?
Yes, smaller images work on browser!
Can you check again in Jerboa now? It seems to work now for me. I am not sure what the problem was, I just did a bit of a cleanup to make space and rebooted the server.
Seems to be fixed! Thanks! Is the limit under 10 MB now? I tried a couple things just over that, but then a sub-8 MB pic worked fine.
Yes, 10 MB at the moment. The reason is because I noticed several very large image files (~ 40 MB) being fetched through federation, and these are filling up the disk… So I set a smaller limit until I figure out how to avoid having the disk filled so quickly.
This isn’t a solution to that problem, but perhaps it’s a good time to check in again and ask of there’s any material assistance that would be helpful from the community? You take on what must be increasing costs, and there are many here who appreciate the instance and would be glad to make a small towards additional drives or whatever else might be needed.
That’s very kind of you, thank you! The cost is still $20.3 /month, it’s really no problem!
I also learned about the ability to prune a table in the database which saved me about 30 GB of space, so my server is over-equipped at the moment.
If it sounds like I am being cheap with my resource resource frugality, it’s not really about not spending the money :-P I am interested in how this thing scales, and I try to pay attention to see how the use of resources is changing. I try to keep the server at a level in which it runs smoothly and then upgrade it only if I see that the performance deteriorates. I want the network to grow by having more people making instances, and it is important that the price is kept manageable, and especially so for people who may want to set up instances in countries in which computational resources are more expensive and salaries are lower.
This makes sense. Sometimes my/our reflexive habit is More!, Bigger!, Faster!, and see where that’s gotten our planet… Well, thank you for what you do :)