Hi @girish Thank You for reply. I think I found the most recent manual. Can you take a look at it?
https://github.com/Coffeedon/Cofffee-Assets/blob/main/README.md

@jdaviescoates I have indeed. I believe that something must have happened to my block storage, as I since noticed that it was no longer mounted at all. Unfortunately I think the images are simply not there at all.

In terms of things I had personally shared, that is just a lost cause now I believe. No major harm done there. But regarding avatars and images from remote posts, is there some way that I can force Mastodon to re-download these rather than trying to pull from a local source that doesn't actually exist?

@girish said in IPv6 for Mastodon - how?:

@stormgrass This one - https://docs.digitalocean.com/products/networking/ipv6/how-to/enable/#on-existing-droplets . Did you do this?

Ah, no, that point I missed. Am trying to fix it now, but the yaml indicated in the doc doesn't exist. So, I've created it and get hit with a syntax error, even though it's a copy of the contents specified.

Anyway, I'll keep investigating, but I think you can mark this as resolved now. Thank you!

YES. It does work. I have two different Mastodons using two different domains, and they are fine. Hope this helps anyone else with the same question.

@girish Thank you, that did the trick! Not entirely sure how and why my install looked the way it did. I think I installed it first thing once it showed up in the app store, but back then it was still marked as unstable. Anyway, it's all good now, thank you!

does mastodon support threads yet?

@girish Confirmed. I also found my description in the meta-tags. Okay, that's how it (the page design) works.

Problem solved.

Once again: Thank you very much!

Greetings

Eismer

@murgero Thank you! I think, resigning from the relays will help. Your answer helped me a lot to understand some things about Mastodon.

Have a nice weekend!

Eismer

I have put a note in our docs and also in the postinstall message.

@doodlemania2 You can probably find a github of a filterlist that has most nsfw instances blocked for you.

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

@username said in How to install Elasticsearch on Mastodon?:

Do I need an external server, or should I install an elasticsearch app on Cloudron, or can I install it directly from the Ubuntu via code.

You will need an external server because we don't support installing additional packages on the server since it might break updates. At some point we do plan to integrate ElasticSearch into Cloudron. I think some other apps like nextcloud require this as well. For the moment, just install it on a ubuntu or equivalent outside Cloudron.

@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 Thanks. Some of this was just oversight on my part. But the advice you have given is very useful. All working/good now!

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

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