How to Add and Check a Proxy in BitBrowser
By the ProxyV4 Engineering Team · Updated:
To set up a proxy in BitBrowser, open a browser profile, go to its proxy section, choose the protocol, enter the host, port, username and password, and run the built-in proxy check before you save. Each profile keeps its own proxy, so a team can give every client or project its own IP. The steps below use generic labels, because BitBrowser renames menus between versions.
BitBrowser proxy setup inside a profile
BitBrowser stores the proxy as part of each browser profile. You set it when you create a profile, or later from the profile's edit screen. Look for the proxy section in the profile form (labels vary by version); it holds a protocol dropdown, host, port, username and password fields, and a check button.
Each profile also keeps its own cookies and logins, so pairing one profile with one proxy keeps a client's sessions and IP together and away from the others.
Match the protocol to your order's mode
The dropdown typically lists HTTP, HTTPS and SOCKS5, and some versions list more. Pick the protocol your proxy is set to serve. ProxyV4 orders run in HTTP only, SOCKS5 only, or both on the same port, chosen on the order's page in the dashboard. If the order is in both mode, either choice works; the HTTP vs SOCKS5 comparison explains the practical differences.
A mismatch is the most common reason a correct-looking proxy fails: a SOCKS5 handshake sent to an HTTP-only port, or the reverse, simply stalls.
Paste the line or fill the fields
ProxyV4 delivers each proxy as one ip:port:user:pass line, for example 203.0.113.10:PORT:USER:PASS. Some BitBrowser versions offer a paste box that splits a line into the four fields; if yours does not, type the parts into each field. Watch for a trailing space copied from a spreadsheet, which turns a correct password into a wrong one.
BitBrowser SOCKS5 with a username and password
BitBrowser passes the credentials itself when it opens the connection, so an authenticated SOCKS5 proxy works without an extension or a separate tunnel. That matters because plain Chrome's command-line proxy flag has no place for a login.
Choose SOCKS5 in the dropdown, enter the same four values, and run the check. If the check passes over HTTP but not SOCKS5 for the same proxy, the order is probably in HTTP-only mode. Switching the mode in the dashboard can move the proxy to a new port, so copy the line again after you change it.
If a workflow depends on UDP, do not assume SOCKS5 in a browser profile carries it. Ask ProxyV4 support through a ticket before you order.
Running the BitBrowser proxy check
The check button sends a test request from the BitBrowser app on your computer, through the proxy, to an IP lookup service, then shows the exit IP and the location that service reports. It tests the proxy and your credentials, not the website you plan to use.
Reading a failed check
- Authentication error or 407: the username or password is wrong, often because of a stray space. Copy the line again from the dashboard.
- Timeout or connection failure: the protocol does not match the order's mode, the port changed, or a local firewall or antivirus blocks BitBrowser. The proxy timeout guide walks through the order to check things in.
- Check fails but the profile browses normally: the lookup service the check uses can be slow or unreachable on its own. Several proxy vendors report this case, so confirm inside the open window before you change anything.
Location looks wrong
Lookup services use different geolocation databases, so two of them can disagree about the city or even the country of a new IP. Compare a second source before you conclude the proxy is wrong.
Adding proxies to many profiles at once
For more than a handful of profiles, BitBrowser offers batch creation or import from a template file in recent versions. The template has columns for profile details and for the proxy's protocol, host, port, username and password. Download the template from your own version of the app rather than reusing an old one, because column names change.
Put one proxy per row and keep the protocol column consistent with each order's mode. Before importing, test the lines with the free proxy checker so a dead or mistyped line does not end up attached to a profile. Keep a sheet that maps profile names to IPs, which makes later edits and renewals easy to track.
Matching ProxyV4 proxies to BitBrowser profile groups
Agencies, store operators and teams use BitBrowser to keep client accounts, business units and staff workspaces separate. A fixed IP per profile helps with that: logins come from the same address each time, and a teammate can tell which IP belongs to which client. The multi-account management use case covers how to organize those groups. Follow each platform's rules on how many accounts you may run and how they may interact.
ProxyV4 sells private datacenter IPv4 in seven countries (United States, Vietnam, Japan, South Korea, Singapore, United Kingdom, Hong Kong) and static ISP IPs registered to consumer internet providers in the United States and Vietnam. Each IP has one tenant for the whole term, traffic is unmetered, and renewing before expiry keeps the same address. Every proxy supports HTTP(S) and SOCKS5 with username and password.
It is not the right product if you need a new IP on every request (rotating proxies are waitlist-only), mobile carrier IPs, or IPv6, which is sold separately as IPv6 proxies. See live per-IP rates on the pricing page, order one IP, and test it in a real profile before buying more.
Verify the exit IP in an open profile
Save the profile, open it, and load the my IP tool in a tab. The address shown should be the proxy's, with the expected country. If you see your own IP, the profile was opened without its proxy saved, or the profile is set to no proxy.
Set the profile's language and time zone to the market you work in, so the sites your team uses show the right currency and local content. Then sign in and work as usual.
Step by step
- 1
Open the profile form
Create a new profile or edit an existing one and find its proxy section.
- 2
Choose the protocol
Select HTTP or SOCKS5 to match the mode set on the order's page.
- 3
Enter the proxy line
Fill in the host, port, username and password from the ip:port:user:pass line, or paste it if your version splits it.
- 4
Run the check
Click the check button and confirm the reported IP and location.
- 5
Open and verify
Save, open the profile and confirm the exit IP in the my IP tool.
Frequently asked questions
Does BitBrowser support SOCKS5 proxies with a password?
Yes. Choose SOCKS5 in the profile's proxy section and enter the username and password; BitBrowser handles the login itself.
Why does the BitBrowser proxy check fail when the proxy works?
The check depends on an outside lookup service, which can time out on its own. If the open profile shows the proxy's IP in a my-IP page, the proxy is working.
Can I use both HTTP and SOCKS5 with one ProxyV4 proxy?
Yes. Set the order to both modes on the order's page and the same port accepts either protocol.
Will my BitBrowser profiles keep their IPs after renewal?
Yes. Renewing before expiry keeps the same IP, and you can renew all proxies or a selection.
Is bandwidth charged for BitBrowser traffic?
No. Traffic on ProxyV4 private IPv4 and static ISP proxies is unmetered; you pay per IP per month.
Static IPs for BitBrowser window groups
Private IPv4 and static ISP proxies with HTTP(S) and SOCKS5 on username and password login, unmetered traffic and the same IP on renewal. Start with one IP.
See live prices