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

@jaschaezra true, also something to think about indeed

@msbt That seems to be it. I'm using a Caprover instance of Mino now, whereas the previous instance was hand-rolled and installed. In the previous manual install, the two were different. In this Caprover install, both were the same. What threw me was that most documentation says that the two ARE different. But I fiddled a bit, changing each and seeing what happens, and that's how I got it working. Thank you for the tip!!

Looks like it wants a slightly higher ruby version than that is bundled with ubuntu 20. I guess we can install the ruby version it wants via rvm but this seems like an overkill to remove a warning.

@redegelde For general mastodon tutorials, please see the upstream docs - https://docs.joinmastodon.org/

@CBCUN can you try to add that variable in the env.production file via in the filemanger via the Cloudron dashboard and then restart the app?

@girish this is why need to research before judge this amazing product I had! Great team Cloudron again this is not trash!! This greatest I had.

Solution: ./bin/tootctl media remove has an option --days which defaults to 7 days of not set. Our instance is only 3 days old. Since i did not set the flag it defaulted to 7 days. The system did everything right. There were no files as old or older than 7 days. Accordingly it did not delete anything. Computer smart. I was able to delete the cached media files.

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?