I have upgraded to 1.3.1 from 1.2.1 and my existing DigitalOcean Spaces bucket is suddenly using a different directory within the DO Space. It was originally under BUCKET//storage/uploads etc... but is now using BUCKET/storage/uploads...
I'm not sure if there is any way to fix this, as all of the images and content from my website and app are currently unavailable as it is under the impression that the images no longer exist?
we may have had a bug before with the path...any chance you can rename or move data?
It's a lot of data but I should be able to move the data across to the new directory that's been created. They're still appearing as files in the Appwrite Console, the files themselves are just not accessible.
[SOLVED] DO Spaces creating new bucket after upgrading to 1.3.1
Recommended threads
- Realtime for files() works almost well, ...
I have been trying to make use of realtime, today (14.03.26) I have pulled all the latest versions of docker images, and sdk available. Whats working: - Conn...
- Error getting preview of file
Rest Response: ``` { "message": "Server Error", "code": 500, "type": "general_unknown", "version": "1.8.1" } ``` Appwrite Logs ``` appwrite ...
- Storage images using custom domain retur...
Some of the images uploaded to my storage bucket returns this error: ``` { "message": "Project with the requested ID could not be found. Please check the value...