@robi hmmm, that's a good question. I was under the impression that some text is mandatory. But having tried it, Mastodon certainly allows it. And the RSS feed looks like this : { "title": "xxxxxxx: “”", "link": "https://xxxxxxxxxxxx", "pubDate": "Sun, 26 Sep 2021 19:56:22 +0000", "enclosure": { "url": "https://xxxxxxxxx.png", "length": "14690", "type": "image/png" }, "content": "", "contentSnippet": "", "guid": "https://xxxxxxx", "isoDate": "2021-09-26T19:56:22.000Z" }, So it works. Although my n8n workflow to crosspost to Twitter would likely break, but I will try that later when I'm feeling braver.

@michaelf in the new package there is a /app/data/config.sh that you can edit to tweak the settings . https://docs.cloudron.io/apps/mastodon/#scaling

@debossnow In Cloudron you can easily change the domain of any app by using the gear icon and the location section menu.

@freetommy DM me here and I'll share details.

@scooke Thank you for valuable information!

@nebulon Thanks you, maybe, this is client-side issues by chrome plugin extentions or PC antivirus, ... etc... I test on other client PC. no issues. Thanks again !

@girish Wow you are amazing as always!

@girish This is part of my problem I posted about yesterday (in fact mastodon.host doesn't even work via HTTP anymore), but also, note the Sidkiq errors I mentioned that might be somewhat related to relays in general.

@jodumont This is a general problem at the Cloudron level. So, let's follow this up at https://forum.cloudron.io/topic/3653/fyi-issue-during-uninstall

Thanks! Fixed

@girish Thanks!

@necrevistonnezr said in Mastodon shown as running, but won't load: Is it just me or is there a general problem with the new Postgres version? We have heard of some issues with postgres but so far it's been related to migration issues and not the database itself. We are fixing the migration code so this doesn't happen again. What happens during migration is: we export the old database, run new postgres, reimport the database. The re-import takes a lot of memory and it's dependent on how much data you have in postgres. The fix we are making now is to give the database more memory when re-importing and then scaling it down after the import is over. If you hit the above, the fix is easy, just give postgres more memory and restart the code with systemctl restart box. It will them re-import (it keeps track that it failed the last time around).

I manually installed Mastadon on a Digital Ocean 1Gb droplet (unrelated to Cloudron), and with only 1 user and 5 posts, it ran out of memory. I bumped the droplet up to the 2Gb option and it ran smoothly.

@girish Yes, that did the trick - thank you so much! The package version 1.1.1 works for upgrading to Mastodon 3.1.2. Thank you for resolving that so quickly.