B
Since it is all still legal jargon my reaction is always 
There is in interesting read tho https://opensource.org/blog/modified-agplv3-removes-freedoms-adds-legal-headaches
Neo4j Precedent: A recent court case (Neo4j v. PureThink) suggests licensors (like Rallly's maintainers) might enforce added restrictions (e.g., paid licenses) even if AGPLv3's Section 7 allows licensees to remove "further restrictions." This could complicate removing the nag banner/user limits.
Soooo . . .
@necrevistonnezr
Oh yea, you are right!
Had no Idea this is going on.
Thanks for the info!
@hpz24 did this resolve it? Just want to have this "task" 
checked in my brain 
@hpz24
OH! That is because I have a typo in my release!
The /tags/ part in the docker image "url" was wrong. Silly me 
Correct is - brutalbirdie/foundryvtt.cloudron.app:1.1.0
# go into /tmp/ download the manifest, update $LOCATION, delete the manifest and go into $HOME
cd /tmp/ && \
wget https://raw.githubusercontent.com/BrutalBirdie/cloudron-foundryvtt/refs/tags/13.342/CloudronManifest.json && \
cloudron update --app $LOCATION --image brutalbirdie/foundryvtt.cloudron.app:1.1.0 && \
rm CloudronManifest.json && \
cd ~/
hey @CadeHenschen there are very specific documentations and step-by-step guides for distribution upgrades:
See here: https://docs.cloudron.io/guides/upgrade-ubuntu-20/
@leemuljadi said in Cloudron Backup for Moving to Another VPS:
is this how to install cloudron with specific version?
According to the official documentation:
https://docs.cloudron.io/backups/#restore-cloudron
wget https://cloudron.io/cloudron-setup
chmod +x cloudron-setup
./cloudron-setup --version x.y.z # version must match your backup version
If you run:
cloudron-support --send-diagnostics
It will generate all information needed for support and give you an URL to view all the information.
Will look something like this:
========================================================
Linux
========================================================
Linux my-DOMAIN-TLD 6.8.0-60-generic #63-Ubuntu SMP PREEMPT_DYNAMIC Tue Apr 15 19:04:15 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
========================================================
Ubuntu
========================================================
Distributor ID: Ubuntu
Description: Ubuntu 24.04.1 LTS
Release: 24.04
Codename: noble
========================================================
Cloudron
========================================================
Cloudron version: 8.3.2
Dashboard domain: DOMAIN.TLD
[...]
@leemuljadi said in Cloudron Backup for Moving to Another VPS:
use Vultr and install Cloudron from the marketplace
I am not sure this type of setup offers a version selection on installation.
Time to get your own hands dirty (= If you need any help, let the forum know.
This is very undescriptive. Could please guide me step by step what you are doing and at which point you fail?
Never heard of them before, and only you mentioned them so far in this forum
Implementation might be easy, but the question is, how many would benefit from that.
Question about prioritization 
I would suggest for now using Hetzner.
I take your Coffee donation as a solved notion? Thanks again for the Coffee 
In the moodle app view you have to add the following CSP:
frame-src https://library.example.com;
did you do that?
Note: add not override, keep the defaults and add the frame-src
More details about frame-src => https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Content-Security-Policy/frame-src
It could be that the TTL of the PTR record was set really high by your ISP 24 to 48 hours.
So it might be that simply waiting will solve this
@osobo said in How can a Calibre web URL be embedded in a Moodle iFrame?:
In Cloudron I've modified the Calibre-web CSP as following
You need to edit the CSP of the moodle app to allow calibre as an iframe embed.
You just did it vice versa
Did the same once for peertube and Bookstack so I could embed peertube videos into bookstack for video guides / documentation.
Hello @arta you can use the n8n cli to reset all users.
See: https://docs.n8n.io/hosting/cli-commands/#user-management
You can reset user management using the n8n CLI. This returns user management to its pre-setup state. It removes all user accounts.
Use this if you forget your password, and don't have SMTP set up to do password resets by email.
Go into the Cloudron n8n web terminal and run:
gosu cloudron /app/code/node_modules/.bin/n8n user-management:reset
Hope this solves your problem 
I always feel silly when asking such questions.
But, can you try to clear your browser cache? 
And also maybe clear the Freescout cache => https://github.com/freescout-help-desk/freescout/wiki/Clearing-the-Cache
Agree it should not be run as root. but if everything runs as root, should work, right?
ps uax
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 1 0.0 0.0 2696 1408 pts/0 Ss+ 07:32 0:00 sleep infinit
root 105 1.0 0.0 0 0 ? Z 07:37 0:51 [python3] <de
root 270 10.4 0.0 0 0 ? Z 07:45 7:26 [python3] <de
root 1101 0.0 0.0 5144 3968 pts/2 Ss+ 07:58 0:00 /bin/bash
root 1736 0.0 0.0 4588 3840 pts/1 Ss 08:25 0:00 /bin/bash
root 1748 0.0 0.0 4324 3328 pts/1 S+ 08:25 0:00 /bin/bash ./s
root 1797 0.0 0.1 63092 15104 pts/1 Sl+ 08:26 0:00 uv run manage
root 1800 0.7 2.9 1165820 234612 pts/1 Sl+ 08:26 0:13 /app/code/.ve
root 1811 13.6 3.4 1911068 272500 pts/1 Sl+ 08:26 4:00 /app/code/.ve
root 1918 0.0 0.0 5016 4096 pts/3 Ss+ 08:27 0:00 /bin/bash
root 2108 2.5 0.0 5016 3968 pts/4 Ss 08:56 0:00 /bin/bash
root 2120 0.0 0.0 8332 3968 pts/4 R+ 08:56 0:00 ps uax
This error is also already report upstream:
https://github.com/freescout-help-desk/freescout/issues/4768
//edit oh that is you @vadim
Might not be related to Cloudron then at all.
@staff might roll back the release if it is confirmed it really is an upstream issue.
@luckow @tobiasb // ping for you since I know you use freescout very actively.
Thanks for reporting, will have to look into that.
For now I've identified the following folders as runtimeDirs meaning, they need read-write access. Explanation behind runtimeDirs in the context of Cloudron => https://docs.cloudron.io/packaging/manifest/#runtimedirs
Many are the case because __pycache__ is being written into them and also from migrations:
"runtimeDirs": [
"/app/code/horilla_documents",
"/app/code/payroll",
"/app/code/.venv/",
"/app/code/facedetection",
"/app/code/geofencing",
"/app/code/helpdesk",
"/app/code/pms",
"/app/code/recruitment",
"/app/code/accessibility",
"/app/code/asset",
"/app/code/horilla_api",
"/app/code/offboarding",
"/app/code/horilla_audit",
"/app/code/horilla_crumbs",
"/app/code/horilla_automations",
"/app/code/horilla_backup",
"/app/code/horilla",
"/app/code/attendance",
"/app/code/onboarding",
"/app/code/horilla_views",
"/app/code/biometric",
"/app/code/employee",
"/app/code/leave",
"/app/code/base",
"/app/code/notifications",
"/app/code/project"
]
This is "meh".
The core application should be read-only, I remember I tried to do:
uv run manage.py makemigrations
uv run manage.py migrate
uv run manage.py compilemessages
inside the Dockerfile to have all that as read-only but then there were still errors
Will have to look into that again.