ZYBrowser

English

简体中文

English

简体中文

Appearance

Proxy Troubleshooting ​

Diagnose proxy issues in this order: connection details, provider restrictions, local client capabilities, and profile assignments. Never send real passwords, API URLs, or complete proxy connection details to an untrusted destination.

Proxy Test Fails ​

CheckResolution
Protocol mismatchConfirm that HTTP, HTTPS, or SOCKS5 matches the provider's connection type. Integrated Proxies supports switching only between HTTP and SOCKS5
Incorrect host or portA custom proxy host must be an IPv4 address or domain, and the port must be an integer from 1 to 65535
Authentication failureVerify the username, password, and provider IP allowlist. Leading and trailing spaces are removed from custom proxy credentials when saving
Provider node unavailableUse the provider's connection tool or console to check node status, expiration, and regional restrictions
Current client cannot testProxy testing requires the desktop client and is unavailable in the web app

After correcting the issue, run another test from the Test Result column. The list updates both the status and test time.

Proxy API Cannot Fetch a Proxy ​

If Check URL or saving fails, confirm that:

  1. The URL begins with http:// or https:// and is complete.
  2. It returns readable text containing a valid IPv4:port.
  3. The returned port is within 1-65535.
  4. The provider does not require the current network egress to be allowlisted and its request rate limit has not been exceeded.
  5. You are retrying in the desktop client; the web app cannot perform local fetch checks.

When testing a Proxy API from the list, the client checks the saved IP first. If it is no longer valid, the client fetches and saves a new address. The fetch policy, URL availability, and provider rate limit can therefore all affect the result.

Invalid Batch Import Format ​

Each custom proxy must use host:port[:username[:password]][{note}], with an optional http://, https://, or socks5:// prefix. Parsing fails when:

  • The host is not an IPv4 address or valid domain.
  • The port is empty, nonnumeric, or outside 1-65535.
  • More than four colon-separated fields are present, such as an unescaped ASCII colon in the username or password.
  • A note exceeds 40 characters.
  • More than 500 records are entered at once or an IPv6 address is used.

The input area marks invalid lines. Correct every format error before deciding whether to enable Add successful proxies only and Check duplicate proxies.

Integrated Proxy Synchronization, Renewal, or Deletion Is Restricted ​

Sync FourLeaf Proxies requires the desktop client and valid authorization. If authorization expires, follow the client prompt in the system browser and remain on the current page until it is complete.

A FourLeaf proxy must be renewed on the provider's website. An integrated proxy purchased directly through ZYBrowser supports renewal and auto-renewal in the list. A directly purchased integrated proxy cannot be deleted; deleting a synchronized FourLeaf record removes only the ZYBrowser record and does not affect the provider resource.

Cannot Assign Profiles or Use an Action ​

SymptomCause and resolution
Clicking the assignment count does nothingThe current member lacks Assign Proxy permission. Ask a team administrator to grant it under Manage Members and Roles
Assignment dialog cannot be confirmedSelect at least one browser profile
Assignment list is emptyThe active team has no available profiles; members with create permission can create one from the empty state
Create, edit, or delete buttons are missingThe current member lacks Create Proxy, Edit Proxy, or Delete Proxy permission respectively
Password or full connection details cannot be copiedComplete credentials are protected by Edit Proxy permission

If a profile still cannot access the target website after launch, also review whether its proxy location, time zone, geolocation, and language are reasonably consistent under Configure Location and Regional Parameters.

Next Steps ​