@jdaviescoates yes, exactly what I meant
Lanhild
Posts
-
Implement a Down for Maintenance screen -
Implement a Down for Maintenance screen@james I'd say both. Either way, the best way to explain this need's the following:
Having the ability to set, from a list, which page to display when an app is down/off/in maintenance.
-
Authentik - Making authentication simple.- For applications with networking related features, not uncommon
- Depends on the use case, as soon as you need LDAP or other protocols, an outposts necessary. Other features like SAML and OIDC will work without additional configuration.
You can see authentik's documentation about this, it's well detailed.
-
Authentik - Making authentication simple.@crazybrad outposts are their own docker containers, created by the authentik worker, itself connected to the docker socket. I reckon we have an addon to connect an app to the socket, but iirc it's not recommended to use it.
-
Authentik - Making authentication simple.@crazybrad Core features such as outposts wouldn't work by packaging authentik as a Cloudron application.
As mentioned earlier in this topic, authentik is the kind of application I'd suggest having installed on a separate server.
-
Implement a Down for Maintenance screen@girish Any thoughts about this?
It's especially useful when you'd like to point users to a status page for which the URL differs with the app.
-
MySQL and Postgresql as standalone apps@chmod777 Archived because I don't maintain it anymore. The core of the app itself works (check through the branches first).
-
What's coming in 9.1@girish Should be opt-in. In cases where a Cloudron server has multiple developers, I don't want my developers to upload code to be built on my server
-
Publish the CloudronManifest schema@girish automatic schema validation by the IDE
-
Publish the CloudronManifest schema@joseph I know about this file. Maybe what I meant wasn't as clear as I thought

What I'd like is to have the readily available JSON schema, online.
For an example, see:
-
Publish the CloudronManifest schemaIt'd be useful for development purposes to have the
CloudronManifestJSON schema published online. -
Backups exiting with code 70@girish Increasing the task memory did it. Issue solved.
-
Backups exiting with code 70@girish Bumped the memory from the default (?) 1GB to 4GB. Right now, it seems like an app backup worked correctly. My Cloudron has quite a lot of stuff, so an global backup takes longer. I'll report back.
-
Backups exiting with code 70@girish There are no memory usage spikes coinciding with the timestamp of the error. Also, I have the same issue on another Cloudron.
Where should I bump the memory of backup task?Trying it out. -
Backups exiting with code 70I am using the
s3-v4-compat (rsync)backup target, with OVH S3's product. All my system backups exit with acode 70. It seems like backups roll on for a bit, and then exit with said code.The same happens with app backups, making their updates impossible unless skipping the backup for them.
This issue happened since the upgrade from 8.3.2 to 9.0.10
Logs
Nov 18 23:02:06 box:taskworker Terminated Nov 18 23:02:06 Exiting with code 70
We can see here with the "Upload finished" lines that the backup seemingly works for a while, but then exits.
Troubleshooting Already Performed
None, I can't control the backup process.
System Details
Cloudron version
9.0.10Ubuntu version
Ubuntu 22.04.4 LTS Linux 5.15.0-161-genericVendor
DigitalOceanCPU
8 Core "DO-Premium-AMD"Memory
33.65 GB RAM & 1.03 GB Swap -
Uptime Kuma 2.0.0 package -
False positive for Google Chrome dangerous website flagAs suspected, comes from upstream
See https://github.com/louislam/uptime-kuma/issues/6223#issuecomment-3433199988
Shouldn't be a Cloudron issue.
-
False positive for Google Chrome dangerous website flagDescription
See the issue @ https://github.com/louislam/uptime-kuma/issues/6223
Basically, it's affecting a bunch of my apps on Cloudron as I have multiple of them on the same subdomain as my Uptime Kuma instance.
I don't anything other than Cloudron applications on this subdomain, and none of them have been compromised.
Steps to reproduce
I updated Uptime Kuma to the version 2.0.1, and a few minutes after my subdomain got flagged.
Logs
N/A
Troubleshooting Already Performed
Went and requested a review from Google on their search console. Unfortunately, it's said it can take multiple days or weeks.
I open this topic in the case an issue on Cloudron's side is known.
System Details
Generate Diagnostics Data
v8.3.2 (Ubuntu 22.04.4 LTS)
VendorDigitalOcean
ProductDroplet
CPU8 Core "DO-Premium-AMD"
Memory33.65 GB RAM & 1.03 GB Swap
Uptime17 days -
Uptime Kuma 2.0.0 package@luckow I don't believe we have a MariaDB addon.
-
Uptime Kuma 2.0.0 packageI've opened an issue upstream, as starting the update triggered a false positive alert from Google Chrome on my subdomain: