7
Unable to post images - Jerboa & Firefox
(mander.xyz)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 18 Jul 2023
7 points (100.0% liked)
Mander
432 readers
1 users here now
founded 2 years ago
MODERATORS
I recently changed the file size limit from 20 MB to 8 MB, maybe that caused the file size problem? I just changed it to 15 MB. But if your smaller file failed too, then I'm not so sure... Do others have this same issue?
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 :)
Hahaha, I'm often guilty of that too. And I think it does make sense in many cases - with physical hardware that one buys, for example, it would not make sense to start very small and upgrade a lot. It is better to start a bit bigger.
But since the server is running on a cloud server that can be changed easily, I can take this luxury in this case. I just have to move a slider, so it's easy to do upgrades gradually:
so tempting to just push that little slider aaaalll the way to the right ๐
Alright then, hold onto your chair, here we go!
๐คฃ wheeeee, I can feel the wind rushing by already
I'm having a different/similar issue today (didn't try yesterday), both Jerboa and Firefox. I get the error "SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data" on Firefox and an error that looks similar to the "too big" error on Jerboa (though the full error doesn't show). It's happening with pretty small images. What's up? ๐
Strange... Nothing should have changed (actually, I changed the settings back to 20 Mb), and space is fine. I've rebooted the server to see if that helps...
Seems to be resolved again, thanks, haha. Appreciate what you do!
Good! So this seems to be caused by a property that is built up over time, and cleared by rebooting the server... RAM, CPU, and disk space seemed fine when I checked before rebooting, so I am not sure what this might be. It could also have been that you tried to upload during a 'CPU' spike. Hopefully it doesn't happen again to you!