Cloudron Forum

Hello @firmansi Thanks for the report. Then I have to assume that it is some Nextcloud third party app issue with the latest update.

yeah there is now... ok now its stopped. I cancelled the update (with backup) and ticked skip backup, the update went fine. Thanks!

@timconsidine you can toggle visibillity for apps that have their own user management. If you use an SSO app, there is "user management" which manages access (and therefore an visible dashboard icon) but "dashboard visibility" is missing from the menu. Its well explained in the documentation. I guess what you could do is remove access for an user (within Cloudron), put the user inside a group X that has no access to said app and set up SSO manually within the app to grant access to users within group X. Basically, I want the "dashboard visibility" options to be available for all apps. To not make Cloudrons UI confusing, a "Hide for non admins/operators" checkbox would be fine.

@james please check my DM

Oh sorry. The doc is even not up2date. In latest version (9.1.5) the response is (unconfigured): {"allowlist":[],"blocklist":[]}

Hello @imc67 Might be a caching issue on your side, but https://docs.cloudron.io/packages/ip2location is working fine.

The app supports a caldav endpoints so if you have a system which can sync this into some other provider it should already work. Currently the Calendar app itself does not have any way to actively reach out into other services. I guess the question here is which part in your setup is the single source of truth regarding the events. That one would be the server and the rest become clients. Wondering what the use-case is to have two such event stores itself. (Same answer really to the contacts topic)

@joseph I've now also noticed problems with the docker registry. In my case I'm also running a builderbot on the same cloudron instance. Seems like it can't connect to the docker registry, my logs on the builderbot are simply saying: Mar 28 08:42:05 build-1774683724218 Build stream finished Mar 28 08:42:05 build-1774683724218 Pushing... Mar 28 08:42:20 build-1774683724218 Push stream finished Mar 28 08:42:20 build-1774683724218 Get "https://docker.apehost.de/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) Mar 28 08:42:20 build-1774683724218 Push failed Probably not related I've also noticed that the logs on the docker registry container get spammed with this error: Mar 28 08:46:32 time="2026-03-28T07:46:32.467979729Z" level=error msg="traces export: Post \"https://localhost:4318/v1/traces\": dial tcp [::1]:4318: connect: connection refused" go.version=go1.23.7 instance.id=401bc88b-1bfe-4713-ae09-1cffdf628884 service=registry version=3.0.0 Mar 28 08:46:35 2026/03/28 07:46:35 [info] 71#71: *109 client 172.18.0.1 closed keepalive connection

@girish , is this perhaps something we can consider adding in one of the next updates? This would be greatly beneficial to be able to specify the IP address for outbound traffic in Cloudron (at least for the mail container but maybe all containers in one setting might be better for some people, not too sure what the best approach is). I found a couple of other related topics so it seems like there is a need for this. I think my solution should still work but likely just needs to be adapted by Cloudron to be more built-in with a GUI to set the outbound traffic IP (or maybe just have it default to the IP set in the Network page by default as I suspect the DNS record IP would be the same IP outbound traffic would be desired). Other related topics I found: https://forum.cloudron.io/post/108717 (Haraka config for controlling outbound SMTP interface) https://forum.cloudron.io/post/81114 (SMTP using wrong IP address on interface with multiple addresses) (admittedly this one is a post I made myself before, lol)

Hello @orezbodajoy Can you please inspect the /home/yellowtent/platformdata/logs/box.log logfile for errors?

@james, I got it back up. Working on getting everything updated.