#Here is my configuration
1 messages · Page 1 of 1 (latest)
Hello @dusky prairie , could you please add PERMIFY_LOG_ENABLED: false? The reason for this is that the logger is trying to upload the logs to telemetry, which is why you can't see them. By adding this, you should be able to view the logs.
thank you I am able to resolve the issue, I was missing backoff-frequence variable. But now, eventhough the server is up I am seeing this message ERROR: Failed to extract ServerMetadata from context I am not sure what this really means. Also is there a way to exclude /healthz endpoint bearer authentication ?
Could you send the request body you sent to permify?
If you send the request with sdk could you share which sdk are you using?
I am just hitting /healthz from browser
these are the messages in the server logs
2024-08-15 18:23:18 time=2024-08-15T12:53:18.120Z level=ERROR msg="failed to extract authorization header from gRPC request" error="rpc error: code = Unauthenticated desc = Request unauthenticated with Bearer"
2024-08-15 18:23:18 time=2024-08-15T12:53:18.120Z level=ERROR msg="finished call" protocol=grpc grpc.component=server grpc.service=grpc.health.v1.Health grpc.method=Check grpc.method_type=unary peer.address=127.0.0.1:40932 grpc.start_time=2024-08-15T12:53:18Z grpc.code=Unknown grpc.error=ERROR_CODE_MISSING_BEARER_TOKEN grpc.time_ms=0.887
2024-08-15 18:23:18 2024/08/15 12:53:18 ERROR: Failed to extract ServerMetadata from context
Which permify version are you using?
should be this version Permify v1.0.1
Can you update the image section to the following to ensure it is correct? guard: image: ghcr.io/permify/permify:v1.0.1 container_name: permify_guard environment: ...
I still have that error message
Hi @dusky prairie , yes, there's an issue with the health endpoint when OIDC is enabled. Could you open an issue for this?
sure