Stuck with SSL_ERROR_INTERNAL_ERROR_ALERT or ERR_SSL_PROTOCOL_ERROR when opening my Nextcloud domain?

[sarimsa]

Discussed in #2105

I newly installed Debian GNU/Linux 12 (bookworm) and then the AIO Docker Image following Nextcloud All-in-One on my labtop.

Now indeed I get a SSL_ERROR_INTERNAL_ERROR_ALERT issue when trying to open Nextcloud on my domain. I checked my Apache container logs via sudo docker logs nextcloud-aio-apache and found

Authorization failed: HTTP 400 urn:ietf:params:acme:error:connection

I took the Debian system "as is". Obviously being a newbe, I need your help to understand

• what a AAAA DNS-record is and where and how to remove that.
• Similary, what is and how to remove any CNAME entry that might be added to your domain for a test and
• how to check if I'm be using cloudflare, and how to check that I'm not behind CGNat (you don't have your own public ip-address - I do, so I assume no challenges here). and that you are not behind a DS-Lite connection (you only have a public ipv6 but no public ipv4 address - I use ipv4, so I assume no challenges here).
• Also make sure that port 443 is correctly forwarded! --> Which ip do I use: the one from system (ie assinged from router, as I did and should work) or the ip assigned to docker?
• Finally: is the default setup of Debian using cloudflare? How can i check this out?

Thanks a lot for any support

[sarimsa]

Well, I made a step forward with the help of DNS Checker.
It did not find an AAAA record, nor a CNAME. I also did not find any signs of using cloudflare.
The port 443 is forwarded to the ip of my labtop assigned by the router.

Where else could the Authorization failed issue come?

Thanks

[szaimen]

Hi, did you check that the port is open using a port checker?

And is the A record for your domain actually the public ip-address of your home network?

---

You might want to check out this guide if you are not able to make things work: #5439