Is this a bug in the Domain submission on initial setup?

crustysparks · December 15, 2024, 7:08am

Support intro

Sorry to hear you’re facing problems.

The community help forum (help.nextcloud.com) is for home and non-enterprise users. Support is provided by other community members on a best effort / “as available” basis. All of those responding are volunteering their time to help you.

If you’re using Nextcloud in a business/critical setting, paid and SLA-based support services can be accessed via portal.nextcloud.com where Nextcloud engineers can help ensure your business keeps running smoothly.

Getting help

In order to help you as efficiently (and quickly!) as possible, please fill in as much of the below requested information as you can.

Before clicking submit: Please check if your query is already addressed via the following resources:

Official documentation (searchable and regularly updated)
How to topics and FAQs
Forum search

(Utilizing these existing resources is typically faster. It also helps reduce the load on our generous volunteers while elevating the signal to noise ratio of the forums otherwise arising from the same queries being posted repeatedly).

Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can.

The Basics

Nextcloud Server version (e.g., 29.x.x):
- 10.0.0
Operating system and version (e.g., Ubuntu 24.04):
- 24.04
Web server and version (e.g, Apache 2.4.25):
- 2.4.62
Reverse proxy and version _(e.g. nginx 1.27.2)
- none
PHP version (e.g, 8.3):
- 8.3
Is this the first time you’ve seen this error? (Yes / No):
- through several attempts from scratch - first time setting up and using next cloud
When did this problem seem to first start?
- ever since trying to set up a new instance
Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
- AIO
Are you using CloudfIare, mod_security, or similar? (Yes / No)
- No

Summary of the issue you are facing:

Not able to get past the submit domain setup.
Don’t know where to find the Docker Run command to skip domain.
Every time, with every new “From Scratch” setup I’m seeing the same error in the docker log.
I can ping the site name successfully

DNS is right, can ping next.crustysparks.ca and also access externally the setup page on :8443.

Steps to replicate it (hint: details matter!):

build new server Ubuntu 24.04
install Docker
run the command for installing the AIO image as given on the website.
access the setup page at :8443

Log entries

Nextcloud

Please provide the log entries from your Nextcloud log that are generated during the time of problem (via the Copy raw option from Administration settings->Logging screen or from your nextcloud.log located in your data directory). Feel free to use a pastebin/gist service if necessary.

PASTE HERE
Docker log from running "sudo docker logs -f nextcloud-aio-mstercontainer"

NOTICE: PHP message: Could not get digest of container nextcloud/aio-domaincheck:latest cURL error 7: Failed to connect to registry-1.docker.io port 443 after 2001 ms: Could not connect to server (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://registry-1.docker.io/v2/nextcloud/aio-domaincheck/manifests/latest
NOTICE: PHP message: Not pulling the image for the nextcloud/aio-domaincheck container because docker hub does not seem to be reachable.
NOTICE: PHP message: Could not get digest of container nextcloud/all-in-one:latest cURL error 7: Failed to connect to registry-1.docker.io port 443 after 0 ms: Could not connect to server (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://registry-1.docker.io/v2/nextcloud/all-in-one/manifests/latest
</html>nter>nginx</center>uest was sent to HTTPS port</center></title></head>rustysparks.ca:443" was: <html>
NOTICE: PHP message: Expected was: 0d048a61fef1ec2195749b0db2d7481119297bc123ec8057

Notice that the first letter of the domain name is missing.

Apache access.log
172.16.0.99 - - [15/Dec/2024:02:24:48 +0000] "POST /api/configuration HTTP/1.1" 422 29 "https://172.16.0.109:8080/containers" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:129.0) Gecko/20100101 Firefox/129.0"
172.16.0.99 - - [15/Dec/2024:02:25:19 +0000] "POST /api/configuration HTTP/1.1" 422 396 "https://172.16.0.109:8080/containers" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:129.0) Gecko/20100101 Firefox/129.0"

From sudo systemctl status docker:

Dec 14 12:21:17 nextserver dockerd[31665]: time="2024-12-14T12:21:17.639935057-08:00" level=info msg="Docker daemon" commit=92a8393 containerd-snapshotter=false storage-driver=overlay2 version=27.4.0
Dec 14 12:21:17 nextserver dockerd[31665]: time="2024-12-14T12:21:17.640063157-08:00" level=info msg="Daemon has completed initialization"
Dec 14 12:21:17 nextserver dockerd[31665]: time="2024-12-14T12:21:17.719088782-08:00" level=info msg="API listen on /run/docker.sock"
Dec 14 12:21:17 nextserver systemd[1]: Started docker.service - Docker Application Container Engine.
Dec 14 16:42:50 nextserver dockerd[31665]: time="2024-12-14T16:42:50.173836727-08:00" level=error msg="[resolver] failed to query external DNS server" client-addr="udp:172.17.0.2:55543" dns-server="udp:172.16.0.253:53" error="read udp 172.17.0.2:55543->172.16.0.253:53: i/o timeout" question=";e5.o.lencr.org.\tIN\t A" spanID=5125c50588a11a23 traceID=7375e971c14d3299f6dcac30a3978327
Dec 14 16:42:50 nextserver dockerd[31665]: time="2024-12-14T16:42:50.173949628-08:00" level=error msg="[resolver] failed to query external DNS server" client-addr="udp:172.17.0.2:42891" dns-server="udp:172.16.0.253:53" error="read udp 172.17.0.2:42891->172.16.0.253:53: i/o timeout" question=";e5.o.lencr.org.\tIN\t AAAA" spanID=c841ac63e6a4ce3a traceID=2e0607da56eea83e126a57f7edf28244
Dec 14 16:44:06 nextserver dockerd[31665]: time="2024-12-14T16:44:06.094045082-08:00" level=warning msg="Security options with `:` as a separator are deprecated and will be completely unsupported in 17.04, use `=` instead."
Dec 14 16:44:07 nextserver dockerd[31665]: time="2024-12-14T16:44:07.366912244-08:00" level=info msg="No non-localhost DNS nameservers are left in resolv.conf. Using default external servers"
Dec 14 16:44:07 nextserver dockerd[31665]: time="2024-12-14T16:44:07.691108284-08:00" level=warning msg="Security options with `:` as a separator are deprecated and will be completely unsupported in 17.04, use `=` instead."
Dec 14 17:54:44 nextserver dockerd[31665]: time="2024-12-14T17:54:44.386255880-08:00" level=error msg="[resolver] failed to query external DNS server" client-addr="udp:172.17.0.2:54953" dns-server="udp:172.16.0.253:53" error="read udp 172.17.0.2:54953->172.16.0.253:53: i/o timeout" question=";yahoo.ca.\tIN\t AAAA" spanID=bd372962f62d1a2a traceID=5fff48055c93ef1bd5834fa5a80bc614


