Using the self built zitadel service, the front-end project opens a log message with HTTP 404
I built the backend service of zitadel locally using Docker, and the frontend uses the project source of zitadel typescript，The error is as follows：
⨯ Error [ConnectError]: [unimplemented] HTTP 404
at <unknown> (.next/server/chunks/2151.js:10:121781)
at v (.next/server/chunks/2151.js:10:122258)
at next (.next/server/chunks/2151.js:10:157654)
at async Object.unary (.next/server/chunks/2151.js:10:156913)
at async Object.i [as listOrganizations] (.next/server/chunks/2151.js:10:52148)
at async q (.next/server/app/(login)/loginname/page.js:2:11565) {
rawMessage: 'HTTP 404',
code: 12,
metadata: Headers {
'content-type': 'application/json',
'content-length': '32',
vary: 'Origin',
'x-robots-tag': 'none',
date: 'Fri, 08 Aug 2025 07:59:06 GMT',
server: 'APISIX/3.13.0'
},
details: [],
cause: undefined,
digest: '263790501'
}
Error fetching custom translations: Error [ConnectError]: [unimplemented] HTTP 404
at <unknown> (.next/server/chunks/2151.js:10:121781)
at v (.next/server/chunks/2151.js:10:122258)
at next (.next/server/chunks/2151.js:10:157654)
at async Object.unary (.next/server/chunks/2151.js:10:156913)
at async Object.i [as getHostedLoginTranslation] (.next/server/chunks/2151.js:10:52148) {
rawMessage: 'HTTP 404',
code: 12,
metadata: Headers {
'content-type': 'application/json',
'content-length': '32',
vary: 'Origin',
'x-robots-tag': 'none',
date: 'Fri, 08 Aug 2025 07:59:06 GMT',
server: 'APISIX/3.13.0'
},
details: [],
cause: undefined
}
There is no problem using the cloud address of zitadel in the environment variable ZITADEL_SPI-URL in the frontend, so are there any special requirements for setting up zitadel Docker
⨯ Error [ConnectError]: [unimplemented] HTTP 404
at <unknown> (.next/server/chunks/2151.js:10:121781)
at v (.next/server/chunks/2151.js:10:122258)
at next (.next/server/chunks/2151.js:10:157654)
at async Object.unary (.next/server/chunks/2151.js:10:156913)
at async Object.i [as listOrganizations] (.next/server/chunks/2151.js:10:52148)
at async q (.next/server/app/(login)/loginname/page.js:2:11565) {
rawMessage: 'HTTP 404',
code: 12,
metadata: Headers {
'content-type': 'application/json',
'content-length': '32',
vary: 'Origin',
'x-robots-tag': 'none',
date: 'Fri, 08 Aug 2025 07:59:06 GMT',
server: 'APISIX/3.13.0'
},
details: [],
cause: undefined,
digest: '263790501'
}
Error fetching custom translations: Error [ConnectError]: [unimplemented] HTTP 404
at <unknown> (.next/server/chunks/2151.js:10:121781)
at v (.next/server/chunks/2151.js:10:122258)
at next (.next/server/chunks/2151.js:10:157654)
at async Object.unary (.next/server/chunks/2151.js:10:156913)
at async Object.i [as getHostedLoginTranslation] (.next/server/chunks/2151.js:10:52148) {
rawMessage: 'HTTP 404',
code: 12,
metadata: Headers {
'content-type': 'application/json',
'content-length': '32',
vary: 'Origin',
'x-robots-tag': 'none',
date: 'Fri, 08 Aug 2025 07:59:06 GMT',
server: 'APISIX/3.13.0'
},
details: [],
cause: undefined
}
There is no problem using the cloud address of zitadel in the environment variable ZITADEL_SPI-URL in the frontend, so are there any special requirements for setting up zitadel Docker
