The server's images are stored and served using object storage.
The object storage provider has sent a message stating that they will perform a 12-hour migration tomorrow, March 10th, from 8:00 AM – 8:00 PM CET, so downtime of the object storage service is expected. Site images will likely not be displayed during this time.
In these past days users have reported issues with image uploads. I suspect that the issue is related to this same migration. If so, images should be back and the upload issue resolved by tomorrow night. If uploads are still causing problems I will investigate further.
Anyone else having trouble uploading images? Here is the message I am getting.
null
{"data":{"files":null,"msg":"Invalid status 403 Forbidden for None - <html><body><h1>403 Forbidden</h1>\nRequest forbidden by administrative rules.\n</body></html>\n\n"},"state":"success"}
This might be a silly question and I might have missed the info, if it is posted somewhere, but is there a way (and need) to support this instance financially? I like it here and would love to help out a bit. I'd offer any other kind of help needed, but I'm not tech savvy, so money would have to do.
Edit: The issue appears to have been some intermittent problem and it was solved (perhaps by chance) a few minutes after contacting support.
I woke up this morning to find out that the images are not accessible through the site.
This seems to be an issue on the side of the object storage provider, as the "bucket" is not accessible through the provider's web portal. I have reached out to them to hopefully sort this out ASAP.
clicked sumbit, and it simply ate my msg. Redrew a blank form.. no way to recover the info loss. This is my 1st use of the onion, so I did not think to enable 1st party j/s (which is strangely off be default in noScript on Tor Browser despite clearnet sites having 1st party js enabled by default). It’s unclear if it’s a JS problem or if it’s because the onion version uses a quite old/classic reddit-like theme. In any case, it sucks.. it’s a defect for sure.
When I'm logged in, if I follow an external link (from lemmyverse.net, for instance) to here, the tab that opens is not logged in, and stays that way even if I navigate around the instance. If I then open another new tab, and directly visit mander.xyz, I'm logged in correctly as normal.
I'm wondering if anyone else is experiencing this? I don't know what could cause this or how to find out if it's a bug with lemmy, mander, or my browser config.
It only happens with images. I only browse on mobile, android. I've had it happen in Firefox and the boost app, haven't tried it anywhere else. Let me know if I can provide any other info that will help.
This only happens to me with mander.xyz, and consistently happens every evening with nearly all images. Maybe 1 out of 20 times I'll get lucky and an image will load. There are too many communities I like here so I haven't just blocked it yet, hoping it can be fixed eventually. :)
Edit: I did see that other post about broken images but it looked like the error was different from the one I always get so I made a separa
Anyone else noticing? It seems to be affecting other instances as well, since instances hot link to eachother.
The rate limiting seems to get much worse in the evenings.
lemmy.world:
mander.xyz:
json
{
"code": "object-request-error",
"msg": "Invalid status 429 Too Many Requests for Some(\\"01/90/24/ad/1d/8d/7e/8a/82/ee/7104ff150707.png\\") - {\n \\"message\\":\\"Too many requests\\"\n}"
}
After all these recent upgrades, updates and improvements, things are going veeert smoothly and fast!🔥 I think this comment I made about a week ago about experiencing slow responses is no longer valid!
Sal and anyone else who helped, you did a great job! Thank you!☺️
Since this update required some manual intervention anyway to update the database version, I took the opportunity to perform some overdue server maintenance and upgrades.
I have migrated the server to a more powerful configuration, and changed the way image files are being stored and served (object storage as opposed to filesystem storage).
I am also aware of some federation issues that have affected this and other instances. I am not sure whether this upgrade will deal with these problems automatically. I will be looking into it and hopefully will implement some solution soon.
Sorry for the downtime experienced in the past few days, but hopefully with the more powerful server the experience will be smoother and will remain so for a while.
For other admins and users interested, this is a bit of information about the server
About 2 weeks ago, kbin.social went down due to maintenance issues, but it seems like federation hasn't been restored on this instance.
Specifically, I am subscribed to https://kbin.social/m/greece which federates with lemmy.world, but on this instance posts since 2 weeks ago and later dont seem to be federating.
Could you please check it and maybe re-enable it in the future?
(I know that currently there's a migration happening and we'll soon(?) update to 0.19.4, so this issue I'm pointing may have to wait till all these finish first (or updating may fix it without any extra work)).
Sorry if this seems like a silly question but I have noticed over the last few months my feed(?) has started to act odd.
No matter what I do I don't see any posts from .world. I checked and mander does not seem to block .world (kinda why I liked this instance) and even weirder is how my feed gets filled with mostly .ml posts with almost no activity no matter how I sort.
This did not happen before and got me thinking, I don't even know how this works across federated instances.
Does anyone know:
How does the sorting work on an instance? Is it all the same no matter what instance it is?
Did anything change in the last few months, that would cause all .world (and I assume others) posts to not show?
Other then changing instances what can I do to mitigate the weird slanted results?
I woke up and noticed that the server was down. I think that there were two different issues happening at once - one related to nginx, and the other related to a memory limit I recently set on a docker container. Issues are fixed now. Sorry!