@jamescridland maybe to take a step back here, what is the reason to run such commands? The media cache is already maintained by the running app ondemand.

I will mark this as solved as many users have succeeded to use s3 for media storage already.

This applies to any open instance (matrix, rocket.chat, etc.), maybe it's best to have this thread pinned in "Discuss"?

@LoudLemur said in Can we join Cloudron.io Mastodon? What's everyone's URLs to follow?:

climate change (I am sceptical about this)

Sorry, sceptical about what, exactly? The very widely empirically measured over decades heating of the planet?

@shanelord01 You can ignore the recommendation. I think it's a hint for developers to optimize (and maybe sysadmins to report back to upstream project of bug/issues).

@scooke I'll report back! As long as you've copied everything over, then you can remove public/system.

@nebulon thank you

@davidneuner there is nothing "to fix". On a given instance you see the content of users on that instance and the users they are following. To see content from other instances you need to follow other users. a relay (as suggested by @doodlemania2) can help seed some content for you to follow.

Yesterday, we pushed a package which prunes the cache a bit more aggressively - https://git.cloudron.io/cloudron/mastodon-app/-/commit/87e046061335a04c96cd9a133c4bf679caeacb2a . Atleast, in our instance, that brought down the cache size from 12G to almost 2GB.

@girish im going to try it again today to see if itll work

@girish One thing I noticed actually is that theres another 2 backups I cant go back to. All same error. The only one that I can is from 2 days ago. All have the same problem. And I am 100% sure I used it AFTER those

@nichu42 Thanks, seems to have solved the problem!

@doodlemania2 thanks, wil do that.

@girish
Perfect :-), Thanks a lot. I used the complete name...:-)

@ericyu00 yeah, it does username login only for LDAP and that also depends on how LDAP is setup. That is this bug report - https://github.com/mastodon/mastodon/issues/11362

@nebulon Hi, think it was an combination. The place was growing and some users get an 500 in there screen. Also posting does not work, I discover lak of space so increase the server."
At the same time i saw when i was looking to the logs Known handler error lines.

This is still the case, but site is working good, no complains
GET /well-known-handler/nodeinfo 404 Not Found No custom well-known config 0.804 ms - 71
GET /well-known-handler/host-meta 404 Not Found No custom well-known config 1.776 ms - 71
GET /well-known-handler/webfinger?resource=acct:redegelde@mastodon.education 404 Not Found No custom well-known config 0.889 ms - 71

Good services,
enough space(48 GB used of 168,9GB

so ift this is no problem, leave it i think

@nebulon Thanks! If that´s the case, we will be patient and wait for it to find its way upstream.

@jdaviescoates said in Opening Up Registration:

will start a new topic about it now...

As promised

https://forum.cloudron.io/post/55988

@ericyu00 If you write to DO support, they usually open it up.

@johav What is wrong with this Dr. Jo? Makes sense... your name and your company name... perfect.

Do you mean changing to openscicomm.access2perspectives.org?

Or, jo.openscicomm.com?

Clearly it will be too lengthy to do https://openscicomm.int.cpn.edu.rs!

This here says you changing your username is basically making a new account, then directing the old username to the new one/new instance.

At any rate, if you are doing this on Cloudron, it's really a simple thing to just start over with the domain name you want. Just be sure that the root domain is one you control because the root needs to have a domain on Cloudron for Mastodon to work (check out the "Federation" section at https://docs.cloudron.io/apps/mastodon/).