https://linen.dev logo
Join Slack
Powered by
Hi! The permit pdp docker container log is fill wi...
# permit-saas
c
Hi! The permit pdp docker container log is fill with the following warning
Copy code
horizon.opal_relay_api                  |WARNING | Could not report uptime status to server: got status code 503 from relay-api. This does not affect the PDP's 
operational state or data updates.\n", "record": {"elapsed": {"repr": "0:03:43.577686", "seconds": 223.577686}, "exception": null, "extra": {}, "file": {"name": 
"opal_relay_api.py", "path": "/app/horizon/opal_relay_api.py"}, "function": "_run", "level": {"icon": "⚠️", "name": "WARNING", "no": 30}, "line": 183, "message": 
"Could not report uptime status to server: got status code 503 from relay-api. This does not affect the PDP's operational state or data updates.", "module": 
"opal_relay_api", "name": "horizon.opal_relay_api", "process": {"id": 17, "name": "MainProcess"}, "thread": {"id": 281472985017632, "name": "MainThread"}, "time": 
{"repr": "2025-11-18 06:59:00.254824+00:00", "timestamp": 1763449140.254824}}}
Is there any setting I did not set, like the uptime server url?
a
Hi @Chuck Chau, I'm an AI assistant for Permit.io. I'll analyze available sources and get back to you shortly.
This warning about the relay-api returning a 503 status code is a non-critical issue that doesn't affect your PDP's functionality. The log message itself states "This does not affect the PDP's operational state or data updates." The relay-api URL is controlled by the 
PDP_CONTROL_PLANE_RELAY_API
configuration (1) , which defaults to 
<https://opal-relay.api.permit.io>
. This is a Permit.io controlled configuration that typically shouldn't be changed . The 503 error (Service Unavailable) suggests a temporary connectivity issue with Permit.io's relay service, which handles uptime reporting. Since this is just for telemetry and doesn't impact authorization decisions or policy updates, you can safely continue operating. To help our engineers investigate this further, could you please provide: 1. Which Workspace / Project / Env you are using 2. What calls you are performing (as SDK code or CURL) 3. Which PDP version you are running 4. Any other relevant logs from your PDP If the warnings are too verbose and you want to reduce log noise, you can adjust the log level, though the uptime reporting will continue attempting in the background.
To learn more, see the sources I considered: [[1] Configurations](https://docs.permit.io/concepts/pdp/configuration)
o
this is nothing to be concerned with, as the log itself indicates, and as the AI noted
c
Will it be returned to normal?
If not, I would rather turn off the feature.
o
Yes. probably a little later today
c
ok, no problem then, just bad luck to see bad stuffs.
By the way, PDP_ORG_API_KEY is no longer working with 0.9.8
Only the PDP_API_KEY continue to work
o
I'll open a ticket to have that investigated
c
It can be used to start the PDP, however, it will fail on check API.
Copy code
ErrorCode: ForbiddenAccess, ErrorType: api_error, Message: The access for this object is forbidden using the provided API key
That key is Org key, suppose to be the master key.
o
Hey @Chuck Chau, few questions regarding your issue: • Have you followed this documentation to configure your pdp with the org level api key ? • Did it work for you with previous PDP versions ?
c
Yes, this was my previous configuration. My previous image version was 0.5.x. It was working for at least a year.
Copy code
--env PDP_ORG_API_KEY=<YOUR_ORG_API_KEY> \
  --env PDP_ACTIVE_PROJECT=<YOUR_PROJECT_ID_OR_KEY> \
  --env PDP_ACTIVE_ENV=<YOUR_ENVIRONMENT_ID_OR_KEY> \
are all defined.
I just updated to 0.9.8 recently.
Anyway, I have fell back to PDP_API_KEY. Have you guys tested 0.9.x with PDP_ORG_API_KEY? It is able to start the service, but it failed on check query.
a
Hey @Chuck Chau, will make sure the team see your message and will circle back to you soon
Open in Slack
PreviousNext
Powered by