Documentation Python quickstart Blog Free tools Enterprise solutions hello@quanticdata.ioLog in

Linux, Docker · SOCKS5 and HTTP · 9 steps

3X-UI Outbound Setup: Route an Inbound Through a SOCKS5 or HTTP Proxy

In 3X-UI a proxy with a login is an outbound. Open Outbounds, click + Outbounds, choose socks or http and fill Tag, Address, Port, Username and Password, then Create and Save. In Routing, add a rule with the inbound in Inbound tags and your new tag in Outbound tag, and save again. The Check button and the Route Tester confirm it inside the panel. Tested in 3X-UI 3.11.0.

Set up the proxy in 3X-UI

Open 3X-UI, follow the 9 moves below and finish with the tool's own check. The values are in the table after the steps.

  1. 01

    Open Outbounds and click + Outbounds

    We ran the panel from the image the project names in its README, ghcr.io/mhsanaei/3x-ui, tag v3.11.0, built from github.com/MHSanaei/3x-ui. Log in to the panel and open Outbounds in the side menu. A new install lists two outbounds, direct and blocked. Click the blue + Outbounds button above the table.

    3X-UI 3.11.0 Outbounds page with the default direct and blocked outbounds and the blue plus Outbounds button framed, next to Subscriptions, more and the TCP, HTTP and Real delay test switch
    3X-UI 3.11.0 Outbounds page with the default direct and blocked outbounds and the blue plus Outbounds button framed, next to Subscriptions, more and the TCP, HTTP and Real delay test switch.
  2. 02

    Choose socks and fill the form

    The form opens on vless. Open Protocol and scroll to the end of the list, where socks and http come after hysteria and masque. With socks the form shrinks to Tag, Address, Port, Username and Password, and Port is preset to 1080. Type a tag you will recognise, quanticdata-us in our run, the gateway host in Address, then the username and password exactly as the generator printed them. Send Through and Target Strategy stay empty, Sockopts and Mux off.

    3X-UI plus Outbounds form with Protocol socks framed, Tag quanticdata-us, and Address residentialpremium.quanticdata.io, Port 1080, Username and Password framed with placeholders in place of the real login
    3X-UI plus Outbounds form with Protocol socks framed, Tag quanticdata-us, and Address residentialpremium.quanticdata.io, Port 1080, Username and Password framed with placeholders in place of the real login.
  3. 03

    Create, then Save

    Click Create at the bottom of the form: the outbound joins the table with its protocol under the tag and host:port in the Address column. Then click Save at the top of the page, which the panel confirms with The parameters have been changed. In our run the outbound was usable straight after Save.

  4. 04

    Add an http outbound the same way

    For the HTTP port of a plan choose http in Protocol. The fields are the same, Port is preset to 8080, and a Headers row appears, which stays empty. Our second outbound was quanticdata-mobile on mobile.quanticdata.io, port 8080, with a mobile username.

    3X-UI plus Outbounds form with Protocol http framed, Tag quanticdata-mobile, and Address mobile.quanticdata.io, Port 8080, Username and Password framed with placeholders, above the Headers row with its Add button
    3X-UI plus Outbounds form with Protocol http framed, Tag quanticdata-mobile, and Address mobile.quanticdata.io, Port 8080, Username and Password framed with placeholders, above the Headers row with its Add button.
  5. 05

    Check the outbound from the panel

    Above the table, switch the test mode from TCP to HTTP, then click the round Check button at the end of the outbound's row. The panel sends a request through the outbound and fills the row: the egress address (hidden here), the country, United States for our line, and the latency, 204 ms in our run.

    3X-UI Outbounds table after the HTTP check on quanticdata-us, row framed: socks, residentialpremium.quanticdata.io:1080, the egress address hidden, country United States, latency 204 ms and the Check (HTTP) tooltip
    3X-UI Outbounds table after the HTTP check on quanticdata-us, row framed: socks, residentialpremium.quanticdata.io:1080, the egress address hidden, country United States, latency 204 ms and the Check (HTTP) tooltip.
  6. 06

    Add a routing rule for the inbound

    Open Routing, then the Routing Rules tab, and click + Routing Rules. Scroll to the end of the form: open Inbound tags and pick the inbound whose traffic should leave through the proxy, then pick your tag in Outbound tag. The inbounds are listed by tag with their remark in brackets, in-10811-tcp (local-test) for our test inbound. Everything above can stay empty; we typed a Comment to recognise the rule.

    3X-UI routing rule form scrolled to the end: Inbound tags set to in-10811-tcp (local-test) and Outbound tag set to quanticdata-us, both framed, above Balancer tag and the Close and Create buttons
    3X-UI routing rule form scrolled to the end: Inbound tags set to in-10811-tcp (local-test) and Outbound tag set to quanticdata-us, both framed, above Balancer tag and the Close and Create buttons.
  7. 07

    Create the rule and Save

    Click Create, then Save at the top. The rule is added under the three rules of a new install, api, geoip:private and bittorrent, with the inbound tag in the Inbounds column and your outbound in the Outbounds column.

    3X-UI Routing Rules table after saving, with the confirmation The parameters have been changed and rule 4 framed: comment local-test to QuanticData, inbound tag in-10811-tcp (local-test), outbound quanticdata-us
    3X-UI Routing Rules table after saving, with the confirmation The parameters have been changed and rule 4 framed: comment local-test to QuanticData, inbound tag in-10811-tcp (local-test), outbound quanticdata-us.
  8. 08

    Ask the Route Tester

    The third tab, Route Tester, asks the running Xray which outbound would handle a connection, without sending traffic. Type a domain, pick the inbound and click Test Route. Ours answered Matched outbound: quanticdata-us.

    3X-UI Route Tester with ipinfo.io, port 443, TCP and the inbound in-10811-tcp selected, and the green answer Matched outbound: quanticdata-us, framed
    3X-UI Route Tester with ipinfo.io, port 443, TCP and the inbound in-10811-tcp selected, and the green answer Matched outbound: quanticdata-us, framed.
  9. 09

    Send a request through the inbound

    Connect through the inbound as its clients do and load an IP page. Our test inbound was a mixed one with its own account on port 10811, so curl could use it directly: the answer was a Charter Communications home connection in New York, the same on three requests in a row.

    curl through the 3X-UI test inbound on 127.0.0.1:10811: ipinfo.io returns a United States address in University Gardens, New York, on Charter Communications, framed with the IP and host name hidden and the inbound account replaced by placeholders
    curl through the 3X-UI test inbound on 127.0.0.1:10811: ipinfo.io returns a United States address in University Gardens, New York, on Charter Communications, framed with the IP and host name hidden and the inbound account replaced by placeholders.

