Set Up Scrapingbypass Proxy in Hubstudio | Scrapingbypass Proxy Tutorial

Configure a Scrapingbypass proxy in a Hubstudio browser environment. This guide covers the custom proxy method, dynamic-IP usage rule and the authentication fields needed to check the connection.

1. Generate your proxy connection details

Sign in to the Scrapingbypass console and select a residential or datacenter proxy plan. For the full extraction workflow, see the residential proxy guide or datacenter proxy guide.

Proxy network: choose residential or datacenter proxies to suit your workload. Residential proxies use residential exit IPs; datacenter proxies are an option for bandwidth-intensive browsing and data collection. Test the destination before committing to a workflow.
Location: select the country, region or city your task requires.
Protocol: Choose HTTP or SOCKS5; use the protocol supported by your application. The protocol selected in the application must match the connection details you generate.
Gateway: use the generated domain gateway by default. If your console offers an IP gateway and you need it for troubleshooting, use the gateway supplied for that plan.
Output format: select ip:port:username:password so you can identify the four fields. Do not confuse it with username:password@ip:port.
Session duration: choose the available duration that fits your task. A longer session is not a permanent static IP.
Separator and quantity: keep the default separator unless your import method requires another one. Set the quantity after choosing a session duration, then click Extract proxies.

Proxy extraction format menu with the host, port, username and password format available — Select ip:port:username:password from the format list; the highlighted row in the illustration is a different format. Configuration illustration with placeholder credentials; this is not a live connection test.

2. Check the host, port and authentication fields

Copy the values from your own extraction result. Quick copy is useful for one proxy; batch extraction provides multiple entries. The following values are placeholders, not working credentials:

gw.cloudbypass.com:1288:YOUR_PROXY_USERNAME:YOUR_PROXY_PASSWORD

Host / server address: gw.cloudbypass.com in this datacenter example. Use the actual host returned by your console; residential plans may return a different gateway, such as gw-res.cloudbypass.com.
Port: 1288 in this example; use the port in your result.
Username: your generated proxy username, including any location or session parameters it contains.
Password: the generated proxy password, not your console sign-in password.

Proxy extraction result showing separate host, port and authentication fields and batch copy — Use the fields from your own result; the illustrated account values have been replaced with placeholders. Configuration illustration with placeholder credentials; this is not a live connection test.

3. Configure the proxy in Hubstudio

Create a new Hubstudio environment or edit an existing browser environment.
In the proxy section, select Custom and choose HTTP or SOCKS5 to match your generated proxy.
Set the usage method to Use dynamic IP rules for this rotating-proxy setup.
Fill in the proxy host, port, username and password using the extraction result.
Click Check proxy and review the connection result. Do not treat a successful proxy check as a guarantee that every destination will accept the session.
Click Done, start the browser environment and verify its exit IP.

Hubstudio proxy settings with gateway, port and placeholder authentication fields — The Hubstudio configuration shown here illustrates where to enter your proxy details. Field names may vary by version. Configuration illustration with placeholder credentials; this is not a live connection test.

Verify the connection and troubleshoot

Save the configuration and start the application or browser profile. Check the public exit IP from inside that profile or the app that should use the proxy, then open your intended destination.
If authentication fails, re-copy the generated proxy username and password without spaces. Keep the entire username, including its session and location parameters.
If the connection times out, check the host, port, protocol, proxy balance and any required upstream route. Test the phone, emulator and desktop environment separately.
A VPN icon, a changed extension icon or a successful proxy check confirms only part of the connection. It does not guarantee that every website will accept the session or that a later request will succeed.
Keep credentials private. When requesting support, share the application version, protocol and a redacted error message, not your proxy password.