Domain does not point to this server or the reverse proxy is not configured correctly.

[johentsch]

How to use GitHub

• Please use the 👍 reaction to show that you are affected by the same issue.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
• Subscribe to receive notifications on status change and new comments.

Steps to reproduce

1. Install Manjaro ARM on Raspberry Pi 4
2. Install UFW firewall and open ports 443 & 8443
3. Set up dynDNS and have router forward ports 443 & 8443 to Raspberry Pi
4. Launch docker AIO 1.3.0
5. Open the instance through the domain and enter the domain under Please type in the domain that will be used for Nextcloud if you want to create a new instance:

Expected behavior

Setup should continue.

Actual behavior

Error message Domain does not point to this server or the reverse proxy is not configured correctly. See the mastercontainer logs for more details. ('sudo docker logs -f nextcloud-aio-mastercontainer'). Setup is stuck.

Host OS

Manjaro ARM

Nextcloud AIO version

1.3.0

Current channel

?

Other valuable info

This problem has occurred in #20 and #27 (among others) but I'm not using any reverse proxy.

It's just strange when you reach the server via a domain:443 to then hear it say that this domain doesn't point to it.

The hint Make sure that this server is reachable on Port 443 and you've correctly set up the DNS config for the domain that you enter. would be more insightful if there was documentation on how to correctly set up the DNS config.

P.S.: It's more than awesome that we can now run this complex interplay of services with one command! However, someone might want to use NC in their home network exclusively and without making it reachable through a domain. This currently seems to be impossible: Yes, I can reach the instance inside the network, but I cannot skip past this setup step, IP addresses are not accepted.

[szaimen]

Hello, can you please post the mastercontainer logs here?

[JoCat]

I faced a similar problem, tried to do and through duckdns.org and noip.com, also tried to bind to a personal domain linked to Cloudflare. In all 3 cases the error Domain does not point to this server or the reverse proxy is not configured correctly. See the mastercontainer logs for more details. ('sudo docker logs -f nextcloud-aio-mastercontainer').

If I invoke the command and see what's in the logs, I get the following:

NOTICE: PHP message: The response of the connection attempt to "http://***.duckdns.org:443" was: Client sent an HTTP request to an HTTPS server.
NOTICE: PHP message: Expected was: 3f40f2b74e89e58fa208c6a52425c7cf302902b3fa9b6f39
NOTICE: PHP message: The error message was: 
NOTICE: PHP message: The response of the connection attempt to "http://***.jocat.ru:443" was: Client sent an HTTP request to an HTTPS server.
NOTICE: PHP message: Expected was: 3f40f2b74e89e58fa208c6a52425c7cf302902b3fa9b6f39
NOTICE: PHP message: The error message was: 
NOTICE: PHP message: The response of the connection attempt to "http://***.ddns.net:443" was: Client sent an HTTP request to an HTTPS server.
NOTICE: PHP message: Expected was: 3f40f2b74e89e58fa208c6a52425c7cf302902b3fa9b6f39
NOTICE: PHP message: The error message was: 

In all 3 cases for some reason the request goes to http with port 443. I don't use any proxy servers, only on the router I threw port 443 to 8443 on the server.

If I use SKIP_DOMAIN_VALIDATION=true, the installation goes through, but the site is still down, and according to the logs, requests to Let's Encrypt are failing because the domain binding is not working correctly.

[johentsch]

Sadly I don't remember any details that would help you but for me it turned out to be a configuration error on my fritzbox. Once I had setup the HTTPS port forwarding correctly it worked...

[szaimen]

@JoCat is it possible that you are behind CGNAT?

[JoCat]

I don't think so, my ISP gives me a static ip.
Maybe me should open port 80 and forward it to the server, but I don't have access to this server for the time being.
So I'll check it sometime later.

[JoCat]

Opening port 80 seemed to help, domain activation failed, but with SKIP_DOMAIN_VALIDATION=true the installation went more correctly.

[szaimen]

Yes, I can reach the instance inside the network, but I cannot skip past this setup step, IP addresses are not accepted.

Do I understans corretly that you did not open port 443?

[johentsch]

Yes, the port is open and the instance can be reached via https://domain.dns-service.tld

[szaimen]

See https://github.com/nextcloud/all-in-one#how-to-skip-the-domain-validation