I seem to recall that there may be tools out there to help this, but your googling will turn up whatever that was just as quick as mine.

I would say that I tried doing this myself, twice, and by the second time I decided to handle it manually. That is, I downloaded and saved (I know, I should have done better saving the originals) the various graphics my site used, as well as my list of contacts, etc., and then re-uploaded them to the new location, then relinked them from within Mastodon. The first time the migration didn't work, there was no one who could help, and it was just quicker to do it manually. All the graphics connected to other users were eventually repopulated anyway, and anything I had wanted previously I had downloaded and saved. So, in a way, there wasn't a need to migrate anything. Good luck.

@jayonrails the avatar link is set in the OIDC responses. that's the only situation where cloudron's profile pics are used in apps.

the second link (everything on the second link)

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.

Thank you for the explanation, I didn't know that.

@johannesjom me too 🙂

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:

@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!

Package update is out.

Thanks for sharing and good to know they are aware of at least and might come up with solutions.

I tried the command

and after running this command, the avatars started reappearing on our instance. It seems to have resolved the issue. Thank you.

Thanks for the rapid execution! 😍

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.

I was logged in to my dashboard as jdaviescoates and into Mastodon as uniteddiversity and what I wanted to do was to login to Mastodon as josef

@girish said in Can't switch user because of OIDC issue:

@jdaviescoates you are probably logged into the dashboard as well.

I was, but as a different user...

But, actually, it seemed I was somehow logged in as both.

So, I just logged out of my dashboard as jdaviescoates but I was immediately still logged in, but as uniteddiversity

I'm not sure how that happened/ was possible - because how did I manage to login as jdaviescoates in addition to uniteddiversity?

I mean, surely I would've had to logout as uniteddiversity in order to be able to login again as jdaviescoates - but I guess, not, somehow 🤷

@girish said in Can't switch user because of OIDC issue:

We are going to look into OIDC logout support from next release.

Sounds like that is a pretty important thing to support, thanks! 🙏

thanks - that did the trick 🙂

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).

@rmdes said in Custom Cloudron image for ElasticSearch:

I'd certainly contribute with funding, even more if the app can then be used by other cloudron apps (if possible)

Nextcloud being such a candidate