Proxy works in the browser but not in the app: causes and fixes

Updated: 2026-11-12

If the proxy works in your browser but an app refuses to use it, the proxy itself is almost certainly fine. The issue is that the app does not read your system proxy settings. Many desktop apps, games, command-line tools and apps built on certain frameworks open their own network connections and ignore whatever you set in Windows or macOS. The fix is to find the app's own proxy setting, set environment variables for command-line tools, or use software such as Proxifier to force the app's traffic through the proxy. This guide helps you work out which case you are in and fix it step by step.

Dedicated HTTP/HTTPS proxies

See pricing Free Proxy Checker

Why browsers pick up the proxy and apps do not

On Windows and macOS, browsers such as Chrome and Edge read the system proxy settings by default. Turn on a proxy in network settings and the browser follows it. Firefox has its own settings but can also use the system proxy.

Apps are different. Each one decides how it connects. Some call the operating system's networking library and inherit the system proxy. Others ship their own networking code, connect directly to their servers and never learn that a proxy exists. Games often use their own protocols, and so do many chat, trading and sync apps. The system proxy setting is a suggestion, not a rule every app must obey.

Step 1: confirm the proxy is alive

Before touching the app, prove the proxy works in a way that does not depend on it. Open what is my IP in a browser that uses the proxy; it should show the proxy IP. Or run curl -x http://user:pass@ip:port https://api.ipify.org, which should return the proxy IP.

If this fails, the app is not the problem. Read proxy connected but no internet first.

Step 2: work out what kind of app it is

A quick way to classify it: open the app's settings and look for Proxy, Network or Connection. If there is nothing, enable the system proxy, restart the app and check the IP it reports, or watch in Proxifier whether the app connects directly.

App type	How it handles proxies	What to do
Has a Proxy option in settings	Its own configuration	Enter IP, port, username and password in the app
Uses the system proxy	Reads Windows or macOS settings	Enable the system proxy and restart the app
Command-line tool or script	Reads environment variables or flags	Set `HTTP_PROXY`, `HTTPS_PROXY` or pass a proxy flag
Ignores every setting	Connects directly	Use Proxifier to force traffic through the proxy
Uses a non-HTTP protocol	Needs a proxy that supports that protocol	Test carefully before buying; an HTTP/HTTPS proxy may not fit

Step 3: use the app's own proxy setting

This is always the cleanest route. Telegram, for example, has a built-in proxy section; see setting up a proxy in Telegram. Antidetect browsers also accept a proxy per profile. Choose HTTP or HTTPS and enter the IP, port, username and password from your ip:port:user:pass line. VinaProxy proxies use HTTP/HTTPS with username and password authentication, so do not pick SOCKS in the app.

Step 4: environment variables for command-line tools

Tools such as curl, git, pip, npm and many Python and Node.js libraries read proxy environment variables. In Windows PowerShell, set them for the current session:

$env:HTTPS_PROXY="http://user:pass@ip:port" and $env:HTTP_PROXY="http://user:pass@ip:port"

On macOS or Linux use export HTTPS_PROXY=http://user:pass@ip:port. Some tools only read lowercase names and some only uppercase, so set both. There is more detail in HTTP proxy environment variables. If your password contains special characters such as @ or :, URL-encode them.

Step 5: Proxifier for stubborn apps

Proxifier intercepts an app's network connections at the system level and routes them through a proxy, even when the app has no idea a proxy exists. It is the standard answer for desktop apps without a proxy setting.

Go to Profile > Proxy Servers > Add, enter the IP and port, choose HTTPS, enable authentication and fill in the username and password.
Click Check so Proxifier tests the connection to the proxy.
Open Profile > Proxification Rules, add a rule, pick the app's executable under Applications and choose your proxy under Action.
Leave the Default rule as Direct so only the chosen app uses the proxy.
Launch the app and watch the Proxifier log: its connections should show the proxy name, not Direct.

What the Proxifier log shows	Meaning
Connections marked Direct	The rule does not match the app; check the executable name
Authentication error	Wrong username or password; see the 407 error guide
Connection opens and closes immediately	The app uses a protocol an HTTP proxy cannot carry

When an HTTP proxy cannot help

Some games and real-time apps send their main traffic over UDP. HTTP/HTTPS proxies only relay TCP connections, so even if Proxifier catches the app, the UDP part may bypass the proxy or simply fail. For these apps, test one IP before buying more and read proxies for online games. Full step-by-step setup is in the Proxifier setup guide.

Frequently asked questions

Why does the app still show my real IP after I enable the Windows proxy?

Because that app does not read the system proxy. Look for a proxy option inside the app or use Proxifier to route its traffic.

Does Proxifier work with username and password proxies?

Yes. When you add the proxy, choose HTTPS, enable authentication and enter the username and password from your ip:port:user:pass line.

My game still bypasses the proxy even with Proxifier. Why?

Many games use UDP for their main traffic, while HTTP/HTTPS proxies only relay TCP. In that case an HTTP proxy is not the right tool.

Do I need the system proxy on if I use Proxifier?

No. Proxifier handles app connections by its rules. Running both can cause loops or conflicts, so stick to one method.

My Python script ignores the proxy environment variables. What now?

Check whether the script disables environment proxies, set both uppercase and lowercase names, or pass the proxy directly in the proxies argument of the requests library.