the missing S3_ALIAS_HOST= was the issue in my configuration. Thanks to your guide i got it working now! Thanks a lot
4 Likes
Before I figured out the S3_ALIAS_HOST thing, I did write this blog post yesterday: Will Twitterâs Downfall Give Rise to the Decentralized Cloud?.
I agree with you we should do a followup post, but that said, folks in this thread should definitely check out the last paragraph in yesterdayâs blog post:
if youâre operating Mastodon, Pixelfed, Peertube, Funkwhale, or another federated platform and need affordable object storage, you can sign up today and get a free 150GB of storage on Storj! Weâll also give up to 1 TB-month of storage and 1 TB of egress free if you speak to us to give us your feedback at fedi@storj.io!
7 Likes
Thanks for the confirmation this works by the way!
If itâs interesting, I added this setup to the Mastodon wizard in this pull request: Add Storj DCS to cloud object storage options by jtolio ¡ Pull Request #21929 ¡ mastodon/mastodon ¡ GitHub
5 Likes
Weâve added docs here: Mastodon and Pixelfed - Storj DCS Docs
5 Likes
Iâd like to thank you again. I can confirm everything is running as it should.
But I would like to raise two issues here that we have been thinking about. How does the uplink actually work? My understanding is that Mastodon communicates with the local folder on the VPS and what the uplink does is that it mirrors the files from that folder to StorJ if Iâm not mistaken. But then that would mean that over time I would need the same amount of space on the VPS as well, since it was just a mirror. My idea is to not have to buy a large disk for the VPS, since those attachments will only be kept on StorJ. So, not sure if it can be configured that way, which is why I prefer to ask for reassurance.
The second question is. Iâve done tests with a working portal already, and itâs a pity that if a user uploads something and then decides to delete it, for example, it disappears from the tmp on the VPS, but it still stays on StorJ in the bucket, which is a pity that it doesnât get deleted afterwards, freeing up space. Iâm thinking that if an instance runs for maybe a couple of years, deleted user stuff that no longer points anywhere would make up a pretty large percentage unnecessarily. And I canât think of a way to then sort it away from the chaos of folders manually. Does anyone have a tip on how this could be addressed as well? 
After you switching your storage to Storj it should not store anything locally (maybe only cache).
You may also run periodic cleanup jobs: Setting up your new instance - Mastodon documentation
2 Likes
Iâm following this guide : Hosting a Static Website - Storj Docs
What should I set as prefix for mastodon ?
My instance is currently serving files from link.storjshare.io. But itâs on many tracker block list.
Is there any issues if i change the S3_ALIAS_HOST now ?
The prefix is used as a part of the object name inside the bucket, but can be visualized as a subfolder, to group some objects with the same prefix.
If you do not use prefixes, you can do not provide it.
You need to unblock link.storjshare.io in your blockers.
You can change S3_ALIAS_HOST to use your own custom domain, but the mastodon requires to have SSL, so you need to have a paid Storj DCS account to enable SSL for your custom domain: Setting Up Custom Domains - Storj Docs
2 Likes
Everything went well 
⌠Thank you 
1 Like