Unable to connect to Nextcloud UI after starting containers

ℹ️ Support 📦 Appliances (Docker, Snappy, VM, NCP, AIO)
,
1

Hi,

I’ve followed the instructions for installing NextCloud AIO (v7.13.1) to the best of my knowledge. I started the containers successfully but I can’t open Nextcloud. The nextcloud-aio-apache error logs:

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.8) 9000 port [tcp/*] succeeded!
[Tue Mar 19 16:56:49.640975 2024] [mpm_event:notice] [pid 102:tid 139647049030408] AH00489: Apache/2.4.58 (Unix) configured -- resuming normal operations
[Tue Mar 19 16:56:49.641538 2024] [core:notice] [pid 102:tid 139647049030408] AH00094: Command line: '/usr/local/apache2/bin/httpd -D FOREGROUND'
{"level":"info","ts":1710863809.6517751,"msg":"using provided configuration","config_file":"/tmp/Caddyfile","config_adapter":""}
{"level":"info","ts":1710863809.6564188,"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":1710863814.5629046,"logger":"tls.issuance.acme.acme_client","msg":"challenge failed","identifier":"d489-98-97-79-136.ngrok-free.app","challenge_type":"tls-alpn-01","problem":{"type":"urn:ietf:params:acme:error:tls","title":"","detail":"3.17.7.232: remote error: tls: no application protocol","instance":"","subproblems":[]}}
{"level":"error","ts":1710863814.5629902,"logger":"tls.issuance.acme.acme_client","msg":"validating authorization","identifier":"d489-98-97-79-136.ngrok-free.app","problem":{"type":"urn:ietf:params:acme:error:tls","title":"","detail":"3.17.7.232: remote error: tls: no application protocol","instance":"","subproblems":[]},"order":"https://acme-v02.api.letsencrypt.org/acme/order/1625195977/253653449707","attempt":1,"max_attempts":3}
{"level":"error","ts":1710863814.5630584,"logger":"tls.obtain","msg":"could not get certificate from issuer","identifier":"d489-98-97-79-136.ngrok-free.app","issuer":"acme-v02.api.letsencrypt.org-directory","error":"HTTP 400 urn:ietf:params:acme:error:tls - 3.17.7.232: remote error: tls: no application protocol"}
{"level":"error","ts":1710863814.5630937,"logger":"tls.obtain","msg":"will retry","error":"[d489-98-97-79-136.ngrok-free.app] Obtain: [d489-98-97-79-136.ngrok-free.app] solving challenge: d489-98-97-79-136.ngrok-free.app: [d489-98-97-79-136.ngrok-free.app] authorization failed: HTTP 400 urn:ietf:params:acme:error:tls - 3.17.7.232: remote error: tls: no application protocol (ca=https://acme-v02.api.letsencrypt.org/directory)","attempt":1,"retrying_in":60,"elapsed":4.3264797,"max_duration":2592000}
{"level":"error","ts":1710863879.4597056,"logger":"tls.issuance.acme.acme_client","msg":"challenge failed","identifier":"d489-98-97-79-136.ngrok-free.app","challenge_type":"tls-alpn-01","problem":{"type":"urn:ietf:params:acme:error:tls","title":"","detail":"3.134.39.220: remote error: tls: no application protocol","instance":"","subproblems":[]}}
{"level":"error","ts":1710863879.4599245,"logger":"tls.issuance.acme.acme_client","msg":"validating authorization","identifier":"d489-98-97-79-136.ngrok-free.app","problem":{"type":"urn:ietf:params:acme:error:tls","title":"","detail":"3.134.39.220: remote error: tls: no application protocol","instance":"","subproblems":[]},"order":"https://acme-staging-v02.api.letsencrypt.org/acme/order/140728084/15381419824","attempt":1,"max_attempts":3}
{"level":"error","ts":1710863879.4600122,"logger":"tls.obtain","msg":"could not get certificate from issuer","identifier":"d489-98-97-79-136.ngrok-free.app","issuer":"acme-v02.api.letsencrypt.org-directory","error":"HTTP 400 urn:ietf:params:acme:error:tls - 3.134.39.220: remote error: tls: no application protocol"}
{"level":"error","ts":1710863879.4601684,"logger":"tls.obtain","msg":"will retry","error":"[d489-98-97-79-136.ngrok-free.app] Obtain: [d489-98-97-79-136.ngrok-free.app] solving challenge: d489-98-97-79-136.ngrok-free.app: [d489-98-97-79-136.ngrok-free.app] authorization failed: HTTP 400 urn:ietf:params:acme:error:tls - 3.134.39.220: remote error: tls: no application protocol (ca=https://acme-staging-v02.api.letsencrypt.org/directory)","attempt":2,"retrying_in":120,"elapsed":69.2236085,"max_duration":2592000}
{"level":"error","ts":1710864002.003478,"logger":"tls.issuance.acme.acme_client","msg":"challenge failed","identifier":"d489-98-97-79-136.ngrok-free.app","challenge_type":"tls-alpn-01","problem":{"type":"urn:ietf:params:acme:error:tls","title":"","detail":"3.134.125.175: remote error: tls: no application protocol","instance":"","subproblems":[]}}
{"level":"error","ts":1710864002.0039248,"logger":"tls.issuance.acme.acme_client","msg":"validating authorization","identifier":"d489-98-97-79-136.ngrok-free.app","problem":{"type":"urn:ietf:params:acme:error:tls","title":"","detail":"3.134.125.175: remote error: tls: no application protocol","instance":"","subproblems":[]},"order":"https://acme-staging-v02.api.letsencrypt.org/acme/order/140728084/15381455064","attempt":1,"max_attempts":3}
{"level":"error","ts":1710864002.004042,"logger":"tls.obtain","msg":"could not get certificate from issuer","identifier":"d489-98-97-79-136.ngrok-free.app","issuer":"acme-v02.api.letsencrypt.org-directory","error":"HTTP 400 urn:ietf:params:acme:error:tls - 3.134.125.175: remote error: tls: no application protocol"}
{"level":"error","ts":1710864002.004328,"logger":"tls.obtain","msg":"will retry","error":"[d489-98-97-79-136.ngrok-free.app] Obtain: [d489-98-97-79-136.ngrok-free.app] solving challenge: d489-98-97-79-136.ngrok-free.app: [d489-98-97-79-136.ngrok-free.app] authorization failed: HTTP 400 urn:ietf:params:acme:error:tls - 3.134.125.175: remote error: tls: no application protocol (ca=https://acme-staging-v02.api.letsencrypt.org/directory)","attempt":3,"retrying_in":120,"elapsed":191.7682608,"max_duration":2592000}
{"level":"error","ts":1710864124.928756,"logger":"tls.issuance.acme.acme_client","msg":"challenge failed","identifier":"d489-98-97-79-136.ngrok-free.app","challenge_type":"tls-alpn-01","problem":{"type":"urn:ietf:params:acme:error:tls","title":"","detail":"3.134.125.175: remote error: tls: no application protocol","instance":"","subproblems":[]}}
{"level":"error","ts":1710864124.928834,"logger":"tls.issuance.acme.acme_client","msg":"validating authorization","identifier":"d489-98-97-79-136.ngrok-free.app","problem":{"type":"urn:ietf:params:acme:error:tls","title":"","detail":"3.134.125.175: remote error: tls: no application protocol","instance":"","subproblems":[]},"order":"https://acme-staging-v02.api.letsencrypt.org/acme/order/140728084/15381494414","attempt":1,"max_attempts":3}
{"level":"error","ts":1710864124.9288766,"logger":"tls.obtain","msg":"could not get certificate from issuer","identifier":"d489-98-97-79-136.ngrok-free.app","issuer":"acme-v02.api.letsencrypt.org-directory","error":"HTTP 400 urn:ietf:params:acme:error:tls - 3.134.125.175: remote error: tls: no application protocol"}
{"level":"error","ts":1710864124.9289272,"logger":"tls.obtain","msg":"will retry","error":"[d489-98-97-79-136.ngrok-free.app] Obtain: [d489-98-97-79-136.ngrok-free.app] solving challenge: d489-98-97-79-136.ngrok-free.app: [d489-98-97-79-136.ngrok-free.app] authorization failed: HTTP 400 urn:ietf:params:acme:error:tls - 3.134.125.175: remote error: tls: no application protocol (ca=https://acme-staging-v02.api.letsencrypt.org/directory)","attempt":4,"retrying_in":300,"elapsed":314.6921661,"max_duration":2592000}

I’ve read lots of posts related to my issue but none of them seems to be exactly the same. For example, I see “remote error: tls: no application protocol” in the logs but I’m not sure what it means.

I’m installed NC using Docker on Windows 10. I’m using ngrok for the public domain of the nextcloud local instance. I’m not sure whether this issue has to do with ngrok or the nexcloud install (even though ngrok seems to be okay). For example, I can’t access https://localhost on the browser (which I believe should load Nextcloud locally).

Will be happy if anyone can point me in the right direction.

2

Hi, is ngrok functioning as reverse proxy?

3

Not sure whether it’s doing exactly that. I deployed it as a tunnel to expose the local server (in this case, Nextcloud) so that it’s accessible to remote clients.

To use it, I generated a random domain that points to port 443 in my local server. I entered this domain in the Nextcloud AIO interface (after disabling domain validation).

I basically followed the instructions in this post.

4

I fear you followed the wrong instructions then. See all-in-one/reverse-proxy.md at main · nextcloud/all-in-one · GitHub for the correct one

5

Hi. Thanks for the feedback. But I don’t know whether any of those options match my specific use case, and there’s no mention of ngrok.

If the problem is with the way I’ve configured Nextcloud using ngrok, I’m wondering what specific steps to take since, at the moment, ngrok is the more accessible option for me.

Also, if you don’t mind, what do the error messages in the logs actually mean?