Warp does not work properly when connected through a proxy

[elviskahoro]

Describe the solution you'd like?

We've been getting reports that Warp doesn't work when connected to a proxy. Creating a public issue so people can subscribe.

Is your feature request related to a problem? Please describe.

No response

Additional context

No response

[Goooler]

Maybe can use system proxy by default?

[dev4joel]

I tried to fix it.🧐 https://embiid.blog/post/WARP-does-not-work-after-submitting-an-invite-code/

[tautomer]

Alternatively, go to /Applications/Warp.app/Contents/MacOS and launch warp via

ALL_PROXY="your_proxy" ./stable

Not sure which proxy is actually used, so I used ALL_PROXY. If you already have the proxies set in your rc file, ./stable works out of box.

@dev4joel's solution is nice, but for people behind proxies, installing another program can often be painful (need manager's approval and admin privilege, etc).

[dev4joel]

@tautomer WOW, That's COOL! TIL! Thanks.

[yam-liu]

Please fix it asap.

[dev4joel]

The login issue is here:

• 👉 https://github.com/warpdotdev/Warp/milestone/5

How to fix the confusing login flow issue is here:

• 👉 Can Not Sign Up Or Sign In Warp With Github(Public Beta)

How to fix the proxy issue is here:

• 👉 WARP-does-not-work-after-submitting-an-invite-code

[Arcadia822]

I still have connection problem.

set HTTP_PROXY or ALL_PROXY: not work

use the ALL_PROXY="your_proxy" ./stable command: not work

the error info is always:

10:35:08 [ERROR] Failed to authenticate user error sending request for url (https://securetoken.googleapis.com/v1/token?key=*****************): operation timed out

Caused by:
    operation timed out

• I do have proxy to connect github and google

[limux]

Alternatively, go to /Applications/Warp.app/Contents/MacOS and launch warp via

ALL_PROXY="your_proxy" ./stable

Not sure which proxy is actually used, so I used ALL_PROXY. If you already have the proxies set in your rc file, ./stable works out of box.

@dev4joel's solution is nice, but for people behind proxies, installing another program can often be painful (need manager's approval and admin privilege, etc).

The issue is resolved, the warp works!

[elviskahoro]

From #2089

1. Would like a feature to support configuring a command-line proxy? Similar to the iterm2 configuration on the 'login shell', for example 'export https_proxy=http://127.0.0.1:.XXXX'

[varenc]

This issue is a bit meandering and touches on a few different topics. For example, making it easy to set proxy variables when running a command in Warp seems quite different then Warp itself respecting your proxy settings.

I believe this issue is about Warp itself. So to make this clearer to the Warp team let me summarize the important bits as if this was a new issue:

---

Warp does not respect the macOS system wide proxy settings

Describe the bug

Warp does not respect the system wide proxy settings. If you set a proxy at the macOS level, in Preferences -> Network -> Advanced -> Proxies, these proxies settings are ignored by Warp and it'll attempt to access the internet directly without going through the proxy.

To Reproduce

Method 1:

• Get on a network where the only public internet access is available through a proxy set in your system wide settings.
• Observe that Warp's online features do not work.

Method 2:

• Install Charles Proxy by downloading it or using homebrew Casks: brew install charles
• Open up Charles, turn on the proxy, and enable the macOS system proxy setting.
• Observe that most all of your network traffic is now appearing in Charles, but not traffic from the Warp app. (look for the domain warp.dev). Restart Warp a few times to confirm this.

Expected behaviour

Warp should respect the system wide proxy settings like every other app. When a system wide proxy is set, Warp should use that proxy.

Workaround

Warp does respect the https_proxy environmental variable. Using this, and assuming Charles proxy is running on port 8888, you can make Warp use Charles proxy by launching it like this:

$ https_proxy=http://127.0.0.1:8888 /Applications/Warp.app/Contents/MacOS/stable

Or you can set a global macOS system environment variable like this:

$ launchctl setenv https_proxy 'http://127.0.0.1:8888'

And then launch Warp the usual way. (note: this will persist until reboot or unset with launchctl unsetenv)

The funny thing is if you want Warp to respect your proxy settings, you'll need to use another terminal program besides Warp to do it.

Operating System

MacOS

OS Version

12.6.1

Shell Version

zsh 5.8.1 (x86_64-apple-darwin21.0)

Warp Version

v0.2022.12.13.08.04.stable_01

[dannyneira]

Warp has recently added support for MacOS proxy settings. Please update to v0.2023.10.10.08.06.stable_02 or above. Please test and confirm if this has helped with the issue.

[ifplusor]

Warp has recently added support for MacOS proxy settings. Please update to v0.2023.10.10.08.06.stable_02 or above. Please test and confirm if this has helped with the issue.

It does not work in my computer.

[lobaak]

This slight variation of the original answer also appears to work.

ALL_PROXY="your_proxy" open -a Warp

[huhu415]

this is my solution, it works.
alias warp='https_proxy=http://127.0.0.1:6152 http_proxy=http://127.0.0.1:6152 all_proxy=socks5://127.0.0.1:6153 open -a Warp'
if first open the warp, usewarp, and you do not command + q to quit it, you can always use this proxy with warp.
so i recommand open this switch

[qiyuey]

I think warp should provide proxy setting function, which is a basic function of many software.