Check it

Two checks inside the panel: Check on the outbound's row in HTTP mode fills Country and Latency, and Route Tester answers Matched outbound with your tag for the inbound you routed. Then load an IP page through that inbound: the address must be the exit of your line.

The panel wrote the outbound and the rule into its Xray configuration and applied them on Save. 3X-UI 3.11.0 with Xray 26.10.21 is shown, running in a Docker container.

The inbound we routed in the test

A rule needs an inbound to match. On your server that is the inbound you already use; pick it in Inbound tags and leave it as it is. For this guide we added one for the test: Inbounds, Add Inbound, Remark local-test, Protocol mixed, Port 10811. The Protocol tab of that form holds the Accounts row with a username and a password, and Auth set to password.

The panel named it in-10811-tcp, and that is the tag the routing form and the Route Tester list. A mixed inbound accepts SOCKS5 and HTTP on one port: curl reached the QuanticData line through socks5h:// and through http:// on 10811, with the account of the inbound in the proxy address.

Which QuanticData line to put behind 3X-UI

  • Residential Premium: a home IP in the country you choose, host residentialpremium.quanticdata.io, SOCKS5 1080 or HTTP 8080, with the session name and its length set in the username. The socks outbound of this guide ran on it.
  • Mobile: a carrier IP for traffic that should look like a phone, host mobile.quanticdata.io, HTTP 8080 or SOCKS5 1080. The http outbound of this guide ran on it, and the panel's HTTP check returned a United States egress.
  • Residential Basic: home IPs with the host and port printed in the line, typed into Address and Port as they are.
  • ISP: one dedicated IP that never changes, for a server that must keep the same address for weeks. The line comes from the plan page.

3X-UI outbound not working: what to check

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

PlanCopy it fromHTTP portSOCKS5 portUsername shape
Residential Premiumthe generator80801080USER-country-us-sid-k3f9a1b2-ttl-30m
Mobilethe generator80801080USER-country-us-type-mobile-sid-a1b2c3-ttl-30m
Residential Basicthe generatorin the linein the lineUSER-country-us plus a session for sticky
Datacenter (per GB)the generator999910000the line's username
IPv6the generator1001in the linethe line's username
ISP (dedicated IP)the plan page, one line per IPin the linein the linethe 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
    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
    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
    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.

3X-UI proxy questions

What customers ask when they put a QuanticData line into 3X-UI.

Something else? Ask us

How do I add a SOCKS5 proxy with a username and password in 3X-UI?

Open Outbounds, click + Outbounds, choose socks at the end of the Protocol list and fill Tag, Address, Port, Username and Password. Click Create, then Save at the top of the page. A routing rule then sends an inbound to that tag.

Where are socks and http in the 3X-UI protocol list?

At the end. In 3X-UI 3.11.0 the list runs freedom, blackhole, dns, vmess, vless, trojan, shadowsocks, wireguard, amneziawg, hysteria, masque, socks, http, loopback, and only the first eight show until you scroll.

Do I have to restart Xray after adding an outbound in 3X-UI?

Not in our run. After Save the panel showed The parameters have been changed, and the next request through the routed inbound already left from the QuanticData line.

How do I test an outbound inside 3X-UI?

On the Outbounds page set the test mode to HTTP and click Check on the row. The panel fills the egress address, the country and the latency: United States and 204 ms for our residential outbound.

What does the Route Tester in 3X-UI do?

It asks the running Xray which outbound would handle a connection from a given inbound to a given domain and port, without sending traffic. With our rule saved it answered Matched outbound: quanticdata-us.

Put a home or mobile IP behind your 3X-UI inbound

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

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