#### Web Browser

If the problem is related to the Web interface, open your browser inspector *Console* and *Network* tabs while refreshing (reloading) and reproducing the problem. Provide any relevant output/errors here that appear.

PASTE


#### Web server / Reverse Proxy

The output of your Apache/nginx/system log in `/var/log/____`:

PASTE HERE



### Configuration
 
#### Nextcloud

The output of `occ config:list system` or similar is best, but, if not possible, the contents of your `config.php` file from `/path/to/nextcloud` is fine (make sure to remove any identifiable information!):

PASTE HERE


#### Apps

The output of `occ app:list` (if possible).

### Tips for increasing the likelihood of a response

* Use the `preformatted text` formatting option in the editor for all log entries and configuration output.
* If screenshots are useful, feel free to include them. 
  - If possible, also include key error output in text form so it can be searched for.
* Try to edit log output only minimally (if at all) so that it can be ran through analyzers / formatters by those trying to help you.

scubamuc · December 15, 2024, 9:34am

Hey @crustysparks welcome to the community

Is this a bug in the Domain submission on initial setup?

nope, just a typo

crustysparks:

</html>nter>nginx</center>uest was sent to HTTPS port</center></title></head>rustysparks.ca:443" was: <html>
NOTICE: PHP message: Expected was: 0d048a61fef1ec2195749b0db2d7481119297bc123ec8057

Notice that the first letter of the domain name is missing.

did you see this message? add a “c” to “rustyparks.ca” and you should be fine

crustysparks · December 15, 2024, 3:25pm

I type the full domain name:

crustysparks · December 15, 2024, 6:28pm

Even when I exclude the host name next and only put in crustysparks.ca it truncates it to sparks.ca. So, I don’t see how this could not be a bug or something is just totally wrong with my setup.

crustysparks · December 15, 2024, 6:31pm

… as well, what’s with the error in the docker daemon …

level=warning msg=“Security options with : as a separator are deprecated and will be completely unsupported in 17.04, use = instead.”

jtr · December 16, 2024, 3:39pm

crustysparks:

NOTICE: PHP message: Could not get digest of container nextcloud/aio-domaincheck:latest cURL error 7: Failed to connect to registry-1.docker.io port 443 after 2001 ms: Could not connect to server (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://registry-1.docker.io/v2/nextcloud/aio-domaincheck/manifests/latest
NOTICE: PHP message: Not pulling the image for the nextcloud/aio-domaincheck container because docker hub does not seem to be reachable.
NOTICE: PHP message: Could not get digest of container nextcloud/all-in-one:latest cURL error 7: Failed to connect to registry-1.docker.io port 443 after 0 ms: Could not connect to server (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://registry-1.docker.io/v2/nextcloud/all-in-one/manifests/latest
</html>nter>nginx</center>uest was sent to HTTPS port</center></title></head>rustysparks.ca:443" was: <html>

The “…was sent to HTTPS” suggests the test is running against a weird URL like http://domain.tld:443 (rather than https://). This only happens if the APACHE_PORT has been overridden and you’re trying to use your own reverse proxy.

The error output suggests you have an nginx reverse proxy in the mix. So it doesn’t sound like you’re using AIO’s reverse proxy, but trying to use your own? You didn’t mention that.

Can you share your actual run command? There are different ones in the docs, depending on your deployment scenario.

crustysparks · December 16, 2024, 8:42pm

I started with a bare bones install of Ubuntu 24.0.4 and didn’t install the LAMP stack or Ngnix other than Docker based on their website rather than using the convenience link provided on Nextcloud’s site. Then I ran the docker installation of AIO command line as per the instructions

I’m at a loss as to how to get to the .tld link. Is that something that I should add to my host file? Because the URL doesn’t resolve.

jtr · December 16, 2024, 8:51pm

Again, please post the actual command. You keep saying “as per the instructions” but there are multiple instruction sets, depending on your goals.

crustysparks · December 16, 2024, 9:46pm

For Linux and without a web server or reverse proxy (like Apache, Nginx, Caddy, Cloudflare Tunnel and else) already in place:

sudo docker run
–init
–sig-proxy=false
–name nextcloud-aio-mastercontainer
–restart always
–publish 80:80
–publish 8080:8080
–publish 8443:8443
–volume nextcloud_aio_mastercontainer:/mnt/docker-aio-config
–volume /var/run/docker.sock:/var/run/docker.sock:ro
nextcloud/all-in-one:latest