Thanks. I have not changed anything recently. I am also blocked from uploading. Not sure yet what the problem is, I am looking into it.
Mander
No problem. Happy hunting! ๐
I think it is the object storage provider... I see that there is a scheduled migration for 12 hours March 10th, but I suspect that they may have already started moving things around.
Makes sense!
I contacted support this morning as the issue persists. They confirmed that it is related to their migration, but they have not been able to give me a specific time for when it will be resolved.
Any news today? I miss pictures.
Only that I am frustrated at the object storage provider (Contabo), and now I see why their reputation is not great. Their reply was that they sent a warning about the "12 hour downtime during March 10th".... but obviously these effects have extended both to before and after this "12 hour downtime". At least I got confirmation that this problem is due to their migration.
Hope they are at least cheap.
They are cheap. But I think that at the current total cost I would be able to improve performance while keeping cost about the same by migrating the instance to a dedicated server instead of a VPS + object storage.
I would be willing to toss a couple of loonies a month at it if it helps with the instance.
Thanks! <3 Cost is not the issue. The reason why I selected this option was because it seemed a good choice at the time. Moving the image database around is a bit of a hassle so I chose to just keep it as it was even after learning of other options. Last time it took several days of downtime to move the images over because the transfer speed into/out of the object storage is very low.
If I would have known that this would happen now, I might have taken this opportunity to move all the images over. But I was not expecting this amount of downtime. Now I worry that trying to move images from one place to another when the object storage is acting up is risky, and also I am busy.
I sent another message to support this morning and received:
We are sorry for the inconvenience caused. Please note that our technicians are working diligently on this matter, there is no ETA.
Sorry ๐
Let's test
Hmmm yes I also get an error upon trying. I'm using Boost though. Not sure how else I can help
Np, I pinged Sal :)
Also having various nginx and 500 errors!