transport: received unexpected content-type "application/json"

[iyobo]

After configuring the profile and using it, I keep getting the error

• rpc error: code = Unimplemented desc = unexpected HTTP status code received from server: 404 (Not Found); transport: received unexpected content-type "application/json"

[vavsab]

@iyobo I need at least your code example that is failing to help you.
It could be due to mixing grpc & rest apis. But need to know which resources you are trying to create and at which resource it's failing exactly.

[cenk1cenk2]

@iyobo did you ever got the chance to figure out what was wrong and why would you receive this message? In my case it happens in every kind of resource, so I bet that I am missing the correct configuration.

[cenk1cenk2]

I have immediately figured this out since the error looked simialr and will leave it here for any other fellow that will search this here.

The reason why this happens is that the provider calls the GRPC endpoints for management. And if you install the zitadel like as I did through helm and your ingress controller or reverse proxy that does not support mixed requests of GRPC and HTTP like I did with the nginx, you would explicitly have to create and mark the given paths as GRPC for the endpoints given in the API documentation here.