Cloudron Forum

@cresdamo109 said in Outbound Spam Filtering: I need to filter outbound emails for spam/malware before they're sent to protect our domain reputation and meet compliance requirements. Can you elaborate further on this? On Cloudron, emails are only sent by users or the apps. AFAIK, none of the apps generate spam. Are your users intentionally sending out spam?

Ahh, fantastic! A business app Thank you so much!

@marcusquinn token burn is real, and default config doesn't care. Hence openrouter's auto route helps As does this config optimization OC efficient config - https://x.com/alexxzay/status/2017824548276600914

I am using a registry app and a builder app. As far as I can see, the tarball is uploaded successfully to the builder. It seems to be an issue with the registry. I am not sure. Could you please provide some commands to check, where the problem's cause is? BTW: I am using Gitea (as a Git-Clone). It there a way, to directly use Gitea for building? I am building locally and am pulling the repository from Gitea to push it to the builer. Is this the recommended workflow?

@marcusquinn Sorry, forgot to delete my post when I came across https://forum.cloudron.io/post/119487

No no, I‘ve the actual version running! It‘s just that it stopped working on 29th of November and when I looked into the events i noticed that on this day 1.21 was installed!

Guess it has something to do with app/pkg/start.sh # oidc if [[ -n "${CLOUDRON_OIDC_ISSUER:-}" ]]; then echo " ==> Configuring OIDC auth" yq eval -i ".oidc_providers[0].idp_id=\"cloudron\"" /app/data/configs/homeserver.yaml yq eval -i ".oidc_providers[0].idp_name=\"${CLOUDRON_OIDC_PROVIDER_NAME:-Cloudron}\"" /app/data/configs/homeserver.yaml yq eval -i ".oidc_providers[0].issuer=\"${CLOUDRON_OIDC_ISSUER}\"" /app/data/configs/homeserver.yaml yq eval -i ".oidc_providers[0].client_id=\"${CLOUDRON_OIDC_CLIENT_ID}\"" /app/data/configs/homeserver.yaml yq eval -i ".oidc_providers[0].client_secret=\"${CLOUDRON_OIDC_CLIENT_SECRET}\"" /app/data/configs/homeserver.yaml yq eval -i ".oidc_providers[0].scopes=[\"openid\", \"email\", \"profile\"]" /app/data/configs/homeserver.yaml yq eval -i ".oidc_providers[0].authorization_endpoint=\"${CLOUDRON_OIDC_AUTH_ENDPOINT}\"" /app/data/configs/homeserver.yaml yq eval -i ".oidc_providers[0].token_endpoint=\"${CLOUDRON_OIDC_TOKEN_ENDPOINT}\"" /app/data/configs/homeserver.yaml yq eval -i ".oidc_providers[0].userinfo_endpoint=\"${CLOUDRON_OIDC_PROFILE_ENDPOINT}\"" /app/data/configs/homeserver.yaml # https://s3lph.me/ldap-to-oidc-migration-3-matrix.html yq eval -i ".oidc_providers[0].allow_existing_users=true" /app/data/configs/homeserver.yaml yq eval -i ".oidc_providers[0].skip_verification=true" /app/data/configs/homeserver.yaml yq eval -i ".oidc_providers[0].user_mapping_provider.config.localpart_template=\"{{ user.sub }}\"" /app/data/configs/homeserver.yaml yq eval -i ".oidc_providers[0].user_mapping_provider.config.display_name_template=\"{{ user.name }}\"" /app/data/configs/homeserver.yaml yq eval -i ".oidc_providers[0].user_mapping_provider.config.email_template=\"{{ user.email }}\"" /app/data/configs/homeserver.yaml else Basically, the script should not update the homeserver.yaml localpart_template key, if its value was set (manually) to null (changing it to null is maybe easier to detect than just commenting it out).

@timconsidine No worries and it's not that big of deal, really. I just wanted to mention it to help with troubleshooting and for others not to be discouraged from trying CCAI(P). I believe the staff wouldn't have considered this feature in 9.1 if it weren't for the success of CCAI. Kudos!

That is strange indeed. so curl -6 https://ipv6.api.cloudron.io/api/v1/helper/public_ip does not work on this server? If so then clearly the server is not correctly set up for ipv6, we should check then what is missing.

v0.1.6 : ensured MCP servers work, resolved searx dependency now pushed to git.cloudron.io/cloudron-agent0 and docker hub image tcmbp132021/cloudron-agent0:latest (aka v0.1.6)

@jdaviescoates very good point. Missing of button requires many additional steps. Thanx @nebulon to bringing back

The bug has been officially addressed now. https://code.castopod.org/adaures/castopod/-/commit/44fb904

I sshed into the server, and the file really does not exist: cloudron# ls /home/yellowtent/appsdata/f6e82f5e-ae79-403b-b824-f96d8989b4f4/fsmetadata.json ls: cannot access '/home/yellowtent/appsdata/f6e82f5e-ae79-403b-b824-f96d8989b4f4/fsmetadata.json': No such file or directory The content of the directory: cloudron# cd /home/yellowtent/appsdata/f6e82f5e-ae79-403b-b824-f96d8989b4f4/ cloudron# ls -la total 2552 drwxr-xr-x 5 yellowtent yellowtent 4096 Jan 30 23:06 . drwxr-xr-x 4 yellowtent yellowtent 4096 Jan 28 19:35 .. drwxr-xr-x 3 yellowtent yellowtent 4096 Jan 28 20:07 2026-01-24-060000-602 -rw-r--r-- 1 yellowtent yellowtent 6343 Jan 31 23:06 config.json drwxr-xr-x 6 www-data www-data 4096 Jan 30 15:02 data -rw-r--r-- 1 yellowtent yellowtent 2582680 Jan 31 23:06 mysqldump drwxr-xr-x 3 yellowtent yellowtent 4096 Jan 28 20:15 snapshot

@girish said in Separate out Backup listings and Backup Sites?: Open to other ideas. Just thinking out loud, but I wonder if you just have no backup submenu and instead just have a single Backups page that has: Sites Listings App Archives

@nebulon that looks a bit better. But I still wonder why not a nice big labelled button?