VPN for Codex: check sign-in and coding tasks

Start on the device you will actually use. Download the free BratVPN app from the downloads page, then use the email form on this page to request a trial. You can keep these instructions open in a browser throughout setup.

Write down whether the problem happens when opening Codex, signing in, getting a response, reading a project or running a command. Those are different connections and permissions. A browser loading the account page does not show that every development task can run, and a failing project test is not automatically a network failure.

For a first comparison, use a small project or a harmless question that needs no credentials, private repository or destructive command. Keep the same computer and task while changing one connection condition. Save existing work before closing a terminal or application so your connectivity test does not lose unfinished changes.

With a local desktop, CLI or editor workflow, check the computer where the process runs. A VPN on a separate phone does not connect that process. If the tool runs on another machine or in a remote development environment, the network of that environment also matters; identify it before changing your laptop repeatedly.

Follow the current official installation and sign-in instructions for your interface. Check the application version and the error wording. On a managed computer, take an explicit connection or permission message to your administrator. Do not paste access keys into a chat or disable device security just to make a connection test pass.

Codex Cloud runs tasks on OpenAI-managed computers. The environment selected for a task supplies its project setup, dependencies and network access. Connecting your local BratVPN app can help you test your own access to Codex, but does not change the remote computer's network or repository permissions.

If opening the task works but fetching a dependency or repository fails inside it, use the task's own error to identify the affected service and environment. Follow the cloud environment documentation and your organization's access rules. Avoid repeatedly creating new tasks as a network test when important work is still in the original task.

Codex availability depends on your account, plan, workspace settings and the interface you use. Confirm that you selected the intended account and workspace. Repository access and permission to run a task are separate from having a working internet connection; a VPN does not grant either of them or reset a usage limit.

A missing dependency, a failed build and a service connection error need different fixes. Keep the exact failing step, platform, application version and approximate time for support. Redact paths containing personal names, private repository details and authentication data. BratVPN access does not include an OpenAI plan or API credit, so verify the required account features separately before purchasing VPN time.

On iPhone or iPad, install through App Store and allow the VPN configuration when iOS asks. On Android, use Google Play or the official Android download when offered on the downloads page. Enter your activation code in BratVPN, not in the other app's login field.

For Windows and macOS, use the official installer on the downloads page and connect on that computer. A VPN connection on your phone does not automatically protect a separate laptop, television or other device. Keep only the VPN profile you intend to test connected.

After testing, open the purchase page to compare current plans and payment options. Save the activation code after payment is confirmed and follow the app instructions. You can also use the existing app or Telegram purchase options when convenient.

If a test fails, tell support the app version, device platform, approximate time, network type and the step that failed. Do not include passwords, email verification codes, VPN activation codes or private messages in a public report. BratVPN is independent of the services named here.