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 | 代理 IP | 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代理 IP- 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 FireBrowser
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 自有设备 IP 权限
Open 自有设备 IP 权限 in FireBrowser and continue to 店铺配置 > 代理设置.
- 2
Choose the protocol in 代理类型
Under 代理类型, select HTTP or SOCKS5 to match the connection you intend to use.
- 3
Enter 代理 IP and 代理端口
Enter the Dashboard host in 代理 IP 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.
FireBrowser includes a self-owned device IP permission step before store proxy configuration; complete that prerequisite first.
Test the connection and verify the exit
Run 检测代理 in FireBrowser. 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 FireBrowser. 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 FireBrowser-specific profile setting is still active. | If FireBrowser does not allow editing the proxy fields, verify the self-owned device IP permission before checking the store configuration again. |
| 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 代理 IP 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 FireBrowser-specific profile setting is still active.
- FixIf FireBrowser does not allow editing the proxy fields, verify the self-owned device IP permission before checking the store configuration again.
- 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 代理 IP 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 FireBrowser official website
Frequently asked questions
Which proxy protocols can I configure in FireBrowser?
This guide maps HTTP, SOCKS5 in FireBrowser. Select the same protocol as the GetIPProxy connection you are testing.
Where do I enter GetIPProxy credentials in FireBrowser?
Open 自有设备 IP 权限, continue to 店铺配置 > 代理设置, and map the Dashboard host, port, username, and password to 代理 IP, 代理端口, 代理账号, and 代理密码.
Why does 检测代理 fail?
If FireBrowser does not allow editing the proxy fields, verify the self-owned device IP permission before checking the store configuration again. 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 FireBrowser?
Choose the same protocol as the active GetIPProxy endpoint. If the Dashboard order gives you a SOCKS5 endpoint, select SOCKS5 in FireBrowser; if it gives you an HTTP(S) endpoint, select the matching HTTP or HTTPS option.
What credential format should I use in FireBrowser?
Use the four separate values from Dashboard: host, port, username, and password. If FireBrowser 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 FireBrowser 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 FireBrowser is using the purchased exit?
First run 检测代理 inside FireBrowser. 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 FireBrowser 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.