Windows · SOCKS5 and HTTP · 4 steps
NekoBox Proxy Setup (Windows): Manual Input of a Socks or HTTP Node
NekoBox on Windows adds a node through Manual Input. Set the type to Socks (version 5) or HTTP, type the gateway host in address and the port in port, fill the username and password in the authentication section and click OK. Start the node and switch on the system proxy to route Windows.
Set up the proxy in NekoBox (Windows)
Open NekoBox (Windows), follow the 4 moves below and finish with the tool's own check. The values are in the table after the steps.
-
01
Open Manual Input
Launch NekoBox, right-click an empty area of the server list and choose Manual Input from the menu.
NekoBox main window with the right-click menu and the Manual Input entry. -
02
Enter the proxy details
In the Edit dialog set Type to Socks and Version to 5 for the SOCKS5 port, or Type to HTTP for the HTTP port. Type the gateway host in Address and the port in Port, then the username and password in the authentication fields. Click OK.
NekoBox Edit dialog with Type, Name, Address, Port, Version, Username and Password framed in red. -
03
Confirm the node
The node appears in the server list with its type, address and name.
NekoBox server list showing the newly added Socks node. -
04
Start the node and enable the system proxy
Select the node and click the start button, then tick System Proxy in the toolbar (Tun mode for apps that ignore it). Open an IP lookup page in a browser to confirm the exit IP.
NekoBox with the node started and the system proxy enabled.
Check it
The URL test on the node row, then an IP lookup page in a browser after System Proxy is on.
Routing rules in NekoBox can send only chosen apps or domains through the node; by default everything uses it once the system proxy is on.
What to type: ports and the username
Copy the line from the dashboard (Proxies, your plan, the generator) rather than typing it: it already carries the host, the country, the session id and the session length. The table shows what each field holds.
| Plan | Copy it from | HTTP port | SOCKS5 port | Username shape |
|---|---|---|---|---|
| Residential Premium | the generator | 8080 | 1080 | USER-country-us-sid-k3f9a1b2-ttl-30m |
| Mobile | the generator | 8080 | 1080 | USER-country-us-type-mobile-sid-a1b2c3-ttl-30m |
| Residential Basic | the generator | in the line | in the line | USER-country-us plus a session for sticky |
| Datacenter (per GB) | the generator | 9999 | 10000 | the line's username |
| IPv6 | the generator | 1001 | in the line | the line's username |
| ISP (dedicated IP) | the plan page, one line per IP | in the line | in the line | the line's own login |
The host and the password are in the same line. Pick HTTP or SOCKS5 in the tool and use the port of that column; a port from the other column is the most common reason a check fails. On Premium ISP city plans one port serves both types. USER and the session id stand for your own values.
Where the line comes from in the dashboard
Step 3: the number of IPs, the price for 30 days and the Buy button. One IP is one antidetect profile.
After payment the plan is in My proxies: each IP comes as IP:Port:Username:Password, HTTP or SOCKS5, ready to paste into the tool.
The plan page has the generator: country, pool, Sticky session with its TTL, HTTP or SOCKS5, then one line per profile in host:port:user:pass.
The whole buying flow, both routes and the prices are on the integrations page.
NekoBox (Windows) proxy questions
What customers ask when they put a QuanticData line into NekoBox (Windows).
Something else? Ask usSocks or HTTP in NekoBox?
Socks with Version 5 and the SOCKS5 port, or HTTP with the HTTP port. The address and login are the same for both.
NekoBox connects but sites do not load. Why?
The type and port probably disagree, or the username and password are empty: NekoBox marks them optional, our gateways need them.
Is NekoBox the same as NekoRay?
NekoBox is the current name of the NekoRay project on Windows. The Android app with the same name has its own guide on this site.
Which QuanticData plan works best in NekoBox (Windows)?
For a whole device, a sticky residential or mobile line keeps one exit for up to 24 hours; a dedicated ISP IP never changes and has unlimited traffic, from $2.69 per IP for 30 days. NekoBox (Windows) takes either as a plain SOCKS5 or HTTP server.
Set up NekoBox (Windows) in five minutes
Create an account, buy one ISP IP or a gigabyte pack, copy the line and paste it into the fields above. ISP from $2.69 per IP for 30 days, mobile from $5 for 1 GB.
Balance, crypto, card or PayPal · no VAT from the balance or crypto