We'll set up an fresh instance. This is quite simpler.
thanks for help!!!

Thanks - I've done some further testing. You are right - it does work.

Seems the Debian host I was using on Linode (using "Secure Your Server" image) was blocking port 9200 by default so had to adjust iptables to allow external access. Had a hard time tracking that down.

Added:

then saved it. Worked immediately.

@nebulon Thank you for your reply. In the instructions it says that first you have to run the command

To synchronize local data, cache Mastodon media to the S3 bucket.
I guess that would have to be a different command here on Cloudron.
Now my images load, but the local avatars, server image have disappeared from the instance and the remote images and avatars are not loading. Is it possible that the remote images will load gradually, I don't know.
I've been really struggling with this for a few days now and the result is still not good. 😞

@ehson_mokhtary you may also find some clues e.g. in these posts:

https://github.com/cybrespace/cybrespace-meta/blob/master/s3.md

(see e.g. this section https://github.com/cybrespace/cybrespace-meta/blob/master/s3.md#follow-up although I've no idea how you'd do that on Cloudron)

https://chrishubbs.com/2022/11/19/hosting-a-mastodon-instance-moving-asset-storage-to-s3/

Found a solution!

Went into my 4.1.9 app page in Cloudron, clicked Terminal, used the Postgres button to get into DB mode, and typed this in:

Managed to upgrade seamlessly to 4.2.0 after that.

Package is out.

Yes package update is out by now.

Updated package is out.

Never heard about this. Besides, I don't think adding Google Analytics is something that would be welcomed by the Mastodon community.

@nebulon yes with fresh installed mastodon instance it's working fine. Thank you

@mhgcic said in Cloudron + Mastodon + Akamai s3:

We added this solution already and did not work.

S3_ENABLED=true
S3_BUCKET=bucket-name
AWS_ACCESS_KEY_ID=<key_id>
AWS_SECRET_ACCESS_KEY=<secret_key>
S3_REGION=<region>
S3_PROTOCOL=https
S3_HOSTNAME=<hostname>

You seem to be missing the S3_ENDPOINT

They were already applied in https://git.cloudron.io/cloudron/mastodon-app/-/commit/56896d2d63cd22fb5870b11e7394936f5ca7c1c5

@girish next one
https://github.com/mastodon/mastodon/releases/tag/v4.1.4

@dsnradio We do that to prevent source code from being changed either intentionally (user) or malicously (hacker). For the former case, it's to make sure apps can be updated reliably. For the latter, it's for security.

If you want to modify an app , you can build the package yourself - https://git.cloudron.io/cloudron/mastodon-app/ and do whatever changes. Of course, you have to take care of updates as well for the custom installation.

Wow okay. Thank you

@nichu42 good link...

I had a look at https://codeberg.org/Fedimins/mastodon-maintenance-tasks . I couldn't run the script directly because there's a bunch of hardcoded paths in it. Found some commands that maybe we can incorporate. Many of the commands are already in our cleanup script.

(waves) See https://www.thedoodleproject.com/relay for instructions!