-
Describe the bugWhen using Codex through CLIProxyAPI, authentication works correctly through the configured proxy, and normal requests also work. However, the token refresh flow appears to ignore the configured proxy settings. As a result, refresh requests fail with:
If I enable a system-wide/global proxy, token refresh works again. This suggests that:
Steps to reproduce
Actual behaviorToken refresh fails repeatedly with logs like: |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 1 reply
-
|
Beta Was this translation helpful? Give feedback.
-
|
Please confirm that you are in a supported country. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @luispater , I’d like to follow up on this because I believe the root cause is specifically about proxy handling in the refresh path, not general region support. What I can reproduce consistently is:
So the key issue seems to be:
This is why the error looks like a region issue, but the actual bug appears to be that refresh is not using the same proxy settings as normal Codex requests. Could you please confirm whether the token refresh HTTP client is initialized from the same proxy source as the normal request client? |
Beta Was this translation helpful? Give feedback.

unsupported_country_region_territoryPlease confirm that you are in a supported country.