# sing-box SOCKS5 and HTTP Outbound with Auth

> A minimal sing-box config.json with an authenticated SOCKS5 or HTTP outbound to a QuanticData line, the check command and the exit IP test. Tested on 1.14.4.

[Home](https://quanticdata.io/) / [Integrations](https://quanticdata.io/integrations/) / sing-box

Windows, macOS, Linux · SOCKS5 and HTTP · 5 steps

# sing-box SOCKS5 Config: An Authenticated Outbound in a Minimal config.json

A sing-box config for an authenticated proxy needs one inbound and one outbound: a mixed inbound on 127.0.0.1:2080 for your programs, and a socks or http outbound with server, server_port, username and password. Check it with sing-box check, start it with sing-box run and send a request through 127.0.0.1:2080. Tested in sing-box 1.14.4.

[Create an account](https://app.quanticdata.io/register?utm_source=integrations-sing-box&utm_medium=ai-twin&utm_campaign=site&utm_content=integrations-sing-box-hero) · [Jump to the steps](https://quanticdata.io/integrations/sing-box/#steps)

By [Aldo Morese](https://quanticdata.io/about/), founder of QuanticData · Published Nov 20, 2026

## Where the proxy goes in sing-box

config.json → outbounds → type socks or http

- **Proxy type**: "type": "socks" or "http"
- **Host**: "server"
- **Port**: "server_port"
- **Username**: "username"
- **Password**: "password"

Split the generator line host:port:user:pass into the four outbound fields. JSON needs the username and password in double quotes.

## Set up the proxy in sing-box

Open sing-box, follow the 5 moves below and finish with the tool's own check. The values are in the table after the steps.

1. 01

   ### Write config.json

   Download the sing-box release for your system from the project's GitHub releases page and unzip it; on Windows the zip holds sing-box.exe and libcronet.dll, which we placed in C:\sing-box. Next to it, save the file below as config.json with your own server, port, username and password. There is no route block: with one outbound, sing-box sends all traffic to it.

   ```json
   {
     "log": { "level": "info", "timestamp": true },
     "inbounds": [
       { "type": "mixed", "tag": "local-in", "listen": "127.0.0.1", "listen_port": 2080 }
     ],
     "outbounds": [
       {
         "type": "socks",
         "tag": "quanticdata",
         "server": "residentialpremium.quanticdata.io",
         "server_port": 1080,
         "username": "USER-country-us-sid-k3f9a1b2-ttl-60m",
         "password": "PASS"
       }
     ]
   }
   ```

   ![Windows terminal in C:\sing-box: sing-box version 1.14.4, the config.json with a mixed inbound on 127.0.0.1:2080 and a socks outbound to residentialpremium.quanticdata.io port 1080 framed, and sing-box check passing](https://quanticdata.io/integrations/img/sing-box/sing-box-config-check.webp?v=20261120b)
2. 02

   ### Check the file

   Run .\sing-box.exe check -c .\config.json. It prints nothing and exits with code 0 when the file is valid. A missing comma stops it with FATAL and the row and column, and a misspelt field with its path, for example outbounds[0].user: json: unknown field "user". The check reads the file only: it does not contact the gateway, so a wrong password still passes here.
3. 03

   ### Start sing-box

   Run .\sing-box.exe run -c .\config.json (add --disable-color in the classic Windows console). The log shows tcp server started at 127.0.0.1:2080 and sing-box started. Leave the window open: closing it stops the proxy.

   ![sing-box run log on Windows: tcp server started at 127.0.0.1:2080, then inbound connections from 127.0.0.1 and two framed lines outbound/socks\[quanticdata\]: outbound connection to ipinfo.io:443 and api.ipify.org:443](https://quanticdata.io/integrations/img/sing-box/sing-box-run-log.webp?v=20261120b)
4. 04

   ### Send a request through it and read the exit IP

   In a second window run curl.exe -s -x http://127.0.0.1:2080 https://ipinfo.io/json. The mixed inbound speaks HTTP and SOCKS5 on the same port, so socks5h://127.0.0.1:2080 works too. Our residential SOCKS5 line answered with a home fibre address in Nebraska, and each request appeared in the sing-box log as outbound/socks[quanticdata].

   ![curl through the sing-box mixed inbound on 127.0.0.1:2080: ipinfo.io returns a United States residential IP in Alliance, Nebraska, and api.ipify.org through socks5h returns the same address, both framed](https://quanticdata.io/integrations/img/sing-box/sing-box-exit-ip-residential.webp?v=20261120b)
5. 05

   ### Switch to an HTTP outbound for a mobile line

   For the HTTP port, change "type" to "http" and use the HTTP port of the plan; nothing else in the outbound changes. Our second file pointed at mobile.quanticdata.io on 8080 with a mobile username, and the same curl returned a T-Mobile USA address in Connecticut.

   ![config-mobile.json with an http outbound to mobile.quanticdata.io port 8080 and a placeholder mobile username, and curl through 127.0.0.1:2080 returning a T-Mobile USA exit IP in Bloomfield, Connecticut](https://quanticdata.io/integrations/img/sing-box/sing-box-exit-ip-mobile.webp?v=20261120b)

### Check it

curl.exe -s -x http://127.0.0.1:2080 https://ipinfo.io/json while sing-box runs. The ip and org fields must be the exit of your line; the sing-box log shows each request as outbound/socks[quanticdata] or outbound/http[quanticdata].

Point any program at 127.0.0.1:2080 as an HTTP or SOCKS5 proxy, with no login: sing-box adds the QuanticData login on the way out. sing-box 1.14.4 for Windows is shown; the same config.json runs on macOS and Linux.

## sing-box HTTP outbound: the same fields

The http outbound takes the same server, server_port, username and password as the socks outbound. Only the type and the port change, as below. We ran both types on Residential Premium and on Mobile, and a socks outbound on Residential Basic with the host and port of its own line: all five configurations passed the check and returned the expected country.

```json
{
  "type": "http",
  "tag": "quanticdata",
  "server": "mobile.quanticdata.io",
  "server_port": 8080,
  "username": "USER-country-us-type-mobile-sid-k3f9a1b2-ttl-60m",
  "password": "PASS"
}
```

## Which QuanticData line to use in sing-box

- Mobile: carrier IPs, T-Mobile USA and Telefonica Germany in our runs, for traffic that should look like a phone. One sticky session per outbound.
- Residential Premium: home IPs by country, sessions up to 24 hours set by ttl in the username. Our 60 minute session kept the same address across sing-box, Karing and Hiddify.
- Residential Basic: home IPs with the host and ports printed in the line; the plan also accepts IP whitelisting, in which case the outbound needs no username and password.
- ISP: one dedicated IP for a server or a long-running job that must keep its address.

## sing-box proxy errors and what they mean

We ran the same files with a wrong password to see what sing-box prints. Both cases show in the run window, not in the check.

- socks5: incorrect user name or password: a socks outbound reached the gateway with a wrong login. Copy the username and password again from the generator.
- authentication required: the same mistake on an http outbound.
- EOF after about 15 seconds: a socks outbound pointed at the HTTP port 8080. Use 1080 for socks.
- malformed HTTP response: an http outbound pointed at the SOCKS5 port 1080. Use 8080 for http.
- The client gets no answer and the log shows nothing: the program is not using 127.0.0.1:2080, or sing-box is not running.
- The country is not the one you wanted: the country is part of the username (country-us). Generate a new line with the right country rather than editing the string.
- Still failing: log in and ask Quantic AI in the dashboard. It tests your line from our side with your own login and tells you what the gateway answered.

## 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

- [![QuanticData Buy proxies page, Residential tab: Residential Premium packs from $4.00 for 1 GB to 25 GB for $70.00 with the price per GB of each](https://quanticdata.io/integrations/img/buy/residential-plans.webp?v=20261030a)](https://quanticdata.io/integrations/img/buy/residential-plans.webp?v=20261030a)

  *Residential and Mobile are bought by the gigabyte: Residential Premium from $4 for 1 GB down to $2.20 per GB at 500 GB.*
- [![QuanticData Buy proxies page, Mobile tab: packs from $5.00 for 1 GB to $1,150 for 500 GB, all valid 90 days, HTTP and SOCKS5](https://quanticdata.io/integrations/img/buy/mobile-plans.webp?v=20261030a)](https://quanticdata.io/integrations/img/buy/mobile-plans.webp?v=20261030a)

  *Mobile: $5 for 1 GB, valid 90 days, down to $2.30 per GB at 500 GB.*
- [![QuanticData residential plan generator with country United States, Max pool, Sticky session of 30 minutes, HTTP, 10 sessions and the host:port:user:pass output format](https://quanticdata.io/integrations/img/buy/generator.webp?v=20261030a)](https://quanticdata.io/integrations/img/buy/generator.webp?v=20261030a)

  *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](https://quanticdata.io/integrations/#buy).

## sing-box proxy questions

What customers ask when they put a QuanticData line into sing-box.

[Something else? Ask us](https://quanticdata.io/integrations/sing-box/#ask)

### How do I configure a SOCKS5 proxy with a username and password in sing-box?

Add an outbound with "type": "socks", the gateway host in server, the port in server_port, and your login in username and password. Version can be left out: SOCKS5 is the default. A mixed inbound on 127.0.0.1:2080 then gives your programs a local proxy without a login.

### Does sing-box support HTTP proxies with authentication?

Yes, as an outbound with "type": "http" and the same server, server_port, username and password fields. We tested it on the QuanticData mobile gateway, port 8080, and the exit was a T-Mobile USA address.

### What is a mixed inbound in sing-box?

A local listener that accepts both HTTP and SOCKS5 on one port. In our config it listens on 127.0.0.1:2080; curl through http:// and through socks5h:// on that port both reached the same exit.

### Does sing-box check test the proxy login?

No. sing-box check validates the file only. A wrong password shows when traffic flows, in the run log, as incorrect user name or password for socks or authentication required for http.

### Can I use the same QuanticData line in Karing or Hiddify?

Yes. Both run a sing-box core. In our tests the same residential session gave the same exit IP in sing-box, Karing and Hiddify.

## More setup guides

- [Clash Verge proxy setup](https://quanticdata.io/integrations/clash-verge/)
- [v2rayN proxy setup](https://quanticdata.io/integrations/v2rayn/)
- [NekoBox (Windows) proxy setup](https://quanticdata.io/integrations/nekobox/)
- [Proxifier proxy setup](https://quanticdata.io/blog/proxifier-proxy-setup/)
- [Karing proxy setup: SOCKS5 or HTTP with a login](https://quanticdata.io/integrations/karing/)
- [Hiddify proxy setup: add a SOCKS5 proxy](https://quanticdata.io/integrations/hiddify/)
- [Proxy location checker: see the exit country](https://quanticdata.io/tools/proxy-location-checker/)
- [All 61 proxy integrations](https://quanticdata.io/integrations/)
- [ISP proxies: one dedicated IP per profile](https://quanticdata.io/isp-proxies/)
- [Mobile proxies on carrier IPs](https://quanticdata.io/mobile-proxies/)
- [Residential proxies with sticky sessions](https://quanticdata.io/residential-proxies/)

sing-box is a third-party product; the menus and labels on this page are the ones sing-box 1.14.4 showed on Windows 11 on 20 Nov 2026. The screenshots are ours, with the username and password replaced by placeholders.

## Give sing-box a home or mobile exit

Create an account, take the free 100 MB residential trial or a mobile pack, generate one sticky line and put it in the outbound.

[Create an account](https://app.quanticdata.io/register?utm_source=integrations-sing-box&utm_medium=ai-twin&utm_campaign=site&utm_content=integrations-sing-box-closing) · [See the prices](https://quanticdata.io/residential-proxies/volume-pricing/)

Balance, crypto, card or PayPal · no VAT from the balance or crypto

---

Source: https://quanticdata.io/integrations/sing-box/ · Site index for AI: https://quanticdata.io/llms.txt
