Cloudron Forum

Nice!!!! Good work!

"net::ERR_CERT_AUTHORITY_INVALID" this error means your client PC has a CA issue, not your cloudron. This is likely cause the cert didn't update after changing the default domain (I assume is what you are doing). Is it working now that it's sat for a minute, it may have renewed that cert.

@matt-derrick Checkout his readme for information on installing: https://github.com/BrutalBirdie/cloudron-foundryvtt?tab=readme-ov-file#how-to-install-from-public-image

@Package-Updates This update is very important! It fixes a CVE

From the Github directly: This release further fixed some CVE Reports reported by a third party security auditor and we recommend everybody to update to the latest version as soon as possible. The contents of these reports will be disclosed publicly in the future.

I assume you've looked here as well: https://docs.cloudron.io/apps/adguard-home/#doh

Is the service enabled in agh? Also check the ports used by agh in the cloudron dashboard to confirm it's using the correct port

I believe you have to modify the content security policy: (note: this is the default for LAMP, not sure what you need for moodle but a google might help: Moodle CSP allow iframe or something)

I'm up-voting this app cuase this is a neat idea! But for those looking to have this now or try it out early before it gets adoption into cloudron (if at all) it is PHP based and can be installed into the LAMP app!!!

I would backup everything and then in a new linode vps install 24.04. Then cloudron on that new server. Then restore the backup data. Once you confirm the new cloudron is online fully and working you simply turn off the old one and point all the DNS records to the new one (if not already) then wait a few days to make sure everything is good then delete the old one.
https://docs.cloudron.io/backups/#restore-cloudron

If you want the former follow in order:

1. https://docs.cloudron.io/guides/upgrade-ubuntu-22/
2. https://docs.cloudron.io/guides/upgrade-ubuntu-24/

The terminal for most apps (if not all) default to login as "root" so this is by design. Restarting fixes the perms cause the startup script switches them to whatever the app needs (in wordpress's case it's www-data" if you wanna make it like that from the get go:

Use either: chown www-data:www-data <whatever dir>

Or: su - www-data then mkdir where ever you need it: mkdir <whatever dir>

Essentially open source, decentralized discord clone? I like it.

@ccfu oh ok so node is also not in the path for www-data. Try this instead:

• Add the Node binaries to PATH:

  • Run command: PATH=$PATH:/usr/local/node-18.18.0/bin/

• Now run npm or node:

  • Run command: npm clean-install

Note - you will need to run that PATH command everytime you reset the www-data session (so whenever you login/logout to the terminal or via ssh / etc)

Use the full path to it as it is probably just not in the $PATH var for www-data:

/usr/local/node-18.18.0/bin/npm <args>

Unstable just means its new and in testing (it could still be unstable) but you can install it to test

Ah then sadly there might not be away, unless it's just enabled and you need to make an account via the admin panel? (if there is one?)

@Botch8891 during install just select "Leave user management to the app"

@Dreamcatch22 SSH using the public key you made during installation (either while installing cloudron or the OS you may have made one as the server is asking for it).

Sounds like the ldap plugin disables itself on update and need to login with some kind of local account to re-enable maybe?

@cylon You might need to restart the systemd service that handles your DNS if it's not the one documented by cloudron

@cylon the doc I sent tells you how to setup an upstream dns server which should resolve your issue.