Cloudron Forum

Lanhild

@james said:

@robi said:

It would be nice if they could be hosted by the local registry app.

The docker images? That should already work and is close to my above suggestion with a private registry. You'd just need to configure the docker registry in the Cloudron dashboard under /#/docker.

I believe what @robi meant is to be able to store the CloudronVersions.json in a registry, much like what authentik does with blueprints.

Lanhild

@robi That'd be a great solution

Lanhild

The convenience and the standardization benefits of using CloudronVersions.json and its features shouldn't be restricted to publicly accessible URLs.

Whether be it manually pasting a CloudronVersions.json's content in my dashboard, I'd like to be able to install my private custom applications this way.

Lanhild

@mazarian Agreed, this feels unusual as "shutting down" isn't as destructive as an uninstallation.

Lanhild

@nebulon I did the upgrade from Ubuntu 22 to 24 today. I confirm that it fixed the issue for me as well.

Lanhild

Updating the Cloudron CLI did the trick.

I was using npm install -g cloudron, believing that'd update to the latest version. Turns you should use npm install -g cloudron@latest to get the most recent version.

Lanhild

On Cloudron 9.1.5, along with Cloudron's CLI version 6.0.0, attempting to install an application systematically results in a 404. This makes it impossible to install an application.

❯ cloudron install --image ghcr.io/lanhild/sh.atuin.cloudronapp:1.0.1                      
Location: atuin
Failed to install app: 404 message: No such route

The error occurs on the demo server as well, ruling out a configuration error.

This might be a regression that appeared since the new cloudron versions feature.

Lanhild

@klawitterb said:
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

I'm also encountering these.

Lanhild

I can't repro the issue on the demo server.

Lanhild

@joseph My answers, step-by-step as you formatted it in your message:

Yes.
Reachable, Docker-Distribution-Api-Version: registry/2.0

<html>
<head><title>302 Found</title></head>
<body>
<center><h1>302 Found</h1></center>
<hr><center>nginx</center>
</body>
</html>

docker login from the Cloudron server results in the following

Error response from daemon: Get "https:/registry.cloudron.local/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

docker login from any other remote works perfectly fine.

Lanhild

@joseph

Error response from daemon: Get "https://registry.cloudron.local/v2/": context deadline exceeded

Lanhild

@joseph it doesn't, gives me a timeout error. I'll add relevant logs in a few minutes.

Lanhild

@joseph said:

@lanhild I just tried to reproduce this and it seems to work fine. Have you added the local registry app as a Private docker registry i.e under System -> Docker -> Registries?

That's what I'm attempting to do, but it results in the error I mentioned.

Lanhild

@joseph I used .local for the sake of my example

Lanhild

@girish pinging for visibility.

Lanhild

@ekevu123 I meant, you won't see the previously uninstalled app backups in the newly installed app, but yes backups won't get deleted

Lanhild

@ekevu123 uninstalling won't preserve the backups

Lanhild

@ekevu123 I never faced this situation. Maybe try putting it in recovery mode?

Lanhild

I'm guessing 9.1.3 rendered the application unusable, as the issue appeared later than the latest update of this app.

Pushing/pulling an image from a remote works correctly. However, attempting to pull an image from the same server doesn't work at all.

For instance:

I have a registry @ registry.cloudron.local
I have an app @ app.cloudron.local, using an image from the registry, on the same cloudron.

Whenever I attempt to update this application with a new image, the pull never works.

Mar 19 18:51:04 box:docker Attempt 1 failed. Will retry: Unable to pull image registry.cloudron.local/app.image:2.0.13. registry error: {"reason":"server error","statusCode":500,"json":null}

In the registry configuration in Cloudron settings, the error Invalid serverAddress: socket hang up appears whenever I attempt to save the private registry settings.

In the registry application logs, there is the following line, appearing intermittently:

Mar 19 20:32:18 time="2026-03-20T00:32:18.895638941Z" 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=redacted service=registry version=3.0.0

I have multiple Cloudrons, all with a registry application installed and facing the same issue.

As mentioned in the beginning of my topic, pulling from a remote works.

Connecting the private registry registry.cloudron.local in my.other-cloudron.local works perfectly. It seems like there might be a DNS issue.

Feel free to ask for more information.

Lanhild

@girish IMO, the version information wouldn't matter for a notification email. I'd just like to know when a manual updates required

Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.

Cloudron Forum

Lanhild

Posts