JanJ
ZITADEL•12mo ago
Jan

404 on GetMyUser

I'm using the Rust crate (https://github.com/smartive/zitadel-rust) to communicate with a locally installed Zitadel (available on http://zitadel-127-0-0-1.nip.io:31080 (which resolves to localhost)). It successfully negotiates an access token using a service account, however when attempting to do any gRPC requests I get a 404 error.

For example:
Reverse proxy (Traefik) log:
10.244.0.1 - - [17/Jan/2025:07:25:47 +0000] "GET /.well-known/openid-configuration HTTP/1.1" 200 2243 "-" "-" 23 "zitadel-zitadel-zitadel-127-0-0-1-nip-io@kubernetes" "http://10.244.2.35:8080" 29ms
10.244.0.1 - - [17/Jan/2025:07:25:47 +0000] "GET /oauth/v2/keys HTTP/1.1" 200 865 "-" "-" 24 "zitadel-zitadel-zitadel-127-0-0-1-nip-io@kubernetes" "http://10.244.1.25:8080" 19ms
10.244.0.1 - - [17/Jan/2025:07:25:47 +0000] "POST /oauth/v2/token HTTP/1.1" 200 927 "-" "-" 25 "zitadel-zitadel-zitadel-127-0-0-1-nip-io@kubernetes" "http://10.244.2.35:8080" 42ms
10.244.0.1 - - [17/Jan/2025:07:25:47 +0000] "POST /zitadel.auth.v1.AuthService/GetMyUser HTTP/2.0" 404 32 "-" "-" 26 "zitadel-zitadel-zitadel-127-0-0-1-nip-io@kubernetes" "http://10.244.1.24:8080" 4ms


The only thing Zitadel logs (with Log.Level=debug): 2025/01/17 07:25:47 ERROR: Failed to extract ServerMetadata from context

Using wireshark I can also see that the response from Zitadel (those 32 bytes) is {"code":5,"message":"Not Found"}. The package capture of the entire interaction is attached.

I can access the API using the REST interface through Python without issue. Using Zitadel 2.67.2 (should be latest).

Any idea what might be causing this or how to further troubleshoot it?
zitadel-404-capture.pcapng12.86KB
Was this page helpful?