How to disable domain check?

ℹ️ Support
, , ,
1

I tried with SKIP_DOMAIN_VALIDATION=true and properly restarting (removing volumes and containersS) but I see alway this screen:

Nextcloud AIO v9.6.0

Domaincheck container is not running

This is not expected. Most likely this happened because port 8383 is already in use on your server. You can check the mastercontainer logs and domaincheck container logs for further clues. You should be able to resolve this by adjusting the APACHE_PORT by following the reverse proxy documentation. Advice: have a detailed look at the changed docker run command for AIO.

Nginx configuration:

    location / {
        proxy_pass https://127.0.0.1:8888$request_uri;

        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Port $server_port;
        proxy_set_header X-Forwarded-Scheme $scheme;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header Accept-Encoding "";
        proxy_set_header Host $host;

        client_body_buffer_size 512k;
        proxy_read_timeout 86400s;
        client_max_body_size 0;

        # Websocket
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection $connection_upgrade;
    }

docker-compose file

    volumes:
      - nextcloud_aio_mastercontainer:/mnt/docker-aio-config
      - /var/run/docker.sock:/var/run/docker.sock:ro
    ports:
      - 8888:8080
    environment:
      # APACHE_PORT: 8888
      # APACHE_IP_BINDING: 
      SKIP_DOMAIN_VALIDATION: true

Tried with internal docker address on Nginx and commented docker-compose lines.

There is a clear way to disable this check?

2

Hi, can you follow all-in-one/reverse-proxy.md at main · nextcloud/all-in-one · GitHub?

3

Okay, I double-checked everything and I have SKIP_DOMAIN_VALIDATION=true on docker-compose.yml file and the instance continue showing this screen.

What I’m missing? I just want to turn it off.

nextcloud-aio-mastercontainer  | NOTICE: PHP message: Could not start domaincheck container: Could not start container nextcloud-aio-domaincheck: Server error: `POST http://127.0.0.1/v1.41/containers/nextcloud-aio-domaincheck/start` resulted in a `500 Internal Server Error` response:
4

It still not possible to skip the domaincheck bug-feature?

5

It is possible since many years already: GitHub - nextcloud/all-in-one: 📦 The official Nextcloud installation method. Provides easy deployment and maintenance with most features included in this one Nextcloud instance.

6

It is possible, but it might not do what you expect it to do: https://github.com/nextcloud/all-in-one?tab=readme-ov-file#can-i-use-an-ip-address-for-nextcloud-instead-of-a-domain

7

2 posts were split to a new topic: How to make AIO work with self-signed certificate?

8

Btw @orwellwasright this is your problem…

You can fix this e.g. by uncommenting and using APACHE_PORT: 11000. Then the domaincheck container should start correctly.

Following all-in-one/reverse-proxy.md at main · nextcloud/all-in-one · GitHub should have given you clues on this.

9

That’s not true. I quote myself:

Can anybody point how to completely (and truly) disable domain-check on AIO installation?

Resetting instance won’t help. You can try to follow the official guides to replicate.

10

This topic is not solved.

This configuration:

    ports:
      - 8383:8080
    environment:
      APACHE_PORT: 8383
      SKIP_DOMAIN_VALIDATION: true
      APACHE_IP_BINDING: 127.0.0.1

Don’t work:

Nextcloud AIO v9.8.0
Domaincheck container is not running

This is not expected. Most likely this happened because port 8383 is already in use on your server.

This configuration:

#    ports:
#      - 8383:8080
    environment:
      APACHE_PORT: 8383
      SKIP_DOMAIN_VALIDATION: true
      APACHE_IP_BINDING: 127.0.0.1

Don’t work:

Nextcloud AIO v9.8.0
Domaincheck container is not running

This is not expected. Most likely this happened because port 443 is already in use on your server.

This configuration:

#    ports:
#      - 8383:8080
    environment:
      APACHE_PORT: 8383
      # SKIP_DOMAIN_VALIDATION: true
      APACHE_IP_BINDING: 127.0.0.1

This:

    ports:
      - 8080:8080
    environment:
      APACHE_PORT: 8383
      # SKIP_DOMAIN_VALIDATION: true
      APACHE_IP_BINDING: 127.0.0.1

Or this one:

#    ports:
      - 8080:8080
    environment:
      APACHE_PORT: 8383
      SKIP_DOMAIN_VALIDATION: true
      APACHE_IP_BINDING: 127.0.0.1

Don’t work:

Bad Gateway - Error 502

This configuration:

#    ports:
      - 8383:8080
    environment:
      APACHE_PORT: 8383
      # SKIP_DOMAIN_VALIDATION: true
      APACHE_IP_BINDING: 127.0.0.1

Don’t work:

Nextcloud AIO v9.8.0
Domaincheck container is not running

This is not expected. Most likely this happened because port 8383 is already in use on your server.

Using # SKIP_DOMAIN_VALIDATION: true gives the same:

This is not expected. Most likely this happened because port XXXX is already in use on your server.

Removed volumes, network and containers following this guide.

Nothing works in order to disable domain-checking and using a Reverse Proxy.

I can reformulate my initial question:

:interrobang: How to disable domain-check AND actually use Nextcloud behind Nginx Reverse Proxy?