Nextcloud Domain Checker running on wrong vlan

ℹ️ Support
, ,
1

The Basics

  • Nextcloud Server version (e.g., 29.x.x):
    • AIO latest(34?)
  • Operating system and version (e.g., Ubuntu 24.04):
    • Unraid Docker
  • Is this the first time you’ve seen this error? (Yes / No):
    • yes
  • When did this problem seem to first start?
    • right after first install
  • Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
    • Docker Image

Summary of the issue you are facing:

Hello,

i got a NextCloud AIO install (docker) on a unraid server. The server has multiple VLANs. I had no problem to tell NextCloud to run on vlan 3. But I can´t find where I can tell it to start the “nextcloud-aio-domaincheck” also on vlan 3. It always uses the first/untagged vlan.

Is there a parameter I can give the docker image at start?

Thanks in advance.

2

@HeribertB welcome to the Nextcloud community :waving_hand:

please check whether your compose.yml has the domain check variable active or whether ist being skipped:

# SKIP_DOMAIN_VALIDATION: false # This should only be set to true if things are correctly configured. See https://github.com/nextcloud/all-in-one#how-to-skip-the-domain-validation
3

Thanks for your answer.

Yes the domaincheck is active. I am aware that i can disable it but that was not my question.

The “nextcloud-aio-mastercontainer” when it starts also starts a container called “nextcloud-aio-domaincheck”. Although the mastercontainer is running on vlan 3 it always starts the domain check on vlan 1.

Is there a way to tell the mastercontainer to start the domaincheck on vlan 3?

4

Solved it by moving the server to the different vlan. Had to manualy tell the Docker the dns server but then everything worked.