@girish Thanks. Some of this was just oversight on my part. But the advice you have given is very useful. All working/good now!

@doodlemania2 Everyone else must be running HUGE services that don't need relays haha.

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

Filtering out all the Anime pr*n is somewhat annoying, but I've managed to get a decent stream of good fed people going!

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.

OK, we found that the issue was related to having a reverse proxy in front of Cloudron. This reverse proxy was not configured properly to forward web sockets.

For nginx, we need something like this:

map $http_upgrade $connection_upgrade { default upgrade; '' close; } server { .... proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection $connection_upgrade; ... }

For apache, we need something like this:

RewriteEngine on RewriteCond ${HTTP:Upgrade} websocket [NC] RewriteCond ${HTTP:Connection} upgrade [NC] RewriteRule .* "wss:/192.168.20.12/$1" [P,L]

For the moment, one can just use SSH to open a web terminal like this:

docker ps -f label=fqdn=app.domain.com docker exec -ti <containerid_from_above> /bin/bash

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