Cursor or GitHub Copilot not working usually comes down to one of four layers: the editor or extension, the signed-in account and seat, organization policy or model settings, or the network path. Check them in that order. A VPN changes only the route and exit IP, so it helps with the last layer alone, while seats, plans, and trade-control restrictions stay as they are.［1］

Key Takeaways

Official availability and account eligibility are separate from network reachability.

Start with the platform's own support, status, and privacy documentation.

A VPN can only address a network-layer problem.

Cursor and GitHub Copilot are separate services with separate account and policy checks.

Is Cursor or GitHub Copilot not working because of the editor, account, or network?

Test the editor extension, web sign-in, account entitlement, and network independently; one surface failing does not identify the layer. Treat a country or region message, a sign-in failure, a missing feature, and a slow or blocked connection as different signals. Record the exact page or client, account state, full error text, network, and time before changing a route; a VPN can test the network layer, but it cannot change eligibility, billing, plan entitlements, or platform rules.

1. Official availability and account

Read the current account, plan, organization-policy, and service-status pages. Eligibility follows the account, the organization, and trade-control rules, not the network you test from.［1］［3］

2. Browser, app, and device

Use the official app or website, update it, clear only local cache when appropriate, and test one browser or device at a time. Avoid unofficial clients and copied login pages.

3. Network path

Check whether the same URL works on another trusted network, whether DNS and HTTPS are normal, and whether the service itself reports an incident. If a VPN is permitted and the issue is clearly network-level, test one route without making account or billing changes.

4. AI-coding-tool checks

Cursor and GitHub Copilot are separate products with separate accounts and policies.［3］ Check the editor login, organization policy, model availability, and data-residency setting; a route change cannot grant an organization entitlement or model access. Use the Copilot documentation and current Cursor model documentation for the exact product.

If your editor or agent calls models with your own API keys, a self-hosted LiteLLM gateway gives each tool a separate virtual key, so one failing route is easier to isolate.

How do you isolate a Cursor or Copilot access failure?

AI coding tools sit between three parties: your editor, the tool's own account service, and, for Copilot, your GitHub account and any organization that manages it.［3］ A failure in an editor panel can come from any of these, so the first step is to name the product and the layer before touching the network.

Which product and which editor?

Cursor is its own editor with its own account and model settings; GitHub Copilot is a GitHub product that runs as an extension in several editors and on GitHub itself.［2］［3］ Write down the product, the editor and its version, the extension version, and which account is signed in. "AI does not work" in Cursor and a greyed-out Copilot icon in another editor are unrelated problems, even on the same laptop.

Is your GitHub account or organization the deciding factor?

For Copilot, check that the GitHub account signed in to the editor is the one with a Copilot seat or subscription. If an organization provides Copilot, its administrators decide who gets a seat and which features and models are enabled; a feature that a colleague sees may be turned off by policy for you. GitHub also publishes how US trade controls restrict access for some regions and accounts.［1］ Messages that mention these restrictions are account and legal decisions, not connection problems, and a different network will not change them.

Is a model or feature simply not offered to you?

Both tools change their model lists over time, and some models are tied to particular plans or settings.［2］ If chat works but a specific model is missing, or an option that a guide mentions does not appear, check the current model availability documentation and your plan before suspecting the network. In Copilot, an organization can also restrict models; in Cursor, check the model settings and the plan shown in your account.

What should you record?

For each attempt, note the time, product, editor and extension versions, signed-in account, plan or seat, organization (if any), the network, and the exact error text or code from the editor's output or log panel. Never paste access tokens, API keys, or proprietary source code into a support ticket; describe the request instead, just as the beginner's AI workflow keeps secrets out of prompts. If the failure only affects one repository, note whether that repository belongs to an organization with its own policies.

How do you test the network without breaking the setup?

Corporate networks often route editor traffic through proxies or inspect HTTPS, which can break the connection to AI services even when the web works. Compare the same editor and account on a second trusted network, such as a home connection, and check whether your editor has proxy settings configured. If your employer requires its own VPN or proxy for work, follow that policy rather than replacing it. Where local law, your employer's policy, and the services' terms allow it, one personal VPN route can be a further comparison; do not sign in with a second account or change organizations to get around a policy.

