Cloudron Forum

@joseph Thanks for your answer.

Hi team

It looks to me that cloudron packaged AzuraCast is the rolling release instead of stable. (I see it in the /admin/updates/ section.

Why not use the stable instead? There seems to be many bugs in the rolling release version that make it almost impossible to run a working radio station.

Any thoughts?

Same issue here too.

Problem solved. I deleted ALL config files and restarted the server.

Hi @girish

I have a similar problem (missing certificate so nginx does not start)

root@my:~# journalctl -u nginx -fa
-- Logs begin at Wed 2022-08-03 20:41:55 UTC. --
Aug 03 23:45:02 my nginx[17769]: nginx: [emerg] cannot load certificate key "/home/yellowtent/platformdata/nginx/cert/_.domainnamexxxx.info.key": PEM_read_bio_PrivateKey() failed (SSL: error:0906D06C:PEM routines:PEM_read_bio:no start line:Expecting: ANY PRIVATE KEY)

I find app config files in /home/yellowtent/platformdata/nginx/applications

But the nginx-log messages does not tell what app exactly is creating the problem.

May I delete all config files, or do I have to go "trial and error" with each file to figure it out?

Where do I find the nginx config files for the app relating to the missing certificate?

@nebulon Thank you for having a look at it.

@nebulon said in Increase character limit for toots from 500 to xxxx:

In your case I guess you could fork the mastodon app package and create your own with that patchset.

Holy moly, unknown territory

Hi @nebulon

I am not sure this is directly from upstream docs, but here is one suggestion:

https://draklyckan.se/2021/11/how-to-increase-the-character-limit-for-toots-in-mastodon/

The above article mention these sources:

https://github.com/mastodon/mastodon/issues/12265
https://github.com/kamysheblid/mastodon_max_characters
https://old.reddit.com/r/Mastodon/comments/hozl70/
https://docs.joinmastodon.org/admin/

Hi all

The default character limit for new toots is 500. But I would like to increase that limit for my special instance.

How can I do this? And hopefully make it a permanent change, not overwritten by updates?

Any help?

Re: Graphite stuck starting

Hi all. I have the same problem with graphite stuck starting. I have the same type of log entries to that of @eyecreate , and I have upped the allocated memory, and have tried the @nebulon suggested method of purging graphite database with no luck so far.

What to do?

I had to install 18.04, then install Cloudron 5.5.0, then restore the backed up cloudron, then upgrade it to 6.1.2, then make a backup.
Then destroy the 18.04 and install 20.04 instead, then restore the 6.1.2 backup....puhh. Done, working!

(Could not restore a 26GB Nextcload app, but no problem, had the files backed up locally)

Guess this thread can be marked as solved?

Hold on a minute....seems like restore worked well after all....strange thing....I check it out and report back....

@nebulon

Thank you. I tried using 18.04, installation went well, but when I picked the restore option, filled in the details for downloading my my DO Spaces backup, I tried once and forgot archive encryption key, then filled in the key, but now got error message:

"Already activated. Restore with a fresh Cloudron installation."

Maybe its easier to install a fresh cloudron, and have you guys connect it to the running subscription?

Please advice how to proceed.

Hmm.....

I actually reinstalled the server OS (Ubuntu 20.04) and started all over from scratch.

./cloudron-setup --provider generic --version 5.5.0

Then installation stopped and gave error msg. From /var/log/cloudron-setup.log:

Package mysql-server-5.7 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
  mariadb-server-10.3

E: Package 'mysql-server-5.7' has no installation candidate

So, as the cloudron I try to reinstall is a subscription cloudron (paid), but with no critical information stored on it, would it be easier to just install a fresh latest version cloudron, and have you guys (support) change the running subscription so it is connected to this new cloudron ID?

Hi

I try to restore a backed up cloudron (upgraded server OS), but setup the wrong cloudron version on my new server. Need to revert to older cloudron version that corresponds with the backup version.

Is there a way to force cloudron to revert to an earlier version, or do I simply need to uninstall the cloudron and install the correct version?

What is the best way to do it? Is there a working command for "uninstall cloudron", or do I have to reinstall the whole server OS and start over again?

Thanks

@girish said in New installation, not able to log in:

echo "changeme" | npm run reset-password -- -u root

Thank you @girish. I actually had a lot running on this cloudron, but could not get PeerTube to work even if I removed several other apps to free up memory.

But the above command for some strange reason fixed it and solved the problem. PeerTube is now working!

Thank you

Hi @girish

I tried installing PeerTube on your demo server, and was able to log in to PeerTube using "root" and "changeme".

Full log from my own installation is sent you at support@cloudron.io

@robi I am using it on the dashboard (main) domain, on a subdomain

@rmdes I chose to have the app have its own usermanagement, so LDAP should not be involved?

@robi No user named "root"

@robi Yes

Tried now using a different subdomain, still same problem.