Can You Use OpenAI Codex in Hong Kong? Sign-in Failures, 403s and Constant Reconnecting
Codex users in Hong Kong usually hit one of three things: the CLI sign-in never completes, requests come back as 403, or tasks run but keep 'Reconnecting'. They all look like 'it won't connect', but the causes differ. Here is whether Codex works in Hong Kong, and how to tell which problem you have.
Keywords: codex hong kong, openai codex hong kong, can i use codex in hong kong, codex cli hong kong, codex hong kong credit card
Last updated: · Maintained by Voguesly Residential IP
- Codex follows OpenAI's supported-region list, which does not include Hong Kong, Macau or mainland China (checked 22 September 2026).
- Three common symptoms: CLI sign-in never completes, 403 unsupported_country_region_territory, or constant 'Reconnecting'. The first two are region problems, the third is the network path.
- Most CLI failures come from the terminal not using your proxy: set HTTPS_PROXY in that terminal and check the exit IP there.
Short answer: Codex follows the same region list as ChatGPT
Codex is an OpenAI product. OpenAI's published list of supported countries and territories (checked on 22 September 2026) does not include Hong Kong, Macau or mainland China. So whether you use the Codex CLI, an IDE extension or the web version, requests that leave from a Hong Kong exit can be stopped by the region check.
Signing in with a ChatGPT account or using an API key makes no real difference here: in both cases what counts is the exit of the machine sending the request.
Three common symptoms and what they mean
| Symptom | Usually | Check first |
|---|---|---|
| CLI sign-in: the browser step finishes, but the terminal never gets the result or reports failure | Browser and terminal use different exits, or the exit is in an unsupported region | Whether browser and terminal show the same exit IP |
| Requests return 403 unsupported_country_region_territory | Region: the terminal's exit is in an unsupported region | The terminal's exit IP location |
| Tasks run but keep reconnecting or the stream drops | Network path: an unstable exit, packet loss, or long connections being cut | Exit stability and latency |
The first two are about region; the third is about the network path. Knowing which one you have saves a lot of trial and error.
The one people miss: your terminal doesn't use your browser's network
ChatGPT works fine in the browser, yet the Codex CLI can't connect. Usually the browser goes through a proxy and the terminal does not. Most command-line tools ignore the system proxy settings on macOS and Windows by default.
- Set HTTPS_PROXY / HTTP_PROXY in your terminal to point at your local proxy port;
- or let your proxy client take over all traffic in TUN mode;
- then check the exit IP from that same terminal window and make sure it matches the browser.
Paying for it
When you sign in to Codex with a ChatGPT account, your usage comes from your ChatGPT plan. At checkout, payment risk checks compare card country, IP location and billing address. A card that 'won't go through' from Hong Kong is usually a mismatch between those three, not a problem with the card. See the payment section of Can you use ChatGPT in Hong Kong?
Why long tasks drop more often
A Codex task can run for minutes, holding a connection the whole time. If the exit changes, packets drop, or the IP is treated as high risk and triggers extra checks, the task disconnects and retries. So beyond the right region, two things matter:
- Stability: keep the same exit for the whole task, and avoid auto-rotating servers;
- Type: a home broadband (residential) IP usually has a cleaner profile than a datacenter IP and gets fewer extra checks.
Results still depend on your account, network and the platform's policies. Nothing removes disconnects entirely; the aim is to make them rarer.
Steps for stable use in Hong Kong
- Run the free AI IP test to see your browser's exit region and IP type;
- Check the exit again from the terminal that runs Codex and make sure both match;
- Use an exit in a supported region, ideally a home broadband IP, with DNS exiting in the same region;
- Keep that exit fixed while long tasks run.
Voguesly (易联) provides US home broadband exits on carriers such as AT&T and Verizon, usable from Hong Kong, Macau and mainland China, with a ¥3.9 (≈ US$0.58, charged in CNY) trial pack to start.
FAQ
Can I use Codex in Hong Kong?
Codex is an OpenAI product and follows OpenAI's supported-region list. As of September 2026 the list does not include Hong Kong, so requests from a Hong Kong exit can be blocked by the region check.
Why does the Codex CLI return 403 in Hong Kong?
unsupported_country_region_territory means the terminal's exit is in an unsupported region. Your terminal does not use the browser's proxy by default, so check the exit IP from the terminal itself.
Is constant 'Reconnecting' a region problem?
Usually not. If tasks run but keep reconnecting, it is normally an unstable exit, packet loss or long connections being cut. Confirm the region is fine first, then look at exit stability.
Can I pay for Codex with a Hong Kong credit card?
Codex usage generally comes with a ChatGPT plan. Failed payments are usually caused by a mismatch between card country, IP location and billing address, not by the card itself.