@ivan is this the case for both new and old media?
@neatchee yea, everything. i had to set my bucket name to . in the config as it was using s3_bucket/bucket_name/file paths and it's just s3_bucket/file for the digital ocean spaces so I suspect it may be something with how ./ in urls is handled by apps?
@ivan Ahhhhhh that's very interesting. Good to know! Glad you got it sorted :)
@neatchee i fixed it! for some reason it was appending the bucket name to the URL if the bucket name was already in the s3 hostname, but if it wasn't in there, it was correctly inserting it into the hostname instead