Cursor stopped pushing to GitHub and lost all internet access

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I’m experiencing a critical issue with Cursor that appeared suddenly.

For the last two months everything was working perfectly — Cursor was able to:

run git push to GitHub from the integrated terminal,

access external websites (e.g., curl https://github.com),

install/update packages,

fetch and pull repositories.

However, starting two days ago, Cursor completely lost internet access.

Current behavior:

git push fails with the error:

error setting certificate verify locations: CAfile: /etc/ssl/cert.pem CApath: none

Any HTTPS request fails:

curl: (77) error setting certificate verify locations

Cursor cannot reach GitHub at all — neither through Git, nor through curl.

No changes were made to my local environment. The exact same commands that worked earlier now fail 100% of the time.

Important details:

I am using Cursor on macOS.

My local Git works normally from the standard terminal.

Only Cursor lost the ability to push or make external HTTPS requests.

This happened suddenly without any configuration changes.

It looks like the internal sandbox environment lost its certificate store or access to the internet entirely.

Steps to Reproduce

Steps to Reproduce

Open Cursor on macOS.

Open any project connected to a GitHub repository.

Run git push from Cursor’s built-in terminal.
→ Push fails with certificate error:

error setting certificate verify locations: CAfile: /etc/ssl/cert.pem CApath: none

Run any HTTPS request from the same terminal, for example:

curl -I https://github.com

→ Returns:

curl: (77) error setting certificate verify locations

Try gh auth login or git fetch — all commands fail due to inability to verify SSL certificates.

Check local macOS terminal outside of Cursor — git push, curl, and all network operations work normally.

Restart Cursor, reload window, reinstall — problem persists.

Result: Cursor’s internal environment has no access to the internet and cannot validate certificates.

Expected Behavior

Expected: Cursor should be able to perform Git operations, HTTPS requests, and access GitHub as before.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.1.50
VSCode Version: 1.105.1
Commit: 56f0a83df8e9eb48585fcc4858a9440db4cc7770
Date: 2025-12-06T23:39:52.834Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 23.5.0

For AI issues: which model did you use?

GPT 5.1 High

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

Hey @Tim_Look

Thanks for reporting this. I can reproduce this when using GPT 5.1. When I switch over to Claude, things work as expected.

Oddly enough, once I’ve done that, git pushes start working again on GPT 5.1. When I switch to a new Agent… I have to do it again.

Is it possible for you to give something like that a try? Switch to another model, try a git push, and see if that sticks.

In the meantime, I’ll report this internally.

perfect, it helped, thank you

The bug has been identified, and we’re working to resolve it. Thanks a lot for this report :pray:

1 Like

Hey @Tim_Look

I’m not experiencing the behavior anymore – so let me know if you are!

@Colin I’m seeing what appears to be a closely related issue, specifically with the agent using GitHub CLI:

Cursor: 2.2.36

In my own terminal, gh issue list, gh issue view, etc. all work fine.

Inside Cursor’s agent sandbox (when using Auto ), any gh command fails with TLS errors like:

Post “https://api.github.com/graphql”: tls: failed to verify certificate: x509: OSStatus -26276

gh auth login from tools also fails with the same TLS error.

If I switch off Auto and explicitly use another model (e.g. Composer 1), the same tool commands start working again. When I go back to Auto, the TLS failures return.

So it seems similar to the certificate / sandbox issue described here, specifically tied to which agent/model is active. Happy to provide more logs or try repro steps if helpful.

Hey @charliecode.io !

Please raise a fresh bug report.

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.