Cloudron Forum

For anyone doing a setup on Cloudron, I found my way here. I was specifically trying to set up monitoring of a Minio instance on my installation. Install Prometheus normally. No special configuration is needed. When you do mc admin prometheus generate ALIAS, you will need to make sure you set that alias up as having enough permissions to actually read everything. Using an alias that has limited access controls (e.g. read-only on a single bucket) will not work; Prometheus will not be able to query the Minio API. Once Prometheus has a positive health check on the Minio instance, you can then set up Grafana. Install normally. When you add Prometheus as a data source, per above, just use the HTTPS URL of the Prometheus installation on Cloudron. No port is needed. The user must be a valid cloudron user. You might want to create a new cloudron user called "prom-graf" or similar, and only give that user permission to access Prometheus. This is just to isolate the access from (say) a standard account you use for all your other tasks/work. Add that username and password in the "basic auth" section. At this point, you can add some dashboards. I used the "import" option, and copy-pasted JSON from these dashboards: https://grafana.com/grafana/dashboards/13502-minio-dashboard/ At that point, I had dashboards living for my Minio installation. I have no idea yet what log volume will look like, or rotation, or... or... but, I might update this thread (or start another) later as I discover those things. I found myself having to dig around for this information/experiment. Perhaps I just didn't read the correct docs.

The second command seems promising.. It looks like it is writing to a hardcoded file /app/code/wallabag/wallabag-export.json (since it's a very old version maybe it didn't write to stdout) . Put the app in recovery mode - https://docs.cloudron.io/apps/#recovery-mode . this makes the filesystem writable In one web terminal, just run /app/pkg/start.sh . this runs the app and creates paths In another web terminal, try running the second command and check if that /app/code/wallabag/wallabag-export.json was created ... if it was you Download it using the Download button in web terminal ? or copy it to /app/data and use file manager .

Maybe there is some initial startup race in the package. Tbh I am not sure if we can recommend using that, given that we have hit a few issues and there was really not much interest by users, and thus it hasn't really reached a stable package state yet. For a start is this error easily reproducible when reinstalling?

@nebulon ah, thanks, I hadn't realised the seemingly unstable state of upstream. But, yeah, it seems a least some of the many issues we have with the Cloudron package aren't only with the Cloudron package.

does mastodon support threads yet?

@stoccafisso I think I am able to reproduce this in one of our managed Cloudrons. Looking into the fix.

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?

@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

@niko was there any error restarting cloudron-firewall service or such? This should still work as expected, so maybe you hit a bug somewhere? Also could you share your ports.json config here so we can try to reproduce this? If you don't want to expose your port settings here, you can also send them to support@cloudron.io

@timconsidine said in Test installation refuse to install apps: @stoccafisso said in Test installation refuse to install apps: Fresh Ubuntu 18.04 server 18 ?? very old version On 31 May 2023, Ubuntu 18.04 LTS will reach the end of standard support. I thought that I read Cloudron no longer supports Ubuntu 18. Yeah, I was about to say the same. I'm pretty sure the latest version of Cloudron do not support Ubuntu 18.04 any more. @stoccafisso I'd recommend starting with a fresh 22.04! (or at least 20.04, but I see no reason not to start with 22.04)

@girish Just as a quick add-on, if you have Comcast business class, port 25 may be allowed by calling the business support line. Same with ATT.

@stoccafisso I have put this in our 4.1 roadmap - https://forum.cloudron.io/topic/1789/what-s-coming-in-4-1 . The feature is already supported in our backend (dataDir field when calling the configure route) but the UI is hidden. We will work on making it public.

From what I understand, the device you are trying to connect from does not support any of the ciphers which Cloudron is requesting. We are following the security guidelines of the following communities: https://bettercrypto.org/static/applied-crypto-hardening.pdf https://mozilla.github.io/server-side-tls/ssl-config-generator/ https://cipherli.st/ https://raymii.org/s/tutorials/Strong_SSL_Security_On_nginx.html So we likely won't support outdated or insecure ciphers from the platform side.

@murgero Thanks for your suggestion! I have put the new healthcheck url in https://git.cloudron.io/cloudron/wordpress-app/commit/45dc91cd7868bd2e66ea726f0968c4752279812e . Will push out the update slowly and see if it causes any issues

@marcusquinn said in Plume: but with ActivityPub by design. This! Here is the repo.

Negative review at:- Stride by Atlassian Reviews https://alternativeto.net/software/stride-by-atlassian/reviews/

Alright, just for future similar issues, here is the solution : sudo -u www-data php -f /app/code/occ files:scan "username" https://docs.cloudron.io/apps/nextcloud/#rescan-files