Setting up nextcloud - unable to reach 'open your nextcloud'

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

Hi to everybody, first of all I’m really getting mad to set up my nextckoud. I already tried it lots of times without any success, and that’s really frustrating. I’m a beginner user regarding linux, docker etc.
I live in Italy and I have an Iliad FTTH connection that grants me a public ipv4 but I can open ports only from 32768 (I think that’s part of the problem). This iliad connection and iliadboxos grants me a personal domain xxxxxx.iliadboxos.it which is already set up I currently use it to connect to my homeassistant server (via http). I have a RSA certificate too but no idea where the key is.
I already tried to set it up several times but last following GitHub - nextcloud/all-in-one: Nextcloud AIO stands for Nextcloud All-in-One and provides easy deployment and maintenance with most features included in this one Nextcloud instance.
I was able to arrive to https://localhost:8080/containers to see all of my containers are working properly but as I click on ‘open your nextcloud’ i got ERR_SSL_PROTOCOL_ERROR.
I checked my apache log and found these two logs:
{“level”:“error”,“ts”:1697384088.9664516,“logger”:“tls.obtain”,“msg”:“could not get certificate from issuer”,“identifier”:“xxxx.iliadboxos.it”,“issuer”:“acme-v02.api.letsencrypt.org-directory”,“error”:“HTTP 400 urn:ietf:params:acme:error:connection - 2a01:e11:1403:4e60::1: Timeout during connect (likely firewall problem)”}
{“level”:“error”,“ts”:1697384088.9664726,“logger”:“tls.obtain”,“msg”:“will retry”,“error”:“[xxxx.iliadboxos.it] Obtain: [xxxx.iliadboxos.it] solving challenge: xxxx.iliadboxos.it: [xxxx.iliadboxos.it] authorization failed: HTTP 400 urn:ietf:params:acme:error:connection - 2a01:e11:1403:4e60::1: Timeout during connect (likely firewall problem) (ca=https://acme-staging-v02.api.letsencrypt.org/directory)”,“attempt”:6,“retrying_in”:1200,“elapsed”:1276.3863032,“max_duration”:2592000}
please can anybody help me? I already spent days trying and trying, I’m really getting mad.

2

Hi, see What can I do when Nextcloud is not reachable via my domain or if I get `SSL_ERROR_INTERNAL_ERROR_ALERT` when opening my Nextcloud domain? ¡ nextcloud/all-in-one ¡ Discussion #2105 ¡ GitHub

3

i got either Authorization failed: HTTP 400 urn:ietf:params:acme:error:connection either Timeout during connect (likely firewall problem).
I know that I can open from external ports > 32768 to redirect to any of my internal, and I already did it, now external 33443 points to internal 443 but I think is not enough.
beside that I read several times the page you linked but it’s too hard for me to comprehend it, I don’t know how to check AAAA records or similar. Is there a guide or some instruction intended not for a professional or advanced user?

4

So port 443 is not forwarded and open in your router?

5

That’s what I can do
image
on WAN side I cannot set anything below 32768

6

All right then you found the Problem

7

any possible solution? I already got that this did is the problem, but I need a solution or a workaround…

8

See https://github.com/nextcloud/all-in-one#which-ports-are-mandatory-to-be-open-in-your-firewallrouter

9

again, no solution, just statements. Is it possible in some way to set the apache container to work on a port different from 443? let’s say for example on 33443?

10

See https://github.com/nextcloud/all-in-one#are-other-ports-than-the-default-443-for-nextcloud-supported

11

is there some guide to use either cloudflare tunnel or ACME DNS-challenge for somebody who don’t even know what they are?

12

See GitHub - nextcloud/all-in-one: Nextcloud AIO stands for Nextcloud All-in-One and provides easy deployment and maintenance with most features included in this one Nextcloud instance. and/or https://github.com/nextcloud/all-in-one#how-to-run-nextcloud-behind-a-cloudflare-tunnel and

13

unfortunately they doesn’t look like an ‘easy’ or within everyone’s reach… I think too much steps are missing to make me able to use it