Cloudron Forum

On a brand new DO Ubuntu server, the first pull fails.

root@my:~# TOKEN=$(curl "https://auth.docker.io/token?service=registry.docker.io&scope=repository:ratelimitpreview/test:pull" | jq -r .token) curl --head -H "Authorization: Bearer $TOKEN" https://registry-1.docker.io/v2/ratelimitpreview/test/manifests/latest % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 5429 0 5429 0 0 17471 0 --:--:-- --:--:-- --:--:-- 17512 HTTP/1.1 200 OK content-length: 527 content-type: application/vnd.docker.distribution.manifest.v2+json docker-content-digest: sha256:c2d41d2ba6d8b7b4a3ffec621578eb4d9a0909df29dfa2f6fd8a2e5fd0836aed docker-distribution-api-version: registry/2.0 etag: "sha256:c2d41d2ba6d8b7b4a3ffec621578eb4d9a0909df29dfa2f6fd8a2e5fd0836aed" date: Sat, 14 Dec 2024 15:41:35 GMT strict-transport-security: max-age=31536000 ratelimit-limit: 100;w=21600 ratelimit-remaining: 0;w=21600 docker-ratelimit-source: 2604:a880:2:d1::

@Bedrijfstak14 in v8, the IPv6 defaults to auto-detected. Probably best to choose this explicitly based on your setup.

@nebulon said in All Offline adter update or db can't restart.:

by avoiding disabling

by avoiding disabling

at least I think that's what you mean? 🙂

After a reboot, it seems fine for now. Let’s see if it persists

@awestenb it means that IPv6 record is not set up. try host -t AAAA my.domain.name . This should be the ipv6 address of you server. If your server does not have IPv6, then in the cloudron setup page -> advanced -> disable ipv6.

Yes, /24 would only allow 250 or so addresses, we do need a /16 . I am not sure why 172.17 and 172.18 networks are conflicting though . In the original error message it says "172.18.0.1" is in use. If your local network is 172.18, it all makes sense. Currently, there is no workaround for this since the code has some places where it hardcodes 172.18 network.

@cocam123 as @timconsidine said, Cloudron is not designed to run alongside 3rd party software. The best approach here is to run your public stuff in a separate VM. Then, as @matix131997 said use the app proxy feature. This will set up nginx to proxy all the requests for the domain to this separate VM . App Proxy was designed specifically for the use case of running software outside of the VM and re-using the IP.

Note that depending on the app, you might have to query a different port i.e the port it is listening on.

# curl -L http://12aded8a-8c78-4b6c-bdbe-2d549b1c2eb5:3000 | wc -c % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 11 0 11 0 0 1412 0 --:--:-- --:--:-- --:--:-- 1571 100 11 0 11 0 0 417 0 --:--:-- --:--:-- --:--:-- 417 100 143k 100 143k 0 0 1464k 0 --:--:-- --:--:-- --:--:-- 1464k 147314

Directus listens on port 8055 and n8n on port 5678

@girish wait ... true 🙂
6a136902-e13f-47d9-b8be-68193a8688b4-image.png

@skeats this is fixed already but pending a Cloudron release. We got a bit behind schedule this time.