right I meant more like the app was maybe installed from a package, where the OTP_SECRET was not yet set properly. This was then a packaging bug not a user error.
here we go
Using a private bucket on Hetzner.
S3_ENABLED=true
S3_BUCKET=NameOfYourBucket
AWS_ACCESS_KEY_ID=xxxxxxxx
AWS_SECRET_ACCESS_KEY=xxxxxxxxxxxxxxxx
S3_REGION=eu-central-1
S3_PROTOCOL=https
S3_HOSTNAME=NameOfYourBucket.fsn1.your-objectstorage.com
S3_ENDPOINT=https://NameOfYourBucket.fsn1.your-objectstorage.com
While typing this here, I had the idea to check the create command for a flag and indeed there is --approve:
/app/code/bin/tootctl accounts modify testusername --approve
@archos
Thank you. That command helped. Now I have some broken images next to some profile pictures like using verified status pic (or something). I think, I check that next. But this was a huge help!
I tried the command
bin/tootctl accounts refresh --all --verbose
and after running this command, the avatars started reappearing on our instance. It seems to have resolved the issue. Thank you.
Oh, OK. I thought I could tweak the performance a bit with this since it's mentioned in some "Mastodon scaling" documents I have found. And Sidekiq shows that Redis is using 100% of the allocated memory.
No, I mean just reinstall your Mastodon and start over with your account. As long as the account you want to have named correctly was only ever created on your own instance, reinstalling that instance should reset that username. If you move it, you won't be able to change it (I think).
The new thread is for funding packaging and support https://forum.cloudron.io/topic/11178/custom-cloudron-image-for-elasticsearch
I’m no good with Docker, but what I can do is pool funds and rally people to get it done.
