Domain Discovery Issues - ID=QUERY-1kIjX Message=Instance not found

TL;DR

The maintainer's two options: build your own login UI, or have your application pass the organization context to ZITADEL by forwarding a scope parameter. ZITADEL doesn't support a custom organization login page out of the box yet.

Steps

1. ZITADEL doesn't support a custom organization login page out of the box yet. The maintainer's two options: build your own login UI, or have your application pass the organization context to ZITADEL by forwarding a scope parameter. If you're setting up domain discovery and hitting 'Instance not found', check whether you actually need a custom login page first, since that's the unsupported part.

When to use

You are seeing this: Issue zitadel/zitadel#7514 (closed, 20 comments): ### Preflight Checklist - [X] I could not find a solution in the documentation, the existing issues or discussions - [X] I have joined the ZITADEL chat Use this skill when you run into "Domain Discovery Issues - ID=QUERY-1kIjX Message=Instance not found".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Sources

• https://zitadel.com/chat

In gh:zitadel/zitadel#7514 (ZITADEL), the issue reported was: Issue zitadel/zitadel#7514 (closed, 20 comments): ### Preflight Checklist

• [X] I could not find a solution in the documentation, the existing issues or discussions
• [X] I have joined the ZITADEL chat

Environment

ZITADEL Cloud

Version

No response

Database

None

Database Version

No response

Describe the problem caused by this bug

Hello,

Trying to setup my Zitadel instance to function with an alternative login page for an Organization and am running all via Docker Containers.

The primary domain/Instance is: login.example.com The organization instance and verified domain is:... The verified resolution from the thread: ZITADEL doesn't support a custom organization login page out of the box yet. The maintainer's two options: build your own login UI, or have your application pass the organization context to ZITADEL by forwarding a scope parameter. If you're setting up domain discovery and hitting 'Instance not found', check whether you actually need a custom login page first, since that's the unsupported part. Source: mount the host path https at container path //github.com/zitadel/zitadel/issues/7514