Hubstudio Proxy Setup with Node4: HTTP, SOCKS5 and Bulk Import

Fill a Hubstudio environment's proxy fields with Node4 values, run its proxy check, and load many environments from the Excel import template.

Before you open Hubstudio, have a Node4 plan and its credential to hand: host, port, username and password are on the Proxies page, and the credential is also under Auth & IP Access. If you have not picked a product yet, choosing the right proxy type matches the job to one; for seller accounts, ad accounts and social profiles in particular, read which Node4 proxy for which job. Hubstudio's interface and help center are in Chinese, so each step below describes the action in English and gives the label as Hubstudio prints it in parentheses. Hubstudio calls a browser profile an environment.

Add a proxy to a new profile

1. Start a new environment (新建环境) and give it a name (环境名称).
2. In the proxy section, choose to enter the proxy yourself (自定义) rather than using no proxy (不使用代理).
3. Set the proxy type (代理类型) to http or socks5. Both work on paid Node4 plans; pick the one whose port you copy in the next step.
4. Fill the proxy host (代理主机) and proxy port (代理端口).
5. Fill the proxy account (代理账号) with your Node4 username and the proxy password (代理密码) with your password.
6. Run the check described in the next section, then finish (完成) to create the environment.

What goes in each field depends on the product:

The free tier is static shared datacenter and HTTP only: select http, because SOCKS5 and the gateways need a paid plan. On the free tier the host and port are always the ones listed on Proxies.

To change the proxy of an environment that already exists, open its proxy information and use the change-proxy action (修改代理); the fields are the same.

Check the proxy before saving

Press the check button under the proxy fields (检测代理). Hubstudio reports whether it could connect through the proxy. Any location it shows for the exit comes from an IP lookup database, and the add-proxy screen lets you switch that source (IP查询渠道) when the result disagrees with what you expect; that is a database disagreement, not a different exit.

Then confirm from inside the environment. Open it, load https://api.ipify.org, and compare the address with the one listed on Proxies for a static proxy. For a gateway there is no fixed address to compare against, so check the country on a lookup page instead. Hubstudio's own detection page, shown when an environment opens, is marked by Hubstudio as for reference only.

One proxy per profile

Give each store, ad or social account its own environment and one IP per account, and keep that pairing. A platform that sees two accounts arrive from the same address has a reason to connect them, whatever the fingerprints say.

Which product keeps the pairing stable matters more here than in scraping. A Dedicated proxy is the same address every time the environment opens, for as long as the plan is paid. A gateway picks its exit per connection, so a bare gateway username can change address between page loads. A session id in the username (USERNAME-session-shop01) holds one exit for up to 30 minutes on Rotating Datacenter and Rotating Unmetered, and up to 30 minutes on residential. When you reopen the environment the next day it leaves from a different address in the same targeted location. Sticky vs rotating sessions covers how the window is measured.

Hubstudio's import template has a usage column that matches this choice: static IP rules (按静态IP规则使用) raise an alert when the environment's address changes, and dynamic IP rules (按动态IP规则使用) do not. Static rules suit a Dedicated proxy; on a gateway the alert would fire on every new exit.

Use IP whitelisting instead of a password

Node4 can authenticate by source address instead of a credential. Register the public address of the computer running Hubstudio under Auth & IP Access, then leave the account and password fields empty. Whitelisting works on every product, with one difference to plan around: a whitelisted residential connection sends no username, so it is untargeted, while the rotating gateways can keep country and session targeting if you put the username in the account field and leave the password empty. IP whitelisting best practices explains the limits.

The address to register is the one your PC reaches the internet from, not the address a profile exits through. Hubstudio's docs mention whitelisting only as something a proxy provider may ask for; there is no Hubstudio setting for it. If your home or office address changes, every environment using the whitelist fails at once until you update the entry.

Import many profiles at once

Hubstudio has two bulk paths, and they take slightly different lines.

Proxies first, then assign them

In the proxy view (代理视角), choose add proxy (添加代理) and then add in bulk (批量添加). Hubstudio takes one proxy per line, up to 100 per batch, in either of two forms:

http://HOST:PORT:USERNAME:PASSWORD
http://USERNAME:PASSWORD@HOST:PORT

Always write the scheme. Hubstudio treats a line with no type as SOCKS5, so a bare line pointed at an HTTP port, or any line on the free tier, fails the check. For SOCKS5 lines write socks5:// and use the SOCKS5 port.

Environments from the template

In the environment list (环境), open bulk import (批量导入), download the environment import template (环境导入模板), fill one environment per row, and upload it (批量上传). The required columns are the environment name (环境名称), the proxy type (代理类型) and the usage (使用方式); the proxy goes in the proxy parameters column (代理参数) as host:port:user:pass with plain ASCII colons, and the type column carries http or socks5. Then continue and start the import (开始导入). Hubstudio limits importing to its boss, admin and manager roles.

Where the Node4 lines come from: for static proxies, use Export on Proxies as TXT with Port and Username & Password ticked (credentials are left out unless you tick it). Leave Protocol Prefix off for the template's proxy parameters column, and tick it for the bulk-add path above, which needs the scheme. Exported static lines carry the HTTP port, so set the type to http, or replace the port with the SOCKS5 port shown on that proxy's row if you choose socks5. For a gateway, open Connect, then Generate proxy list, leave Type on sticky (the default), choose the line format and generate: you get one pinned exit per line, and the URL format already matches the second form above.

Hubstudio's bulk parser splits on : and @, and its notes say a field containing either character breaks the line. A Node4 password with one of them must be entered one at a time with the single-add form (单个添加) instead. The same characters cause a 407 when they are not encoded in other tools.

When the check fails

A 407, or the credential is rejected

The usual causes are a gateway host paired with a product your account does not hold, a stray space pasted into the account field, a misspelled targeting key such as -contry-us, or a whitelisted setup where the PC's address has changed. Fixing 407 errors walks through each one.

The check times out or cannot connect

Most often the type and the port disagree: socks5 selected with an HTTP port, or a bulk line with no scheme that Hubstudio read as SOCKS5. A free-tier proxy set to socks5 times out the same way. If type and port match, test from another network to rule out a local firewall, then follow connection issues.

The wrong country

A misspelled targeting key is refused with a 407 rather than ignored, so a wrong country with no error usually means the account field has no country segment, or the environment uses the whitelist with no username. Remember that the reported location depends on the lookup source; switch it before deciding the exit is wrong. Node4's X-Node4-Country header is present only on plain-HTTP responses and on refusals; an HTTPS tunnel or a SOCKS5 connection carries none, so inside an environment you will rarely see it. Residential sends it only on a refused country. Verify the exit with a lookup page as in country and city targeting.

For prices and plan sizes, see pricing. Hubstudio is one of three anti-detect browsers with a Node4 walkthrough; the others are AdsPower and BitBrowser.