This could be related to several network-specific factors in your sidecar deployment. Here are the key areas to investigate: ​*Network Configuration & Timeouts*​ The PDP has several timeout configurations that might be relevant (1) : •

PDP_OPA_CLIENT_QUERY_TIMEOUT

(default: 1 second) - controls the timeout for querying OPA for authorization decisions •

PDP_CONTROL_PLANE_TIMEOUT

(default: 75 seconds) - timeout for control plane requests •

PDP_HEALTHCHECK_TIMEOUT

(default: 3 seconds) - timeout for health checks In private network environments with restrictive firewalls or network policies, these timeouts might be too short, or connectivity to required endpoints might be blocked. ​*Required Connectivity*​ Your PDP sidecar needs to establish connections to several Permit.io endpoints : •

PDP_CONTROL_PLANE

(default:

<https://api.permit.io>

) •

OPAL_SERVER_URL

(default:

<https://opal-v2.permit.io>

) •

OPAL_SERVER_WS_URL

(default:

<wss://opal-v2.permit.io>

) - WebSocket connection If any of these are blocked or have intermittent connectivity in certain private networks, it could cause hanging requests. ​*Proxy Configuration*​ If your private network requires HTTP proxy access, you need to configure the

ALL_PROXY

environment variable :

ALL_PROXY=<http://proxy.example.com:8080>

Note that your proxy must support HTTP/2 and WebSocket connections for the PDP to function properly . ​*To help diagnose this further, could you provide:*​ 1. Which Workspace / Project / Env you are using 2. What calls are being performed (as SDK code or CURL) 3. Which PDP version you are running 4. Relevant logs from your PDP (especially around the time requests hang) This will help our engineers investigate the root cause of the hangi

To learn more, see the sources I considered: [[1] Configurations](https://docs.permit.io/concepts/pdp/configuration)