• Welcome to the Chevereto User Community!

    Here, users from all over the world come together to learn, share, and collaborate on everything related to Chevereto. It's a place to exchange ideas, ask questions, and help improve the software.

    Please keep in mind:

    • This community is user-driven. Always be polite and respectful to others.
    • Support development by purchasing a Chevereto license, which also gives you priority support.
    • Go further by joining the Community Subscription for even faster response times and to help sustain this space
  • Chevereto Support CLST

    Support response

    Support checklist

    • Got a Something went wrong message? Read this guide and provide the actual error. Do not skip this.
    • Confirm that the server meets the System Requirements
    • Check for any available Hotfix - your issue could be already reported/fixed
    • Read documentation - It will be required to Debug and understand Errors for a faster support response

Delete picture (S3 compatible in It still exists )

shaohua

Chevereto Member
Delete picture (S3 compatible in It still exists )

Delete the image in the website, the external pure storage still exists
 
I can confirm that this is true.
I got 90K+ pending images on backblaze with s3-compatible API processed by CRON jobs, all images are still in the bucket. I have no idea how I will delete all of them now.
I used b2 cli tool to make sure that image is physically present in these buckets to rule out cloudflare cache or server cache.
 
Last edited:
After further testing, I could not replicate this bug.
For backblaze, it takes time for them to remove file from their bucket. I think once deletion is requested, they put it in their internal queue, and their cleaner deleted it when queue is hit.

When I tested it with Digital ocean spaces, it was deleted instantly. So, I think this is not a bug.
 
When I tested it with Digital ocean spaces, it was deleted instantly. So, I think this is not a bug.
It is important to remark that bugs that could be affecting S3 Compatible vary a lot as providers so I think that we should at least wait for the OP response. Perhaps it was just the cron?
 
we should at least wait for the OP response
Yes. I didn't mean to hijack OP's post. I had similar bug, or so I thought, but it turned out it wasn't a bug afterall. I was just clarifying about my report.
OP's issue might be different than mine.
 
Dear @shaohua could you please provide more context for this? Did you tried with the cron setup?

Is this still an issue for you?

Kindly keep us updated.
 

Chevereto Cloud

Back
Top