In Cursor, Settings > Network > Run Diagnostics checks the connection to its servers, and setting HTTP Compatibility Mode to HTTP/1.1 can help when a corporate proxy blocks HTTP/2 streaming. Cursor's network help also notes that a VPN can trigger suspicious-activity messages and that DNS can fail after you disconnect one until Cursor is fully restarted.［4］

When should you hand it to support or your administrator?

Stop testing routes once the same error appears everywhere. Seat assignment, model policy, and organization settings go to your organization's administrator; individual Copilot subscriptions and account restrictions go to GitHub Support; Cursor plan, model, and account issues go to Cursor's support. Include the redacted record and the editor log lines, since they usually show which layer refused the request.

What can a VPN change?

It can change the path between your device and the service and replace the visible exit IP. This may help distinguish local blocking from an account or product restriction. Coding assistants often fail at a company proxy rather than at the provider; the network-layer comparison across AI tools compares that case with browser-based chat and image tools.

Editor extensions open their own connections, so an AethoVPN test for Cursor or Copilot has to cover the editor, not only the browser. Install the Windows client or the Linux .deb package (Debian/Ubuntu x64), keep global mode on so the editor process uses the tunnel, choose a nearby location marked green, and repeat the same completion or chat request with the same account and extension version. If completions return over the tunnel but time out on the plain network, include that result in the support packet. Seats, organization policy, and a broken extension install are not network issues. Download the Windows or Linux client for the machine you code on.

What can't a VPN change?

It cannot change country or identity data on an account, payment eligibility, age checks, subscription status, plan entitlements, moderation decisions, or the platform's terms. Do not create accounts, alter billing, or bypass unsupported service rules based on a VPN route.

Which coding-tool symptom points to which next step?

What you see	Most likely layer	Next step
Copilot icon is greyed out after GitHub sign-in	Seat, subscription, or wrong account	Check the signed-in account and seat assignment
A colleague sees a model you do not	Organization policy or plan	Ask the organization administrator or check the plan
A message about trade controls or restricted access	Account or legal restriction	Read GitHub's trade-controls page; contact GitHub Support
Cursor opens but chat requests fail	Cursor account, plan, or model setting	Check model settings and the plan in your account
AI features fail only on the office network	Proxy, HTTPS inspection, or filtering	Compare networks and check the editor's proxy settings

Summary

Separate official availability, account eligibility, device state, and network reachability.
Use a VPN only for a permitted network-layer test.
Keep account, payment, and identity information truthful and unchanged.

FAQ

Why can I sign in to GitHub but not use Copilot in my editor?

GitHub sign-in alone does not prove an assigned Copilot seat, enabled organization policy or working editor extension. Check the Copilot entitlement, editor authentication and exact feature notice separately.

Why does Cursor chat fail when the editor opens?

An open editor does not prove that Cursor's AI services can connect. Use Cursor's built-in network diagnostics, check the selected model and account state, then examine firewall or proxy restrictions if diagnostics fail.［4］

Can a VPN enable a Copilot model blocked by my organization?

No. GitHub says organization and enterprise policies govern feature and model access. Ask the administrator about the policy; changing an IP address does not grant a seat or override controls.

Should I compare Cursor and Copilot as one service?

No. They have separate sign-in, subscriptions, clients and service paths. Record which product, editor, extension, account and model failed before testing a second network.

What should I send to support for an AI coding tool failure?

Share the product, editor and extension version, account type, exact error and a safe diagnostic result. Redact repository code, secrets, tokens and private prompts from logs or screenshots.

Disclaimer: This article is for general informational purposes only and does not constitute legal, technical, or professional advice. Platform availability, account rules, and privacy settings can change; follow official requirements and local law.

Sources:

GitHub - Trade Controls — https://docs.github.com/en/site-policy/other-site-policies/github-and-trade-controls
Cursor Docs - Models & Pricing — https://cursor.com/docs/models-and-pricing
GitHub Docs - About GitHub Copilot — https://docs.github.com/en/copilot/get-started/about-github-copilot
Cursor Help - Network, proxy, and remote connections — https://cursor.com/help/troubleshooting/network

Sources checked 4 October 2026.

Related Articles:

Cursor or GitHub Copilot Not Working? How to Find the Cause