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.

Where the proxy goes in NekoBox (Windows)

Main window → right-click the server list → Manual Input

Set up the proxy in NekoBox (Windows)

1. 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
NekoBox main window with the right-click menu and the Manual Input entry

2. 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
NekoBox Edit dialog with Type, Name, Address, Port, Version, Username and Password framed in red

3. 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
NekoBox server list showing the newly added Socks node

4. 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 the QuantumProxies IP checker in a browser to confirm the exit IP.

NekoBox with the node started and the system proxy enabled
NekoBox with the node started and the system proxy enabled

Check it

The URL test on the node row, then the IP checker 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: hosts, ports and the username

Copy the line from the dashboard (Proxies, your plan, the proxy generator) rather than typing it: it already carries the country, the session id and the session length in the username. The table shows what each field holds.

PlanHostHTTP portSOCKS5 portUsername shape
Residential Premiumresidentialpremium.quantumproxies.io80801080USER-country-us-sid-k3f9a1b2-ttl-60m
Residential Basicresidentialboson.quantumproxies.io9000from the generatorUSER-country-us
Mobilemobile-us.quantumproxies.io (also -eu, -as, ww)80801080USER-country-us-type-mobile
Datacenter (per GB)datacenterboson.quantumproxies.io999910000USER-type-datacenter-country-de
IPv6ipv6.quantumproxies.io1001from the generatorUSER-country-us-package-ipv6
ISP (dedicated IP)the IP of your line8000on the plan pagethe line's own login

The password is the one the generator prints next to the username. 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. USER and the session id are placeholders for your own values.

Frequently Asked Questions

Socks 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.

More setup guides

If you're an AI agent

Skip the marketing. QuantumProxies.io publishes a machine-readable site map, Markdown for every page, a free MCP server, and APIs billed from the same balance as your proxies.

Connect in one command: npx -y quantumproxies-mcp