mighty-services
commented
1 year ago that's the log from the master container:
Trying to fix docker.sock permissions internally...
Creating docker group internally with id 118
WARNING: the devicemapper storage-driver is deprecated, and will be removed in a future release.
WARNING: devicemapper: usage of loopback devices is strongly discouraged for production use.
Use `--storage-opt dm.thinpooldev` to specify a custom block storage device.
[0;92mInitial startup of Nextcloud All In One complete!
You should be able to open the Nextcloud AIO Interface now on port 8080 of this server!
E.g. https://internal.ip.of.this.server:8080
If your server has port 80 and 8443 open and you point a domain to your server, you can get a valid certificate automatically by opening the Nextcloud AIO Interface via:
https://your-domain-that-points-to-this-server.tld:8443[0m
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.20.0.2. Set the 'ServerName' directive globally to suppress this message
[Tue Dec 20 20:15:01.379836 2022] [ssl:warn] [pid 121] AH01906: 172.20.0.2:8080:0 server certificate is a CA certificate (BasicConstraints: CA == TRUE !?)
[Tue Dec 20 20:15:01.379889 2022] [ssl:warn] [pid 121] AH01909: 172.20.0.2:8080:0 server certificate does NOT include an ID which matches the server name
{"level":"info","ts":1671567301.3816109,"msg":"using provided configuration","config_file":"/Caddyfile","config_adapter":""}
{"level":"warn","ts":1671567301.3838482,"msg":"Caddyfile input is not formatted; run the 'caddy fmt' command to fix inconsistencies","adapter":"caddyfile","file":"/Caddyfile","line":2}
{"level":"info","ts":1671567301.3850005,"logger":"admin","msg":"admin endpoint started","address":"localhost:2019","enforce_origin":false,"origins":["//localhost:2019","//[::1]:2019","//127.0.0.1:2019"]}
{"level":"warn","ts":1671567301.3852391,"logger":"http","msg":"server is listening only on the HTTP port, so no automatic HTTPS will be applied to this server","server_name":"srv0","http_port":80}
{"level":"warn","ts":1671567301.3852522,"logger":"http","msg":"automatic HTTP->HTTPS redirects are disabled","server_name":"srv1"}
{"level":"info","ts":1671567301.3856926,"logger":"tls.cache.maintenance","msg":"started background certificate maintenance","cache":"0xc0001f28c0"}
{"level":"warn","ts":1671567301.3857899,"logger":"tls","msg":"YOUR SERVER MAY BE VULNERABLE TO ABUSE: on-demand TLS is enabled, but no protections are in place","docs":"https://caddyserver.com/docs/automatic-https#on-demand-tls"}
{"level":"info","ts":1671567301.3864424,"logger":"tls","msg":"cleaning storage unit","description":"FileStorage:/mnt/docker-aio-config/caddy/"}
{"level":"info","ts":1671567301.386468,"logger":"tls","msg":"finished cleaning storage units"}
{"level":"info","ts":1671567301.3864498,"logger":"http.log","msg":"server running","name":"srv0","protocols":["h1","h2","h3"]}
{"level":"info","ts":1671567301.3865538,"logger":"http","msg":"enabling HTTP/3 listener","addr":":8443"}
{"level":"info","ts":1671567301.386824,"msg":"failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See https://github.com/lucas-clemente/quic-go/wiki/UDP-Receive-Buffer-Size for details."}
{"level":"info","ts":1671567301.3869948,"logger":"http.log","msg":"server running","name":"srv1","protocols":["h1","h2","h3"]}
{"level":"error","ts":1671567301.3870358,"msg":"unable to create folder for config autosave","dir":"/root/.config/caddy","error":"mkdir /root/.config: permission denied"}
{"level":"info","ts":1671567301.387044,"msg":"serving initial configuration"}
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.20.0.2. Set the 'ServerName' directive globally to suppress this message
[Tue Dec 20 20:15:01.403537 2022] [ssl:warn] [pid 121] AH01906: 172.20.0.2:8080:0 server certificate is a CA certificate (BasicConstraints: CA == TRUE !?)
[Tue Dec 20 20:15:01.403554 2022] [ssl:warn] [pid 121] AH01909: 172.20.0.2:8080:0 server certificate does NOT include an ID which matches the server name
[Tue Dec 20 20:15:01.405591 2022] [mpm_prefork:notice] [pid 121] AH00163: Apache/2.4.54 (Debian) PHP/8.0.26 OpenSSL/1.1.1n configured -- resuming normal operations
[Tue Dec 20 20:15:01.405729 2022] [core:notice] [pid 121] AH00094: Command line: 'apache2 -D FOREGROUND'
szaimen
Thanks for all your work, guys! I'm really enjoying this project :)
I just switched from latest to beta, so that I have the latest and greatest Nextcloud Hub3 version on my server :)
After the upgrade, I realized that Nextcloud Office is not working anymore. It did when I set up this instance a few months ago with Nextcloud 24. In the Setup-Screen, it says the there is no connection possible. I've put in the URL of my instance, so https://cloud.example.com
I don't know If I need to add something behind that. I couldn't find any information regarding to this in the internet.
The things I tried so far (with no success):
docker system pruneand rebuilding it all withdocker-compose updocker system prune, removing volumes of apache, collabora, clamav, elasticsearch and rebuilding it all withdocker-compose upWhen I switch to the collabora demo server it says "OK" in the settings, but when I try to open a document it's telling me that It can open the connection.
What I did before the error:
Nextcloud AIO is on the latest version (mastercontainer has version 4.0) and it's running in an up-to-date Ubuntu 22.04 vm with this config: