Cannot reach my Nextcloud after successful Setup. SSL problem?

Hello!

Sorry for opening another topic…After fixing the self inflicted DynDNS-issue I now run into another wall: The setup is complete and I can see the “Open your Nextcloud” Button on the install page. :tada:
Unfortunately clicking that just forwards to a login page for my router (fritz.box).

  • The router forwards ports 80, 443 and 3478 one-to-one to my Nextcloud.
  • when I try to reach the Nextcloud via it´s local IP (https://192.168.178.41) Firefox says: (translated to english, original error is in german)
Error: Secure connection failed

There was an error connecting to 192.168.178.41. The remote station reports that it has encountered an internal error.

Error code: SSL_ERROR_INTERNAL_ERROR_ALERT

I tried the help page linked on the setup-page (https://github.com/nextcloud/all-in-one/discussions/2105) but the output of sudo docker logs nextcloud-aio-apache does not (as far as I understand it) provide any details on the issue. Here is the output:

sudo docker logs nextcloud-aio-apache

Waiting for Nextcloud to start...
[This prints multiple times]


Connection to nextcloud-aio-nextcloud (172.19.0.8) 9000 port [tcp/*] succeeded!
{"level":"info","ts":1717488138.065634,"msg":"using provided configuration","config_file":"/tmp/Caddyfile","config_adapter":""}
[Tue Jun 04 08:02:18.069158 2024] [mpm_event:notice] [pid 119:tid 140139801713416] AH00489: Apache/2.4.59 (Unix) configured -- resuming normal operations
[Tue Jun 04 08:02:18.069487 2024] [core:notice] [pid 119:tid 140139801713416] AH00094: Command line: '/usr/local/apache2/bin/httpd -D FOREGROUND'
{"level":"info","ts":1717488138.0697207,"msg":"failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See https://github.com/quic-go/quic-go/wiki/UDP-Buffer-Sizes for details."}
{"level":"error","ts":1717488268.9768176,"logger":"http.handlers.reverse_proxy","msg":"aborting with incomplete response","upstream":"localhost:8000","duration":0.00544729,"request":{"remote_ip":"65.154.226.166","remote_port":"4416","client_ip":"65.154.226.166","proto":"HTTP/2.0","method":"GET","host":"neindochohh.de","uri":"/dist/core-common.js?v=282f3ef3-0","headers":{"Sec-Fetch-Dest":["script"],"Pragma":["no-cache"],"Cache-Control":["no-cache"],"X-Forwarded-For":["65.154.226.166"],"X-Forwarded-Proto":["https"],"X-Forwarded-Host":["neindochohh.de"],"User-Agent":["Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/117.0.5938.132 Safari/537.36"],"Accept":["*/*"],"Sec-Fetch-Site":["same-origin"],"Cookie":[],"Sec-Fetch-Mode":["no-cors"],"Accept-Encoding":["gzip, deflate, br"]},"tls":{"resumed":false,"version":772,"cipher_suite":4865,"proto":"h2","server_name":"MYDOMAIN.de"}},"error":"writing: write tcp 172.19.0.10:443->65.154.226.166:4416: write: connection reset by peer"}

Waiting for Nextcloud to start...
[This prints again multiple times]

Connection to nextcloud-aio-nextcloud (172.19.0.9) 9000 port [tcp/*] succeeded!
{"level":"info","ts":1717490440.91104,"msg":"using provided configuration","config_file":"/tmp/Caddyfile","config_adapter":""}
{"level":"info","ts":1717490440.9178452,"msg":"failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See https://github.com/quic-go/quic-go/wiki/UDP-Buffer-Sizes for details."}
[Tue Jun 04 08:40:40.944276 2024] [mpm_event:notice] [pid 55:tid 139984017668872] AH00489: Apache/2.4.59 (Unix) configured -- resuming normal operations
[Tue Jun 04 08:40:40.944488 2024] [core:notice] [pid 55:tid 139984017668872] AH00094: Command line: '/usr/local/apache2/bin/httpd -D FOREGROUND'

Thanks again in advance! :slight_smile:

Hm… I am actually able to open your domain. Can you try if accessing the domain from outside your home network works?

Yes, I can! That´s both weird and great! :tada: :smiley: Thanks for the information! Maybe it´ll work itself out, I´m using a VPN to configure for now :slight_smile:

Small update in case someone runs into the same problem: It didn´t have anything to do with the nextcloud itself, it was a IPv6 issue. I changed the DynDNS Update-URL on my router so that it didn´t include <ip6addr> anymore and now everything works perfectly!

1 Like