[Bug]: HTTP 404 when connecting custom TypeScript login UI to self-hosted Zitadel instance

[Casburggraaf]

Preflight Checklist

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

Version

master and v2.71.7 of zitadel

Describe the problem caused by this bug

I’m trying to connect a custom TypeScript-based login UI to my self-hosted Zitadel instance, but I’m encountering an HTTP 404 error when attempting to access the /loginname page.

Error:

⨯ Error [ConnectError]: [unimplemented] HTTP 404
    at <unknown> (.next/server/chunks/8278.js:1:137572)
    at w (.next/server/chunks/8278.js:1:138049)
    at next (.next/server/chunks/8278.js:1:173467)
    at async Object.unary (.next/server/chunks/8278.js:1:172726)
    at async Object.l [as listOrganizations] (.next/server/chunks/8278.js:1:47329)
    at async p (.next/server/app/(login)/loginname/page.js:1:19119) {
  rawMessage: 'HTTP 404',
  code: 12,
  metadata: {
    date: 'Thu, 17 Apr 2025 06:41:06 GMT',
    content-type: 'application/json',
    content-length: '33',
    vary: 'Origin',
    x-robots-tag: 'none',
    strict-transport-security: 'max-age=31536000; includeSubDomains'
  },
  details: [],
  cause: undefined,
  digest: '2844608709'
}

To reproduce

1. Set up a self-hosted Zitadel instance (latest version)
2. Install the official TypeScript custom login UI
3. Configure it to connect to the self-hosted backend
4. Navigate to /ui/v2/login/loginname

Screenshots

Expected behavior

The login page should load and allow users to enter their login name.

Relevant Configuration

Zitadel version: v2.71.7
Frontend: TypeScript custom login UI (from zitadel/zitadel-login repo)
Deployment: tried on Vercel and custom infrastructure

Additional Context

No response