I had already checked unbound and restarted it.
unbound.service - Unbound DNS Resolver
Loaded: loaded (/etc/systemd/system/unbound.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2024-04-03 17:08:55 UTC; 23h ago
Main PID: 730 (unbound)
Tasks: 1 (limit: 96378)
Memory: 11.6M
CPU: 7.803s
CGroup: /system.slice/unbound.service
└─730 /usr/sbin/unbound -d
I just restarted the service, no difference.
Hello community,
I've been experiencing problems with the internet in the containers for a short time. I noticed it because the Nextcloud instances couldn't connect to the Appstore. The containers are all externally accessible.
A curl google.de on the host system delivers a correct result.
A curl google.de inside a container delivers the following error:
curl: (7) Failed to connect to google.de port 80 after 3131 ms: No route to host
Nslookup returns correct values on the host system and in a container.
I'm currently in the dark. I am only using IPv4 at the moment.
Has anyone of you ever had such a problem?
Best regards,
Thomas
Hello everyone,
I have a freshly installed Ubuntu Server (22.04.3) and am trying to install Cloudron.
It looks like the installation depends on the step:
Installing Cloudron version 7.6.0 (this takes some time)
The log currently looks like this:
error pulling image configuration: download failed after attempts=1: error parsing HTTP 408 response body: invalid character '<' looking for beginning of value: "<html><body><h1>408 Request Time-out</h1> \nYour browser didn't send a complete request in time.\n</body></html>\n"
2023-10-12T15:45:41 ==> installer: Could not pull registry.docker.com/cloudron/g raphite:3.4.2@sha256:bc30121baecfa887856de56278fca5a532543c8ff439b60dc178132d578 c5e9f
registry.docker.com/cloudron/graphite@sha256:bc30121baecfa887856de56278fca5a5325 43c8ff439b60dc178132d578c5e9f: Pulling from cloudron/graphite
445a6a12be2b: Already exists
4cfe0cdc770e: Already exists
e6a0eb1fa9b7: Already exists
e995e5b957f9: Already exists
e6d226089461: Already exists
b3243df2776e: Already exists
debd247c1af3: Already exists
ea1f575bfbef: Already exists
566e1eaf48e1: Already exists
68da526a8544: Already exists
2f3677647d18: Already exists
90984d402264: Already exists
802deede2955: Already exists
1861003a8fe7: Already exists
524cf22ec2b3: Already exists
9871ea879f63: Pulling fs layer
710d51248471: Pulling fs layer
9871ea879f63: Waiting
13c19ce58371: Pulling fs layer
710d51248471: Waiting
b582552c3695: Pulling fs layer
b582552c3695: Waiting
13c19ce58371: Waiting
Do you have an idea?
VG Fisi
@girish Now it would only be helpful if the mount target can be freely selected in the container.
Hallo Miteinander,
aktuell können Volumes in den Apps nur nach "/media/{volume name}" gemountet werden.
Für manche Apps wäre es doch sinnvoll das Ziel selbst zu bestimmen. So wäre es beispielsweise bei der Nextcloud App möglich den Storage für die Daten einfacher auszulagern. Zudem wäre es dann sinnvoll, Mounts schon beim installieren der App mit angeben zu können.
Es stellt sich dann nur die Frage, wie Backups der Volumes gelöst werden können, denn aktuell werden Volumes nicht gesichert.
Wie seht Ihr das?
VG Fisi
Gibt es hier schon etwas neues?
Hallo Cloudron Team,
Joomla war schon öfters als APP gewünscht. Ist Joomla mittlerweile in Planung? Wie ist der Stand dazu?
VG
Fisii