Zalo Won't Log In Through a Proxy: Find the Cause Step by Step

Step 1: make sure the proxy is alive

Before blaming Zalo, test the proxy on its own. Paste it in ip:port:user:pass format into the proxy checker, or run this in a terminal:

curl -x http://user:pass@ip:port https://api.ipify.org

If it prints the proxy IP, the proxy works and the problem sits on the computer or in the app. If it fails, use the error table below. Also check the dashboard to confirm the proxy has not expired; an expired proxy stops accepting connections until it is renewed.

Common errors and what they mean

Each error has its own guide: 407 proxy authentication required, ERR_TUNNEL_CONNECTION_FAILED and proxy timeout.

Step 2: is Zalo PC really going through the proxy?

This is the most common cause with Zalo PC. You set a proxy in Windows or in the browser, the browser works, but Zalo PC does not. Many desktop apps ignore the system proxy setting or use it for only part of their traffic, as explained in proxy works in the browser but not in apps.

The reliable fix is Proxifier, which forces the Zalo process through the proxy:

• Add the proxy as type HTTPS with the address and port, enable authentication and enter the username and password. Click Check to let Proxifier test it.
• Create a rule for the Zalo application. Zalo PC may run several processes, so watch Proxifier's connection log while Zalo opens and add every process that connects.
• Do not point the default rule at the proxy if only Zalo should use it; that tends to slow down or break other software.
• Restart Zalo after creating the rule. An app that is already open often keeps its old connections.

Step 3: check Zalo Web in the browser

• Antidetect profile: proxy type HTTP, correct port, and the profile's built-in proxy test passes. Review the GenLogin or Chrome guide if you configure it directly.
• Extensions: ad blockers or script blockers sometimes block Zalo Web's real-time connection. Disable them in that profile to test.
• Old cookies: if the profile logged into Zalo from another IP before, clear the Zalo site cookies and scan the QR code again.
• Expired QR code: the code is valid only briefly. On a slow connection it can expire before the page finishes loading; reload for a fresh one.

Step 4: local software and the system clock

Antivirus and firewall software can block Zalo or Proxifier from connecting out, especially right after installation. Allow both apps in the firewall, or disable it briefly to confirm the cause and then turn it back on. The full checklist is on check the proxy and firewall.

A wrong system clock causes certificate errors on HTTPS connections, so Zalo reports no network even though the proxy is fine. Turn on automatic time sync in Windows or macOS.

If a VPN is running alongside the proxy, switch it off. Two stacked relays cause errors and change the IP Zalo sees.

When Zalo asks for verification, the proxy is not broken

When an account signs in from a new device or IP, Zalo may ask you to confirm on the phone that is already logged in, or send a code by SMS. That is account protection, not a proxy failure. Confirm on the main phone and keep using the same IP afterwards; with a stable IP and device, these prompts usually become rare.

If you change IPs constantly, every change is another login from a new location. That is why accounts should use fixed IPs rather than rotating proxies. The guide to managing multiple Zalo accounts covers IP planning per account, and Vietnam proxies lists the static ISP and private IPv4 options.

If nothing works

• Note the proxy IP, the time of the error, a screenshot of the message and the curl result from step 1.
• Try the same proxy on another computer or a brand-new profile to see whether the fault is the proxy or the machine.
• Open a support ticket from the dashboard with those details. Support runs 24/7, and if a technical fault on the proxy side cannot be fixed, refunds follow the refund policy.

Frequently asked questions