The storage fork: you earlier set vehicle/site images to a private bucket with signed URLs. That's fine for images rendered by your own code. But blog images are different — Hassan uploads an image, gets a URL, and pastes it into blog post body content. A signed URL expires (7 days), so a blog written today would show broken images next week when the signed link dies. So for blog/content images, you want a stable, permanent URL — which effectively means a public bucket (or a public CDN path) for this library, not signed URLs.