Good catch. nc is not part of the base image it seems (not explicitly). I have replaced that code with bash logic.

thank you for all your explanations

@nebulon could you please also approve me? I'd like to cast a vote for GlitchTip

@paradoxbound if I enable Dane, should I enable MTA-STS?

I've tripled checked (created new key and secret) and it works...

@james said in Cloudron App Install Update Error Bug: Hello @dualoswinwiz Please use registry.docker.com as the docker hub server address. This should resolve the issue. i was using like this registry.hub.docker.com --- changing this to registry.docker.com solved the problem

Can you run cloudron-support --unbound-forward-dns 1.1.1.1 ? This will forward all DNS requests to cloudflare public DNS.

Fixed in https://git.cloudron.io/platform/box/-/commit/b537d73a5585662605176346ffb31db4ebbb6a02

The AWS module changed between v8 and v9 and maybe some discrepancy between the versions is causing this. I will close this because testing and accommodating minio issues is a dead end unfortunately given that the project has gone into maintenance mode. We are looking into Gargage as an alternative.

Maybe you can open a new thread with the log? The previous issue is probably not relevant since it was many versions ago. Did you also restore Cloudron to a new server and hit this issue?

Hello @potemkin_ai You could also check the Cloudron event log to see if and when the password was changed. Have you checked that?

@james said in Private docker registry in Cloudron: Hello @dualoswinwiz I have just created a personal access token with the Read-only permission. Configured Cloudron: [image: 1766752382547-8248133a-0064-4fa0-a724-828faf826879-image.png] and was able to install my custom app from a private repo. Did you use registry.hub.docker.com as the Server address? Nope i was using docker.io once i changed to registry.hub.docker.com its working thank you.

Great, good to hear and looking forward to the fix. Anyway it’s not very urgent. Thanks and happy Xmas

Hello @thibault In Cloudron 9 external links have been moved Appearance. [image: 1766566436835-f81d64b3-c318-43f3-ba10-abfe1f9a37d0-image.png] We already had multiple report of users not being able to find it so we will move it back to its old position or to another place where it makes sense.

Hello @arta Yes it does. If you place the file /root/yellowtent/boxdata/custom_pages/notfound.html you can customize it. I have copied the original and edited the text: [image: 1766355580244-a2bb1bf8-7374-4be0-a13e-811a40335ed4-image-resized.png]

https://forum.cloudron.io/topic/14767/error-accessing-dashboard-after-update-from-8.x-to-9.x-read-this

Hello @fanvyr @fanvyr said in Error accessing Dashboard after update from 8.x to 9.x? Read this: Originally didn't want to publish it Please continue reporting if you find something that is off. Each report helps us improve and has great value.

Thanks for reporting. Fixed in https://git.cloudron.io/platform/box/-/commit/5107cd28c4a0b8b362e9ee5da7151a9271db9fa3 . It won't collapse anymore and you can select it. The link to http://www.barracudanetworks.com/reputation/?pr=1&ip= ... itself is broken, gets forwarded to https://www.barracuda.com/ which results in a 404. Working link is https://www.barracudacentral.org/lookups but I didn't manage to add the IP as parameter This is actually the raw TXT record that is in their DNS. It would not be safe to render it as a link, since it is random external data. But also their DNS simply has raw links like above which are i guess broken. For example: # host -t TXT 70.188.231.171.b.barracudacentral.org 127.0.0.150 Using domain server: Name: 127.0.0.150 Address: 127.0.0.150#53 Aliases: 70.188.231.171.b.barracudacentral.org descriptive text "http://www.barracudanetworks.com/reputation/?pr=1&ip=171.231.188.70"