Cloudron Forum

So decided to upgrade my server to Ubuntu 24 and its working now again.

Indeed seems like hairpin doesn't work, from troubleshoot:
[FAIL] Could not load dashboard domain.
Hairpin NAT is not working. Please check if your router supports it

I just tried the good old have you tried turning it off and on again, interestingly troubleshoot now errors with:
[FAIL] Could not load dashboard website with loopback check

From the server:
ping -n docker.apehost.de -> works
telnet idontexist.apehost.de -> Name or service not known
telnet docker.apehost.de -> connection refused
docker pull docker.apehost.de/path-to-exisiting-image -> Error response from daemon: Get "https://docker.apehost.de/v2/": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

From my local machine:
docker pull docker.apehost.de/path-to-exisiting-image -> works just fine

Just tried, that just gives me a telnet: Unable to connect to remote host: Connection refused

Without https:// I'm getting: Invalid serverAddress: socket hang up

Log spam seems to be gone now, still having trouble with the actual connection to the registry on my cloudron:

Docker registry resides on the same cloudron

@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

@james i've noticed that my baserow instance now runs into out of memory after update to 1.33.3 (or .4, not sure). Either it now needs loads of more memory or there's something wrong, had increased memory limit from 5gb to 6.5 gb and it still wasn't enough.

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

Hey Cloudron Team,

I'm building a custom app which is using a OIDC client from cloudron. I've noticed that the picture url in the OIDC profile is returning a 404 with this message

{
  "status": "Not Found",
  "message": "no avatar"
}

I've got a profile picture set in my account, so I would expect it to be returned. I think this worked before but I haven't looked it this for a while so not sure if this is a regression from v9.

Any ideas? Thanks!

Sounds interesting, but I’m I’m vacation at that time.
My band had its rehearsal room in Herzbergstr. Brings back some old memories.

30 days sounds good to me.

I've noticed that the profile avatar picture from /api/v1/profile/avatar/... does not return a cache-control header. Could we add one so the browser will cache it?

I guess duration could be discussed, not sure if the url would change if picture changes. If so I guess we could choose a long cache duration.

I haven’t spend a lot of time in tandoor, but I really find the ui unappealing.

Also an interesting side fact: you can connect self hosted LLMs as long as they support the open ai api. It’s also mentioned in the docs.

Just stumbled upon this and thought this might be interesting for others as well: Mealie has an integration with Open AI which enables importing recipes from images. Worked really well in my tests.

To enable this you'll need an API key and at least Tier 1 which you'll get after depositing 5$, see also https://docs.mealie.io/documentation/getting-started/installation/open-ai/.

For cloudron simply open the env file in the file manager and add OPENAI_API_KEY=<your_key>.

A shared cloudron base image gives you at least all the dependencies needed for accessing the addons like databases, also the shared layer should result in less storage consumption when running many apps on one server.

Im running a nuxt.js/vue.js app I’m building for myself on cloudron. Feel free to reach out to me, I’m guessing it shouldn’t be too different from react/next.

I’m using multi stage dockerfiles for my projects, works like a charm. Only for final stage I use the cloudron base image.

@girish just wanted to check this but my /.well-known/openid-configuration endpoint doesn't list the picture claim?
Am I missing something? I'm on v7.7.2.

"claims_supported": [
    "sub",
    "email",
    "email_verified",
    "family_name",
    "given_name",
    "locale",
    "name",
    "preferred_username",
    "sid",
    "auth_time",
    "iss
]

Tbh not really but I am check with my own app if I’m getting anything