On this page
Before you start
Use the active order that contains the endpoint you want this profile to use.
HostProxy server hostname or address shown in DashboardPortThe separate connection port for the selected protocolUsernameThe authentication username from the active orderPasswordThe authentication password from the active order
Treat the username and password as private credentials. Do not place them in screenshots, tickets, or public messages.
If you do not have an order yet, review current locations, line types, and prices before returning to this guide. View static residential IPs
Map the GetIPProxy fields
Enter each value in its matching field. Do not add a protocol prefix to the host unless the browser explicitly requests a complete URL.
| GetIPProxy value | Browser field | What to enter |
|---|---|---|
Host | 代理地址 | Proxy server hostname or address shown in Dashboard |
Port | 端口 | The separate connection port for the selected protocol |
Username | 账号 | The authentication username from the active order |
Password | 密码 | The authentication password from the active order |
Host代理地址- Proxy server hostname or address shown in Dashboard
Port端口- The separate connection port for the selected protocol
Username账号- The authentication username from the active order
Password密码- The authentication password from the active order
Configure the proxy in Zhanfu Browser
UI labels can change between client versions. Use the referenced path as the current starting point and confirm the saved connection before opening the profile.
- 1
Open 新建环境
Open 新建环境 in Zhanfu Browser and continue to 代理配置.
- 2
Choose the protocol in 代理协议
Under 代理协议, select HTTP or SOCKS5 to match the connection you intend to use.
- 3
Enter 代理地址 and 端口
Enter the Dashboard host in 代理地址 and the connection port in 端口.
- 4
Add 账号 and 密码
Enter the Dashboard username in 账号 and password in 密码.
- 5
Run 检测代理
Run 检测代理 and confirm that the detected exit region matches the resource you purchased.
- 6
Save with 创建环境 and open the profile
Select 创建环境, then use 启动 to open the configured profile.
Zhanfu Browser validates the proxy while the environment is being created; keep the detected region aligned with the environment you intend to use.
Test the connection and verify the exit
Run 检测代理 in Zhanfu Browser. After it succeeds, open the profile and use an independent IP check to confirm the exit IP and country or region match the purchased resource.
- 检测代理Run 检测代理 and confirm that the detected exit region matches the resource you purchased.
- 启动Select 创建环境, then use 启动 to open the configured profile.
- Verify the exitRun 检测代理 in Zhanfu Browser. After it succeeds, open the profile and use an independent IP check to confirm the exit IP and country or region match the purchased resource.
Troubleshooting
| Symptom | Possible cause | Fix |
|---|---|---|
| 检测代理 fails after the proxy fields are saved | A previous provider, inherited proxy, or Zhanfu Browser-specific profile setting is still active. | If Detect proxy shows an unexpected region, confirm that the credentials belong to the intended GetIPProxy order before creating the environment. |
| Protocol or format error | 代理协议 does not match the HTTP(S) or SOCKS5 endpoint, or the host includes an unwanted protocol prefix. | Select one of HTTP, SOCKS5 and keep 代理地址 and 端口 in separate fields. |
| Authentication failed | The username or password is incomplete, combined into one proxy string, or belongs to an inactive order. | Re-enter the Dashboard values separately in 账号 and 密码, then confirm that the order is active. |
| The profile opens in the wrong region | The saved profile is using different credentials from the endpoint that was tested. | Edit the same profile, run 检测代理 again, save with 创建环境, and compare the detected region with the purchased resource. |
| Connection timeout | A local firewall, VPN, global proxy, or client network rule is intercepting the connection. | Temporarily rule out the conflicting network layer, reopen 代理配置, and repeat 检测代理. |
- 检测代理 fails after the proxy fields are saved
- Possible causeA previous provider, inherited proxy, or Zhanfu Browser-specific profile setting is still active.
- FixIf Detect proxy shows an unexpected region, confirm that the credentials belong to the intended GetIPProxy order before creating the environment.
- Protocol or format error
- Possible cause代理协议 does not match the HTTP(S) or SOCKS5 endpoint, or the host includes an unwanted protocol prefix.
- FixSelect one of HTTP, SOCKS5 and keep 代理地址 and 端口 in separate fields.
- Authentication failed
- Possible causeThe username or password is incomplete, combined into one proxy string, or belongs to an inactive order.
- FixRe-enter the Dashboard values separately in 账号 and 密码, then confirm that the order is active.
- The profile opens in the wrong region
- Possible causeThe saved profile is using different credentials from the endpoint that was tested.
- FixEdit the same profile, run 检测代理 again, save with 创建环境, and compare the detected region with the purchased resource.
- Connection timeout
- Possible causeA local firewall, VPN, global proxy, or client network rule is intercepting the connection.
- FixTemporarily rule out the conflicting network layer, reopen 代理配置, and repeat 检测代理.
What a static residential IP changes
It can help with
- Giving one browser profile a dedicated residential network exit during the purchased term
- Keeping the same assigned IP while the order is active, with renewal support when eligible
- Matching the profile network exit to a purchased country or region
It does not guarantee
- Account approval, account safety, or freedom from platform review or restrictions
- Isolation of cookies, device fingerprints, identity, payment details, permissions, or behavior
- Permission to use a service in ways that violate law or the target platform rules
Check the browser’s current interface
Browser controls and labels can change between versions. Use the available official sources below to confirm the current product and documentation before following this independent setup guide.
- Official website Zhanfu Browser official website
Frequently asked questions
Which proxy protocols can I configure in Zhanfu Browser?
This guide maps HTTP, SOCKS5 in Zhanfu Browser. Select the same protocol as the GetIPProxy connection you are testing.
Where do I enter GetIPProxy credentials in Zhanfu Browser?
Open 新建环境, continue to 代理配置, and map the Dashboard host, port, username, and password to 代理地址, 端口, 账号, and 密码.
Why does 检测代理 fail?
If Detect proxy shows an unexpected region, confirm that the credentials belong to the intended GetIPProxy order before creating the environment. Also confirm that the order is active and that a local VPN, firewall, or global proxy is not replacing the profile connection.
Should I choose HTTP, HTTPS, or SOCKS5 in Zhanfu Browser?
Choose the same protocol as the active GetIPProxy endpoint. If the Dashboard order gives you a SOCKS5 endpoint, select SOCKS5 in Zhanfu Browser; if it gives you an HTTP(S) endpoint, select the matching HTTP or HTTPS option.
What credential format should I use in Zhanfu Browser?
Use the four separate values from Dashboard: host, port, username, and password. If Zhanfu Browser asks for one proxy string, keep the same order as host:port:username:password and do not publish the real credentials in screenshots or tickets.
Can one static residential IP be used for multiple Zhanfu Browser profiles?
A static residential IP can technically be entered in more than one profile, but that also means those profiles share the same network exit. Use a separate dedicated IP when different accounts, stores, clients, or business environments need separate exits.
How do I check that Zhanfu Browser is using the purchased exit?
First run 检测代理 inside Zhanfu Browser. After the test succeeds, open the profile and use an independent IP check page to confirm that the exit IP and country or region match the GetIPProxy resource you purchased.
Does using GetIPProxy in Zhanfu Browser guarantee account safety?
No. A dedicated static residential IP controls the network exit. Browser fingerprints, cookies, identity, payment details, permissions, behavior, and platform decisions remain separate factors.