I can't access nextcloud AIO interface

Hi! Today when I tried to access my nextcloud aio interface it was not working. I checked portainer since there I have installed the nextcloud AIO and the nextcloud-aio-apache container is unhealthy. I’ve restart it multiple times including restarting all of the containers without any result. I would really appreciate anyone’s help!

Nextcloud-aio-apache logs

Connection to nextcloud-aio-nextcloud (172.18.0.10) 9000 port [tcp/*] succeeded!

[Thu May 16 22:12:25.844652 2024] [mpm_event:notice] [pid 34:tid 273521743801600] AH00489: Apache/2.4.59 (Unix) configured – resuming normal operations

[Thu May 16 22:12:25.845326 2024] [core:notice] [pid 34:tid 273521743801600] AH00094: Command line: ‘/usr/local/apache2/bin/httpd -D FOREGROUND’

INF ts=1715886745.852693 msg=using provided configuration config_file=/tmp/Caddyfile config_adapter=

INF ts=1715886745.859741 msg=failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See UDP Buffer Sizes · quic-go/quic-go Wiki · GitHub for details.

Connection to nextcloud-aio-nextcloud (172.18.0.10) 9000 port [tcp/*] succeeded!

[Thu May 16 22:22:35.522556 2024] [mpm_event:notice] [pid 34:tid 258365660146944] AH00489: Apache/2.4.59 (Unix) configured – resuming normal operations

[Thu May 16 22:22:35.523265 2024] [core:notice] [pid 34:tid 258365660146944] AH00094: Command line: ‘/usr/local/apache2/bin/httpd -D FOREGROUND’

INF ts=1715887355.531091 msg=using provided configuration config_file=/tmp/Caddyfile config_adapter=

INF ts=1715887355.5355399 msg=failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See UDP Buffer Sizes · quic-go/quic-go Wiki · GitHub for details.

Connection to nextcloud-aio-nextcloud (172.18.0.10) 9000 port [tcp/*] succeeded!

[Thu May 16 22:25:11.464350 2024] [mpm_event:notice] [pid 34:tid 247070167600384] AH00489: Apache/2.4.59 (Unix) configured – resuming normal operations

[Thu May 16 22:25:11.464993 2024] [core:notice] [pid 34:tid 247070167600384] AH00094: Command line: ‘/usr/local/apache2/bin/httpd -D FOREGROUND’

INF ts=1715887511.4735715 msg=using provided configuration config_file=/tmp/Caddyfile config_adapter=

INF ts=1715887511.4778652 msg=failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See UDP Buffer Sizes · quic-go/quic-go Wiki · GitHub for details.

Waiting for Nextcloud to start…

Waiting for Nextcloud to start…

Waiting for Nextcloud to start…

Waiting for Nextcloud to start…

Waiting for Nextcloud to start…

Waiting for Nextcloud to start…

Waiting for Nextcloud to start…

Waiting for Nextcloud to start…

Waiting for Nextcloud to start…

Waiting for Nextcloud to start…

Connection to nextcloud-aio-nextcloud (172.18.0.10) 9000 port [tcp/*] succeeded!

INF ts=1715887828.8989518 msg=using provided configuration config_file=/tmp/Caddyfile config_adapter=

INF ts=1715887828.9074314 msg=failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See UDP Buffer Sizes · quic-go/quic-go Wiki · GitHub for details.

[Thu May 16 22:30:28.972442 2024] [mpm_event:notice] [pid 62:tid 254101906509056] AH00489: Apache/2.4.59 (Unix) configured – resuming normal operations

[Thu May 16 22:30:28.973024 2024] [core:notice] [pid 62:tid 254101906509056] AH00094: Command line: ‘/usr/local/apache2/bin/httpd -D FOREGROUND’

Connection to nextcloud-aio-nextcloud (172.18.0.10) 9000 port [tcp/*] succeeded!

[Thu May 16 22:53:19.262064 2024] [mpm_event:notice] [pid 34:tid 269155090734336] AH00489: Apache/2.4.59 (Unix) configured – resuming normal operations

[Thu May 16 22:53:19.262722 2024] [core:notice] [pid 34:tid 269155090734336] AH00094: Command line: ‘/usr/local/apache2/bin/httpd -D FOREGROUND’

INF ts=1715889199.270226 msg=using provided configuration config_file=/tmp/Caddyfile config_adapter=

INF ts=1715889199.2751338 msg=failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See UDP Buffer Sizes · quic-go/quic-go Wiki · GitHub for details.

Connection to nextcloud-aio-nextcloud (172.18.0.10) 9000 port [tcp/*] succeeded!

[Thu May 16 22:57:12.074638 2024] [mpm_event:notice] [pid 34:tid 249171834424576] AH00489: Apache/2.4.59 (Unix) configured – resuming normal operations

[Thu May 16 22:57:12.075097 2024] [core:notice] [pid 34:tid 249171834424576] AH00094: Command line: ‘/usr/local/apache2/bin/httpd -D FOREGROUND’

INF ts=1715889432.0844798 msg=using provided configuration config_file=/tmp/Caddyfile config_adapter=

INF ts=1715889432.0894024 msg=failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See UDP Buffer Sizes · quic-go/quic-go Wiki · GitHub for details.

Connection to nextcloud-aio-nextcloud (172.18.0.10) 9000 port [tcp/*] succeeded!

[Fri May 17 00:36:38.290180 2024] [mpm_event:notice] [pid 35:tid 255628661558528] AH00489: Apache/2.4.59 (Unix) configured – resuming normal operations

[Fri May 17 00:36:38.290735 2024] [core:notice] [pid 35:tid 255628661558528] AH00094: Command line: ‘/usr/local/apache2/bin/httpd -D FOREGROUND’

INF ts=1715895398.293372 msg=using provided configuration config_file=/tmp/Caddyfile config_adapter=

INF ts=1715895398.3025408 msg=failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See UDP Buffer Sizes · quic-go/quic-go Wiki · GitHub for details.

Connection to nextcloud-aio-nextcloud (172.18.0.10) 9000 port [tcp/*] succeeded!

INF ts=1715895685.5536036 msg=using provided configuration config_file=/tmp/Caddyfile config_adapter=

[Fri May 17 00:41:25.555041 2024] [mpm_event:notice] [pid 34:tid 278843556535552] AH00489: Apache/2.4.59 (Unix) configured – resuming normal operations

[Fri May 17 00:41:25.555556 2024] [core:notice] [pid 34:tid 278843556535552] AH00094: Command line: ‘/usr/local/apache2/bin/httpd -D FOREGROUND’

INF ts=1715895685.5590258 msg=failed to sufficiently increase send buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See UDP Buffer Sizes · quic-go/quic-go Wiki · GitHub for details.

nc: getaddrinfo for host “nextcloud-aio-nextcloud” port 9000: Try again

Waiting for Nextcloud to start…

nc: getaddrinfo for host “nextcloud-aio-nextcloud” port 9000: Try again

Waiting for Nextcloud to start…

nc: getaddrinfo for host “nextcloud-aio-nextcloud” port 9000: Try again

Waiting for Nextcloud to start…

nc: getaddrinfo for host “nextcloud-aio-nextcloud” port 9000: Try again

Waiting for Nextcloud to start…

nc: getaddrinfo for host “nextcloud-aio-nextcloud” port 9000: Try again

Waiting for Nextcloud to start…

nc: getaddrinfo for host “nextcloud-aio-nextcloud” port 9000: Try again

Waiting for Nextcloud to start…

nc: getaddrinfo for host “nextcloud-aio-nextcloud” port 9000: Try again

Waiting for Nextcloud to start…

nc: getaddrinfo for host “nextcloud-aio-nextcloud” port 9000: Try again

Waiting for Nextcloud to start…

nc: getaddrinfo for host “nextcloud-aio-nextcloud” port 9000: Try again

Waiting for Nextcloud to start…

nc: getaddrinfo for host “nextcloud-aio-nextcloud” port 9000: Try again

Waiting for Nextcloud to start…

nc: getaddrinfo for host “nextcloud-aio-nextcloud” port 9000: Try again

Waiting for Nextcloud to start…

nc: getaddrinfo for host “nextcloud-aio-nextcloud” port 9000: Try again

Waiting for Nextcloud to start…

nc: getaddrinfo for host “nextcloud-aio-nextcloud” port 9000: Try again

Waiting for Nextcloud to start…

nc: getaddrinfo for host “nextcloud-aio-nextcloud” port 9000: Try again

Waiting for Nextcloud to start…

nc: getaddrinfo for host “nextcloud-aio-nextcloud” port 9000: Try again

Waiting for Nextcloud to start…

nc: getaddrinfo for host “nextcloud-aio-nextcloud” port 9000: Try again

Waiting for Nextcloud to start…

nc: getaddrinfo for host “nextcloud-aio-nextcloud” port 9000: Try again

Waiting for Nextcloud to start…

nc: getaddrinfo for host “nextcloud-aio-nextcloud” port 9000: Try again

Waiting for Nextcloud to start…

Waiting for Nextcloud to start…

Waiting for Nextcloud to start…

Waiting for Nextcloud to start…

Waiting for Nextcloud to start…

Waiting for Nextcloud to start…

Waiting for Nextcloud to start…

Waiting for Nextcloud to start…

Waiting for Nextcloud to start…

Waiting for Nextcloud to start…

Connection to nextcloud-aio-nextcloud (172.18.0.4) 9000 port [tcp/*] succeeded!

INF ts=1715979904.339591 msg=using provided configuration config_file=/tmp/Caddyfile config_adapter=

[Sat May 18 00:05:04.341899 2024] [mpm_event:notice] [pid 61:tid 258290593910016] AH00489: Apache/2.4.59 (Unix) configured – resuming normal operations

[Sat May 18 00:05:04.342265 2024] [core:notice] [pid 61:tid 258290593910016] AH00094: Command line: ‘/usr/local/apache2/bin/httpd -D FOREGROUND’

INF ts=1715979904.3459458 msg=failed to sufficiently increase send buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See UDP Buffer Sizes · quic-go/quic-go Wiki · GitHub for details.

Hi, can you post the output of sudo docker inspect nextcloud-aio-mastercontainer here?

Sure, here it is!

[
{
“Id”: “c87a314f8825116e57d45efd402e8d7857bc9a8f240cb6975bca79972600afdf”,
“Created”: “2024-05-06T14:43:47.136238789Z”,
“Path”: “/start.sh”,
“Args”: ,
“State”: {
“Status”: “restarting”,
“Running”: true,
“Paused”: false,
“Restarting”: true,
“OOMKilled”: false,
“Dead”: false,
“Pid”: 0,
“ExitCode”: 1,
“Error”: “”,
“StartedAt”: “2024-05-17T23:08:41.682026276Z”,
“FinishedAt”: “2024-05-17T23:08:49.880579919Z”,
“Health”: {
“Status”: “unhealthy”,
“FailingStreak”: 0,
“Log”: [
{
“Start”: “2024-05-14T21:07:20.73863516Z”,
“End”: “2024-05-14T21:07:20.793127186Z”,
“ExitCode”: 0,
“Output”: “Connection to localhost (::1) 80 port [tcp/http] succeeded!\nConnection to localhost (::1) 8000 port [tcp/] succeeded!\nConnection to localhost (::1) 8080 port [tcp/http-alt] succeeded!\nConnection to localhost (::1) 8443 port [tcp/] succeeded!\nConnection to localhost (::1) 9000 port [tcp/] succeeded!\nConnection to localhost (127.0.0.1) 9876 port [tcp/] succeeded!\n”
},
{
“Start”: “2024-05-14T21:07:50.794626915Z”,
“End”: “2024-05-14T21:07:50.845084148Z”,
“ExitCode”: 0,
“Output”: “Connection to localhost (::1) 80 port [tcp/http] succeeded!\nConnection to localhost (::1) 8000 port [tcp/] succeeded!\nConnection to localhost (::1) 8080 port [tcp/http-alt] succeeded!\nConnection to localhost (::1) 8443 port [tcp/] succeeded!\nConnection to localhost (::1) 9000 port [tcp/] succeeded!\nConnection to localhost (127.0.0.1) 9876 port [tcp/] succeeded!\n”
},
{
“Start”: “2024-05-14T21:08:20.846462939Z”,
“End”: “2024-05-14T21:08:20.905639478Z”,
“ExitCode”: 0,
“Output”: “Connection to localhost (::1) 80 port [tcp/http] succeeded!\nConnection to localhost (::1) 8000 port [tcp/] succeeded!\nConnection to localhost (::1) 8080 port [tcp/http-alt] succeeded!\nConnection to localhost (::1) 8443 port [tcp/] succeeded!\nConnection to localhost (::1) 9000 port [tcp/] succeeded!\nConnection to localhost (127.0.0.1) 9876 port [tcp/] succeeded!\n”
},
{
“Start”: “2024-05-14T21:08:50.906886569Z”,
“End”: “2024-05-14T21:08:50.967257146Z”,
“ExitCode”: 0,
“Output”: “Connection to localhost (::1) 80 port [tcp/http] succeeded!\nConnection to localhost (::1) 8000 port [tcp/] succeeded!\nConnection to localhost (::1) 8080 port [tcp/http-alt] succeeded!\nConnection to localhost (::1) 8443 port [tcp/] succeeded!\nConnection to localhost (::1) 9000 port [tcp/] succeeded!\nConnection to localhost (127.0.0.1) 9876 port [tcp/] succeeded!\n”
},
{
“Start”: “2024-05-14T21:09:20.968178978Z”,
“End”: “2024-05-14T21:09:21.022893724Z”,
“ExitCode”: 0,
“Output”: “Connection to localhost (::1) 80 port [tcp/http] succeeded!\nConnection to localhost (::1) 8000 port [tcp/] succeeded!\nConnection to localhost (::1) 8080 port [tcp/http-alt] succeeded!\nConnection to localhost (::1) 8443 port [tcp/] succeeded!\nConnection to localhost (::1) 9000 port [tcp/] succeeded!\nConnection to localhost (127.0.0.1) 9876 port [tcp/] succeeded!\n”
}
]
}
},
“Image”: “sha256:9e36ce8757c382b70680b9e075501b5666363072a70935119a56669dce2751b6”,
“ResolvConfPath”: “/var/lib/docker/containers/c87a314f8825116e57d45efd402e8d7857bc9a8f240cb6975bca79972600afdf/resolv.conf”,
“HostnamePath”: “/var/lib/docker/containers/c87a314f8825116e57d45efd402e8d7857bc9a8f240cb6975bca79972600afdf/hostname”,
“HostsPath”: “/var/lib/docker/containers/c87a314f8825116e57d45efd402e8d7857bc9a8f240cb6975bca79972600afdf/hosts”,
“LogPath”: “/var/lib/docker/containers/c87a314f8825116e57d45efd402e8d7857bc9a8f240cb6975bca79972600afdf/c87a314f8825116e57d45efd402e8d7857bc9a8f240cb6975bca79972600afdf-json.log”,
“Name”: “/nextcloud-aio-mastercontainer”,
“RestartCount”: 110,
“Driver”: “overlay2”,
“Platform”: “linux”,
“MountLabel”: “”,
“ProcessLabel”: “”,
“AppArmorProfile”: “docker-default”,
“ExecIDs”: null,
“HostConfig”: {
“Binds”: [
“nextcloud_aio_mastercontainer:/mnt/docker-aio-config”,
“/var/run/docker.sock:/var/run/docker.sock:ro”
],
“ContainerIDFile”: “”,
“LogConfig”: {
“Type”: “json-file”,
“Config”: {}
},
“NetworkMode”: “bridge”,
“PortBindings”: {
“80/tcp”: [
{
“HostIp”: “”,
“HostPort”: “80”
}
],
“8080/tcp”: [
{
“HostIp”: “”,
“HostPort”: “8080”
}
],
“8443/tcp”: [
{
“HostIp”: “”,
“HostPort”: “8443”
}
]
},
“RestartPolicy”: {
“Name”: “always”,
“MaximumRetryCount”: 0
},
“AutoRemove”: false,
“VolumeDriver”: “”,
“VolumesFrom”: null,
“ConsoleSize”: [
0,
0
],
“CapAdd”: null,
“CapDrop”: null,
“CgroupnsMode”: “private”,
“Dns”: ,
“DnsOptions”: ,
“DnsSearch”: ,
“ExtraHosts”: null,
“GroupAdd”: null,
“IpcMode”: “private”,
“Cgroup”: “”,
“Links”: null,
“OomScoreAdj”: 0,
“PidMode”: “”,
“Privileged”: false,
“PublishAllPorts”: false,
“ReadonlyRootfs”: false,
“SecurityOpt”: null,
“UTSMode”: “”,
“UsernsMode”: “”,
“ShmSize”: 67108864,
“Runtime”: “runc”,
“Isolation”: “”,
“CpuShares”: 0,
“Memory”: 0,
“NanoCpus”: 0,
“CgroupParent”: “”,
“BlkioWeight”: 0,
“BlkioWeightDevice”: ,
“BlkioDeviceReadBps”: ,
“BlkioDeviceWriteBps”: ,
“BlkioDeviceReadIOps”: ,
“BlkioDeviceWriteIOps”: ,
“CpuPeriod”: 0,
“CpuQuota”: 0,
“CpuRealtimePeriod”: 0,
“CpuRealtimeRuntime”: 0,
“CpusetCpus”: “”,
“CpusetMems”: “”,
“Devices”: ,
“DeviceCgroupRules”: null,
“DeviceRequests”: null,
“MemoryReservation”: 0,
“MemorySwap”: 0,
“MemorySwappiness”: null,
“OomKillDisable”: null,
“PidsLimit”: null,
“Ulimits”: ,
“CpuCount”: 0,
“CpuPercent”: 0,
“IOMaximumIOps”: 0,
“IOMaximumBandwidth”: 0,
“MaskedPaths”: [
“/proc/asound”,
“/proc/acpi”,
“/proc/kcore”,
“/proc/keys”,
“/proc/latency_stats”,
“/proc/timer_list”,
“/proc/timer_stats”,
“/proc/sched_debug”,
“/proc/scsi”,
“/sys/firmware”,
“/sys/devices/virtual/powercap”
],
“ReadonlyPaths”: [
“/proc/bus”,
“/proc/fs”,
“/proc/irq”,
“/proc/sys”,
“/proc/sysrq-trigger”
]
},
“GraphDriver”: {
“Data”: {
“LowerDir”: “/var/lib/docker/overlay2/7939f32c619b7ae87986500601fb204b9d0e322ced7d45d0758f69fd72facb46-init/diff:/var/lib/docker/overlay2/d48d9323f21ace8e2dfe31bbf509a355f65be4e2690ed7f1bc627a77e2c363f9/diff:/var/lib/docker/overlay2/48359300b6629cde44f552d4138388e5a5f247a496177bac185c91fbf9e2c693/diff:/var/lib/docker/overlay2/f1305cc5b08d23b3a55b0f86ecb6e4a362ebbab855cc3c9beff6209a64087bb8/diff:/var/lib/docker/overlay2/c9c32ba3d4276dac2e2831b4f293bab60986873c20e6ed688df02c6effc0851b/diff:/var/lib/docker/overlay2/defbd150525dd791f60cddb337edaba916e9d5cbfdd4207ceed6e14822c74de8/diff:/var/lib/docker/overlay2/1188c40a4010c75e05d05d854ee9838252a73ef09041ff8fde3abbcdbc5cb0e4/diff:/var/lib/docker/overlay2/500a8b8ba717cc62ce0554e365c7c204898fd65cf5486ee974bca8a76dab6bd4/diff:/var/lib/docker/overlay2/8e4a7a91633e7490671bfa4a1d9dc536feee906ba89fcf2a811fe2195a9fba5c/diff:/var/lib/docker/overlay2/4c59e7197eeb57aaae57c4f5e54c9c9e5f4810915f06ef1a8083b3e50d311acd/diff:/var/lib/docker/overlay2/b2364a41093ab3f526aa92aee4664cc28e5b83df37d9281f0ff8623fec7dd153/diff:/var/lib/docker/overlay2/056fcdf8983a854057a1a05fe41e911809940b09a3ed1ffc67c6dad46d8e6893/diff:/var/lib/docker/overlay2/65fc489034960f5611aa7a4a2c54ac7e7a9284a492f403e99a05935e492b5e37/diff:/var/lib/docker/overlay2/7440d24cb200639f168000eff1e7560cb6ccaa22dcd8303beed00e65a35ee605/diff:/var/lib/docker/overlay2/1502a0bc8945988579ccd86335c0230f96fca67b2456dec31388fab7bbbd7721/diff:/var/lib/docker/overlay2/bf4cb7ec13924806db66245c9fd4a97f5b5d4f50554682cc529de52027209f36/diff:/var/lib/docker/overlay2/f6dc22e6c2641d684765aa319e082dde3051ce1190e9b136592e20cfca6ba687/diff:/var/lib/docker/overlay2/e15e2e70dcf77a24536f827b44ebd61033ec94606a308b8e3ffb4625c5b516c6/diff:/var/lib/docker/overlay2/3fc37aef142666a4e03f247122962b8da2b2b2a5a3c998519016c476e90408b9/diff”, “MergedDir”: “/var/lib/docker/overlay2/7939f32c619b7ae87986500601fb204b9d0e322ced7d45d0758f69fd72facb46/merged”,
“UpperDir”: “/var/lib/docker/overlay2/7939f32c619b7ae87986500601fb204b9d0e322ced7d45d0758f69fd72facb46/diff”,
“WorkDir”: “/var/lib/docker/overlay2/7939f32c619b7ae87986500601fb204b9d0e322ced7d45d0758f69fd72facb46/work”
},
“Name”: “overlay2”
},
“Mounts”: [
{
“Type”: “volume”,
“Name”: “nextcloud_aio_mastercontainer”,
“Source”: “/var/lib/docker/volumes/nextcloud_aio_mastercontainer/_data”,
“Destination”: “/mnt/docker-aio-config”,
“Driver”: “local”,
“Mode”: “z”,
“RW”: true,
“Propagation”: “”
},
{
“Type”: “bind”,
“Source”: “/var/run/docker.sock”,
“Destination”: “/var/run/docker.sock”,
“Mode”: “ro”,
“RW”: false,
“Propagation”: “rprivate”
}
],
“Config”: {
“Hostname”: “6711f7c82b21”,
“Domainname”: “”,
“User”: “root”,
“AttachStdin”: false,
“AttachStdout”: true,
“AttachStderr”: true,
“ExposedPorts”: {
“80/tcp”: {},
“8080/tcp”: {},
“8443/tcp”: {},
“9000/tcp”: {}
},
“Tty”: false,
“OpenStdin”: false,
“StdinOnce”: false,
“Env”: [
“NEXTCLOUD_MEMORY_LIMIT=5000M”,
“PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin”,
“PHPIZE_DEPS=autoconf \t\tdpkg-dev dpkg \t\tfile \t\tg++ \t\tgcc \t\tlibc-dev \t\tmake \t\tpkgconf \t\tre2c”,
“PHP_INI_DIR=/usr/local/etc/php”,
“PHP_CFLAGS=-fstack-protector-strong -fpic -fpie -O2 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64”,
“PHP_CPPFLAGS=-fstack-protector-strong -fpic -fpie -O2 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64”,
“PHP_LDFLAGS=-Wl,-O1 -pie”,
“GPG_KEYS=1198C0117593497A5EC5C199286AF1F9897469DC C28D937575603EB4ABB725861C0779DC5C0A9DE4 AFD8691FDAEDF03BDF6E460563F15A9B715376CA”,
“PHP_VERSION=8.3.6”,
“PHP_URL=https://www.php.net/distributions/php-8.3.6.tar.xz”,
“PHP_ASC_URL=https://www.php.net/distributions/php-8.3.6.tar.xz.asc”,
“PHP_SHA256=53c8386b2123af97626d3438b3e4058e0c5914cb74b048a6676c57ac647f5eae”
],
“Cmd”: null,
“Healthcheck”: {
“Test”: [
“CMD-SHELL”,
“/healthcheck.sh”
]
},
“Image”: “nextcloud/all-in-one:latest”,
“Volumes”: null,
“WorkingDir”: “/var/www/docker-aio”,
“Entrypoint”: [
“/start.sh”
],
“OnBuild”: null,
“Labels”: {},
“StopSignal”: “SIGQUIT”
},
“NetworkSettings”: {
“Bridge”: “”,
“SandboxID”: “b7035b09d417c121cf08514e845202d1199a163d835f8427230d5e4d6d84961e”,
“SandboxKey”: “/var/run/docker/netns/b7035b09d417”,
“Ports”: {},
“HairpinMode”: false,
“LinkLocalIPv6Address”: “”,
“LinkLocalIPv6PrefixLen”: 0,
“SecondaryIPAddresses”: null,
“SecondaryIPv6Addresses”: null,
“EndpointID”: “”,
“Gateway”: “”,
“GlobalIPv6Address”: “”,
“GlobalIPv6PrefixLen”: 0,
“IPAddress”: “”,
“IPPrefixLen”: 0,
“IPv6Gateway”: “”,
“MacAddress”: “”,
“Networks”: {
“nextcloud-aio”: {
“IPAMConfig”: null,
“Links”: null,
“Aliases”: [
“6711f7c82b21”
],
“MacAddress”: “”,
“NetworkID”: “b7f367ae6a3f39d3e1b2bc98e8536f7e3dfc0d2b5f129b47c18a7e5ccd61d89c”,
“EndpointID”: “”,
“Gateway”: “”,
“IPAddress”: “”,
“IPPrefixLen”: 0,
“IPv6Gateway”: “”,
“GlobalIPv6Address”: “”,
“GlobalIPv6PrefixLen”: 0,
“DriverOpts”: null,
“DNSNames”: [
“nextcloud-aio-mastercontainer”,
“6711f7c82b21”,
“c87a314f8825”
]
}
}
}
}
]

All right and the output of sudo docker logs nextcloud-aio-mastercontainer ?

Here is the output of the other command, it just says the same message over and over:

scussions/2065
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs
Apart from that, there has been this: How to fix sudden dns resolution issues after the AIO update to v4.4.1 or higher. · nextcloud/all-in-one · Discussion #2065 · GitHub
Could not resolve the host nextcloud.com.
Most likely the DNS resolving does not work.
You should be able to fix this by following Configuring DNS | dockerlabs

I’ve deleted some of this log, because the nc community forum haves a character limit but as I said, is the same messaje for 100 times :slight_smile:

Can you please respond to me :)) or anyone I would really appreciate it!

I think it is pretty obvious what you need to do?