S3 Compatible Storage

[joseph]

I think you have to add these to /app/data/env ? There is no .env in Cloudron deployment.

[Divemasterza]

correct it is in /app/data/env - unfortunately not working.

[scooke]

Two examples I've looked at use the S3_REGION parameter, and my personal experience is that it IS required.
https://formbricks.com/docs/self-hosting/setup/cluster-setup#s3-configuration
https://github.com/formbricks/formbricks/blob/main/.env.example

Do any of the other parameters you've set work and its just the S3 deets that aren't working, or is it the entire env/.env file that isn't being read?

[joseph]

@scooke S3_REGION you mean ?

[scooke]

I am Canadian, and I bought a macbook pro in switzerland, with swiss keys, but improperly laid out, so it's a constant battle to type correctly - I use stickers, and of course the proper US keyboard.

[scooke]

OK, since I like doing this kind of stuff, I installed Formbricks just to see where it might be going wrong. I am using a Minio install using runtipi on another server, made a special bucket and user for this test, plugged that info into the /app/date/env file (including REGION), BUT I also added

# Enable for S3-compatible storage that requires path style
# 0 for disabled, 1 for enabled
S3_FORCE_PATH_STYLE=1

I don't know why or how or what, but there is/was some issue in the Minio/S3 world where an update made all future bucket paths virtual_path_style, or maybe it was the other way around? Anyway, I find I need to include this so that my buckets are https://s3.example.com/bucket, rather than https://bucket.s3.example.com.

I then uploaded an image for a background in a survey, and it did, and it saved, and I can see it in the bucket. SO, it is working. Good luck!

[andreasdueren]

@scooke Which provider are you using? I tried R2 with no luck

[scooke]

@andreasdueren Provider for minio? AT any rate, I posted the above after just installing formbricks to see if I could help the OP, then I uninstalled it. I'm no help now!

[Divemasterza]

Ok, I finally resolved it on my side, and it was caused by the CORS policy on the S3 buckets. The policies were too restrictive, and obviously it wasn't working.

[andreasdueren]

@Divemasterza Which provider is this? R2 doesn't work, seemingly because it doesn't support the S3 POST Object operation