@dsp76 Yes, this could be an useful feature to let access backends only authorized users. So, VPN could be used both: to lock all the apps, or only backends.
p44
Posts
-
VPN protection for certain routes -
Can't make app VPN protection workI think if we do a simple IP whitelist/blocklist, the onus is on the Cloudron admin to manage all this. Users come and go, move between places, have dynamic IPs etc. But sure, this can be added to, if it's seen as beneficial over VPN.
Vurrent VPN system is perfect and gives a certain level of granularity.
-
Can't make app VPN protection workOne question: why did you guys opt for this VPN protection vs simply allowing users to define a white list of source IPs or domains from where the access would be allowed? Would be much simpler and not require the VPN hassle (no matter on an endpoint or a router).
I tried to use Blocked IPs & ranges feature adding all IP’s list unless the specified IP but VPS became unresponsive.
I agree to enable an allow list that, when enabled, blocks everything unless specific IP.
-
Security issue thread - PHP and eMudhra cert compromise@jdaviescoates Thanks a lot, how I can run this without installing Cloudron CLI? Eg. directly from App command line.
I think if this problem is on scale, devs should release a fix also to address this specific issue...
Edit:
@jdaviescoates I installed Cloudron CLI and I used this string that you posted above:
for a in $(cloudron list | awk '$5=="stopped" && $3=="org.wordpress.unmanaged.cloudronapp@4.0.0" {print $1}'); do cloudron start --app "$a" && cloudron update --app "$a" --appstore-id org.wordpress.unmanaged.cloudronapp@3.17.0 --force; done -
Security issue thread - PHP and eMudhra cert compromiseI have:
WordPress (Developer) 7.0
Package version
org.wordpress.unmanaged.cloudronapp@4.0.0The (only) one updated shows now:
WordPress (Developer) 7.1.3
Package version
org.wordpress.unmanaged.cloudronapp@3.17.0My question is: if there is an available update, why if I hit "check for updates” nothing happens?
Thanks a lot
-
Security issue thread - PHP and eMudhra cert compromiseHi @girish on a single Wordpress Developer instance I was asked to update to org.wordpress.unmanaged.cloudronapp@3.17.0 and I updated.
But all other Wordpress Developer instances, even if I hit "check updates”, nothing happens...
-
Critical PHP RCEs (CVE-2026-109618 / CVE-2026-109619) – impact on Cloudron apps? -
Security issue thread - PHP and eMudhra cert compromise@jdaviescoates Another “workaround” could be to install VPN app and mark as required to access to all installed application. What do you think? Could be a temporary workaround to avoid to stop every app?
-
Security issue thread - PHP and eMudhra cert compromise@nebulon Thanks Nebulon
and thanks for all your efforts -
Security issue thread - PHP and eMudhra cert compromise@girish Thanks a lot, I did manually. But I cannot figure out why not was automatically updated...
-
Security issue thread - PHP and eMudhra cert compromise@girish on different Cloudron instances I ran
# dpkg-query -W -f 'installed: ${Version}\n' ca-certificatesI had older version, I updated.
Why wasn't it updated, even though Cloudron should have updated it?
-
FreshRSS returns 502 "app not responding"I think something depends on 10.1.5 update... let’s wait for help
-
FreshRSS returns 502 "app not responding"Do you manage login with Cloudron or with app itself?
Just to debug, please do this test:
go to
config.php in app root folder, then change auth_type to form:'auth_type' => 'form',then reboot
-
AppsMonitor - monitoring for your Cloudron@robi Totally agree...
-
Using AI to write docs@LoudLemur Thanks for this interesting question. It could be ok to draft docs by hand, then refine and polish with AI...
AI is too much verbose, as @girish noted....
-
What's coming in Cloudron 10In the network UI, there is a setting called "VPN protection". First enable the feature and select how to route the client traffic.
This is a great feature. I hope it can be documented more thoroughly, to better understand how to benefit from it in all use cases and scenarios.
-
Upgrade from 9.2.0 to 10.0.2 interrupted by apt-daily-upgrade, leaving pending database migrations -
Upgrade from 9.2.0 to 10.0.2 interrupted by apt-daily-upgrade, leaving pending database migrations -
Upgrade from 9.2.0 to 10.0.2 interrupted by apt-daily-upgrade, leaving pending database migrationsHi all
I encountered an issue while upgrading Cloudron from 9.2.0 to 10.0.2 on Ubuntu 24.04.
I investigated with ChatGPT, and below you can find report that I asked to write.
I hope this can help to fix the installation script.
Thanks
After the upgrade, the dashboard was unreachable. Running:
sudo cloudron-support --troubleshootreported:
Database migrations are pending. Last migration in DB: 20260330000000-backupSites-remove-disk-provider.js Last migration file: 20260820150000-users-add-loginLocationsJson.jsThe Box service was running, but
box.logcontained:Unknown column 'apps.requiresVpn' in 'field list'The missing column should have been created by:
20260624120000-apps-add-requiresVpn.jsDisk space and inodes were fine, and MySQL, Docker and nginx were running normally.
Looking at the update task and previous boot journal, I found this sequence:
installer: stop box service for update installer: switching the box code installer: calling box setup script start: Configuring nginx Warning! D-Bus connection terminated. Failed to wait for response: Connection reset by peerAt approximately the same time,
apt-daily-upgrade.serviceandunattended-upgradestarted. This caused a systemd re-execution, after which:cloudron-updater.service: Main process exited, status=1/FAILUREIt appears that the new 10.0.2 code was installed, but the setup script stopped before applying the database migrations. This left the Cloudron code and database schema out of sync.
Recovery
I temporarily stopped and runtime-masked the automatic APT services to prevent another concurrent run:
sudo systemctl stop apt-daily.timer apt-daily-upgrade.timer sudo systemctl stop apt-daily.service apt-daily-upgrade.service packagekit.service sudo systemctl mask --runtime \ apt-daily.service \ apt-daily-upgrade.service \ packagekit.serviceAfter confirming that no active APT or DPKG operation was running, I stopped Box and ran the troubleshooting command again:
sudo systemctl stop box sudo cloudron-support --troubleshootBecause Box was down, the support tool automatically reran the Cloudron startup/migration script. All pending migrations were then processed successfully, including:
Processed migration 20260624120000-apps-add-requiresVpn ... Processed migration 20260820150000-users-add-loginLocationsJson DoneIt also restarted Box automatically.
A subsequent check showed:
[OK] dashboard is reachable via loopback [OK] No pending database migrations [OK] box v10.0.2 is running [OK] Dashboard is reachable via IPv4 PASS: 29 WARN: 0 FAIL: 0The dashboard also returned HTTP 200.
Finally, I restored the APT services:
sudo systemctl unmask --runtime \ apt-daily.service \ apt-daily-upgrade.service \ packagekit.service sudo systemctl start apt-daily.timer apt-daily-upgrade.timerEverything is now working correctly.
Could this have been caused by a race between the Cloudron setup script and
apt-daily-upgrade? Would it make sense for the updater to temporarily inhibit automatic APT jobs or automatically resume the migration phase if the detached updater service is interrupted?