A Hotel Wi-Fi Check Before the Codex Release Fix

Coding-agent routes EN2026-10-27

You have a release fix to finish, a laptop on hotel Wi-Fi, and Codex CLI waiting in your terminal. The browser works, but the coding assistant times out. Before changing API keys or reinstalling anything, check the route your terminal uses to reach the internet.

Travelling adds several possible checkpoints: a hotel login page, your company VPN, a corporate proxy and the API service itself. Understanding which checkpoint failed makes troubleshooting much less mysterious.

The corporate proxy between Codex and the API

A proxy is an intermediary that sends network requests on your behalf. Companies use proxies to enforce access rules, record connections or inspect traffic. Your browser may receive its proxy settings automatically, while a command-line application may need separate configuration.

A VPN is different: it changes how traffic reaches a network. Your employer might require both a VPN and a proxy. Neither a working browser nor a connected VPN proves that Codex CLI has the access it needs.

The hotel network check before opening Codex

Open a browser and complete the hotel’s Wi-Fi login page. Until that is done, command-line requests may be redirected or blocked.
Connect the company VPN if your organisation requires it. Follow your employer’s travel and location policies.
Ask IT for the proxy address, port, authentication method and certificate requirements. Do not guess these from another team’s setup.
Confirm that sending repository content to your chosen AI provider or relay is permitted. Network access is not the same as data-handling approval.

Proxy variables in the terminal launching Codex

Many command-line networking libraries read proxy environment variables. In a macOS or Linux shell, a typical starting point is export HTTPS_PROXY="http://proxy.company.example:8080". If IT also requires it, set export HTTP_PROXY="http://proxy.company.example:8080".

The http:// prefix here describes the connection to the proxy; it does not mean the destination API stops using HTTPS. Use the exact proxy scheme and address supplied by IT.

Launch Codex from that same terminal so it inherits the variables. An already-running editor or terminal may still have the old environment. On Windows PowerShell, the equivalent session setting is $env:HTTPS_PROXY = "http://proxy.company.example:8080".

Proxy support can vary by Codex version and networking component. Check your installed version’s documentation if these settings have no effect. Avoid adding the API host to NO_PROXY: that variable requests a direct connection and may bypass the required corporate route.

Certificate errors on an inspected connection

Some corporate proxies inspect HTTPS traffic and present certificates signed by the company’s own certificate authority. Your browser may trust that authority while Codex does not.

If you see a certificate verification error, obtain the approved certificate and installation instructions from IT. Confirm how your installed Codex build loads trusted certificates; different runtimes can use different trust stores. Do not disable TLS verification or assume that a Node.js certificate setting controls every component of Codex.

RelayVano configuration after proxy access works

If your organisation permits an external relay, I recommend RelayVano as a pay-as-you-go option for accessing supported AI models from Codex. Its API base is https://api.relayvano.com. Sign up for RelayVano, then use its current Codex configuration instructions and a dedicated API key.

The proxy address and API base are separate settings: the proxy controls the network route, while the API base identifies the service receiving requests. Copy the documented provider configuration and exact model identifier rather than guessing endpoint suffixes. For Codex, confirm that the configured provider supports the API interface your installed version requires, including Responses API support where applicable.

A short failure checklist before the release fix

Timeout or connection refused: check VPN status, proxy address, port and destination allowlisting.
HTTP 407: investigate proxy authentication, not the model API key.
Certificate verification failure: check corporate certificate trust.
HTTP 401 or 403: identify which service returned it before changing credentials or permissions.
HTTP 404 or an unsupported-model error: check provider configuration, API path and model identifier.

Keep API keys and proxy passwords out of shell history, screenshots and support logs. Once a small, non-sensitive Codex request succeeds, return to the release fix—not before.