TX-UI VPS plans currently listed

ProviderPlanvCPURAMDiskRegionsBillingPrice
EnzonixShared Compute - General Compute11 GB20 GBAshburn, United StatesFixed price$5.00/mo
EnzonixShared Compute - General Compute11 GB20 GBAmsterdam, NetherlandsFixed price$5.00/mo
EnzonixShared Compute - General Compute24 GB80 GBAmsterdam, NetherlandsFixed price$9.00/mo
EnzonixShared Compute - General Compute24 GB80 GBAshburn, United StatesFixed price$9.00/mo
EnzonixShared Compute - General Compute48 GB160 GBAmsterdam, NetherlandsFixed price$16.00/mo
EnzonixShared Compute - General Compute48 GB160 GBAshburn, United StatesFixed price$16.00/mo
EnzonixShared Compute - General Compute816 GB320 GBAmsterdam, NetherlandsFixed price$32.00/mo
EnzonixShared Compute - General Compute816 GB320 GBAshburn, United StatesFixed price$32.00/mo
EnzonixShared Compute - General Compute11 GB20 GBAshburn, United StatesHourly$0.007/hr
EnzonixShared Compute - General Compute12 GB40 GBAshburn, United StatesHourly$0.01/hr
EnzonixShared Compute - General Compute24 GB80 GBAshburn, United StatesHourly$0.015/hr

TX-UI Instant App

Self-hosted TX-UI VPS hosting

TX-UI is a 3X-UI fork with Xray-core, AmneziaWG 3.1, MTProto FakeTLS, and Iran routing helpers. Compare live prices, deploy with a VLESS client link already written, and connect from v2rayNG, Hiddify, or Happ.

TX-UI logo

TX-UI

Instant App on marketplace VPS

Live marketplace offers

Compare TX-UI VPS plans

Choose billing and size, compare providers side by side, pick a location, then launch.

Enzonix logo
Enzonix

Shared Compute - General Compute

$5.00/mo

1 vCPU · 1 GB · 20 GB

Choose location

Ashburn, United States

1 provider

Inside TX-UI

TX-UI is the web panel. Xray-core on the same VPS accepts connections and forwards traffic. The panel can also run AmneziaWG 3.1 and MTProto FakeTLS when you add those inbounds. This Instant App creates one VLESS TCP inbound and a client link for you, with no form fields at create time.

  • TX-UI overview with Xray-core running and resource gauges

    Xray-core status on the overview

    The panel shows whether Xray-core is running, along with CPU, memory, and throughput. Restart, logs, and the Xray config are on the same screen.

  • TX-UI inbounds list with noderings-default VLESS on 8443

    An inbound for each listener

    Each inbound is a protocol, a port, and a transport. This Instant App creates one VLESS TCP inbound on port 8443, named noderings-default, with TLS off. Add AmneziaWG, MTProto FakeTLS, REALITY, or another inbound when the first one is not enough.

  • TX-UI clients view for the ready inbound

    A client for each person

    Clients have a label, a traffic cap, an expiry, and an IP limit. The first client label is noderings, and its link is in the credentials file. Add another client when a second phone should have its own quota.

  • TX-UI add inbound form with VLESS protocol selected

    Add more inbounds in the panel

    The add-inbound form picks protocol, port, and listen settings. Use it for AmneziaWG, MTProto FakeTLS, or a TLS/REALITY inbound when plain VLESS is not enough on your network.

What runs behind TX-UI

Xray-core

TX-UI stores clients, inbounds, and traffic. Xray-core is the process that listens for VLESS and the other Xray protocols you enable. The panel can also manage AmneziaWG 3.1 and MTProto FakeTLS. The overview reports Xray as running or stopped. A panel login with no imported client leaves the phone on its normal connection.

Configure TX-UI

After the VPS is up, sign in, change the panel password, and check that the ready inbound is the one you want to hand out.

  1. 01

    Open the panel

    In a browser, open http:// and the IPv4 from your order. You should see the TX-UI login.

  2. 02

    Read the password and the client link

    SSH in as root with the create-flow password or key. The file lists the panel user, the panel password, and the first VLESS link. The txui_core line says xray-core.

    cat /root/.noderings_password
  3. 03

    Sign in and change the panel password

    Use txui_admin_user and txui_admin_pass from that file. Change the password in panel settings before you leave the login on the public internet.

  4. 04

    Leave the working ports reachable

    TCP 22 is SSH. TCP 80 is the panel. TCP 8443 is the ready VLESS inbound. The container uses the host network. AmneziaWG or other inbounds you add later need their own ports.

  5. 05

    Know what the first inbound is

    Remark noderings-default, protocol VLESS, transport TCP, port 8443, TLS off. That link exists so a phone can connect on first boot. On a filtered network, add AmneziaWG, MTProto FakeTLS, REALITY, or another inbound and give clients that link. Plain VLESS is easy for a network to recognize.

Add a user

A user is a client on an inbound. The Instant App creates the first one. You create the rest in the panel.

  1. 01

    Open the ready inbound

    In the panel, go to Inbounds. Select noderings-default, or create a new inbound when you want a different protocol or port.

  2. 02

    Add a client

    Add a client on that inbound. VLESS clients get a UUID. The email field is a label (the first one is noderings). You can set a traffic cap, an expiry, and an IP limit.

  3. 03

    Copy the QR, the link, or the subscription

    From the client row, show the QR code, copy the share link, or copy the subscription URL. For the first client, the same link is the txui_client_link line in the credentials file.

  4. 04

    One link can sit on several devices

    Importing one link on a phone and a laptop counts as one client. Set an IP limit when you want to stop sharing. Add a separate client when you want a separate quota or a clean revoke.

  5. 05

    Revoke a client

    Disable or delete that client in the panel and save. The panel updates Xray-core. The old link stops working after the reload.

Connect a phone or laptop

You import a VLESS link, a QR code of that link, or a subscription URL. Then you turn the tunnel on in the client app. For an AmneziaWG inbound you create later, use an Amnezia client and the panel's .conf or share link.

  1. 01

    Install a client for that device

    Android: v2rayNG or Hiddify. iOS: Hiddify, Streisand, Happ, or Shadowrocket. Windows: v2rayN, Happ, or Hiddify. macOS and Linux: Hiddify, Happ, or Clash Verge Rev with a Clash subscription. AmneziaWG inbounds need an Amnezia client.

  2. 02

    Import the profile

    Paste the VLESS link, scan the QR from the panel, or add the subscription URL. The first link is txui_client_link in the credentials file.

  3. 03

    Connect

    Select that profile and turn the tunnel on. Allow the VPN permission the phone asks for.

  4. 04

    Check that traffic uses the VPS

    Open a page that shows your public IP and compare it with the VPS address. In the panel, the client should show as online. If the IP did not change, the tunnel is not carrying traffic.

  5. 05

    If it fails

    Confirm TCP 8443 is open and the link host is the VPS IP, not 127.0.0.1. A TCP inbound will not connect if the client is set to UDP. After you switch an inbound to REALITY or AmneziaWG, check the client matches that protocol.

Clients that work

These apps run on the phone or computer. They are not Instant Apps. Import a link from this server, and pick an app that speaks the protocol of the inbound you are using. The ready inbound is VLESS over TCP.

  • v2rayNG

    • Android

    Android. Scan the QR or paste the VLESS link.

  • NekoBox

    • Android

    Android client built on sing-box. Imports the same VLESS link.

  • Hiddify

    • Android
    • iOS
    • Windows
    • macOS
    • Linux

    The Hiddify app, separate from Hiddify Manager. Imports a link or a subscription.

  • Streisand

    • iOS
    • macOS

    iOS, and macOS on Apple silicon. Imports the VLESS link.

  • Happ

    • Android
    • iOS
    • Windows
    • macOS
    • Linux

    Phone and desktop builds. Imports the VLESS link or a subscription.

  • Shadowrocket

    • iOS

    Paid iOS app. Imports the VLESS link.

  • v2rayN

    • Windows

    Windows. Paste the VLESS link or add a subscription.

  • Clash Meta

    • Android
    • Windows
    • macOS
    • Linux

    Use when you import a Clash subscription from the panel.

Where it helps

A VPS in a region you pick is an exit for traffic you send through Xray-core. On a filtered ISP, the result depends on the inbound, the client, and what that network blocks. The ready inbound is plain VLESS over TCP, with no TLS. TX-UI's AmneziaWG and MTProto options are for later tuning.

Where TX-UI is commonly used, and where it is a poor match
SituationFitWhat to expect
Everyday privacy exitDepends on the networkUseful when you want traffic from a phone to leave through a VPS you picked. The hosting provider can see that server.
Filtered networks in IranOften usedTX-UI ships Iran routing helpers plus AmneziaWG 3.1 and MTProto FakeTLS in the panel. Operators often replace plain VLESS TCP with one of those. Test on your own line.
China (GFW)Depends on the networkPeople test REALITY, Hysteria, and similar inbounds. Plain VLESS TCP is a weak start. Verify on the network you actually use.
Russia and other filtered ISPsDepends on the networkSometimes chosen when a network filters WireGuard or OpenVPN. The protocol still has to pass that ISP.
OpenVPN-only or office VPN profilesPoor matchOpenVPN Connect will not import a VLESS link. TX-UI can add AmneziaWG or WireGuard later. This Instant App creates a VLESS inbound.

Why use the NodeRings marketplace?

Compare live TX-UI VPS plans from independent providers, then run the Incognito-Coder panel and Xray-core on the offer you pick. A 3X-UI fork with AmneziaWG 3.1 and MTProto FakeTLS in the panel. Use it instead of paying for a commercial Xray panel or a retail VPN subscription.

  • Compare TX-UI VPS offers in one place

    See live prices, regions, and plan sizes before you buy. Shop self-hosted Xray panel hosts across independent providers.

  • Panel and Xray-core on first boot

    Deploy TX-UI and the VPS comes up with the panel, Xray-core, a VLESS inbound, and a client link. AmneziaWG and MTProto stay available in the panel. You still get root SSH.

  • Choose the exit region yourself

    The provider region is the geography of the VPS address clients will use. That choice is separate from whether a filtered ISP lets the tunnel connect.

  • Passwords and client links stay on the VPS

    The panel password and the first client link are written on the server. You change the password, revoke clients, and decide which inbound stays open.

TX-UI hosting from independent providers

Most TX-UI install guides assume one server you already own. NodeRings lists Compute Instance plans from independent providers so you can compare self-hosted Xray offers by price, size, and region, then launch on the one that fits.

TX-UI Instant App prepares the panel and Xray-core on the provider VPS you selected. The provider operates that machine. NodeRings lists the plan and deploys the Instant App.

Single-provider TX-UI hosting

  • One company catalogue and renewal price
  • One set of regions
  • One vendor panel for that host only

NodeRings marketplace

  • TX-UI VPS offers from independent providers
  • Compare resources, prices, and regions side by side
  • Deploy TX-UI on the plan you pick

How it works

Compare plans, pick a provider offer, and launch TX-UI on that server.

  1. 01

    Compare TX-UI plans

    Pick a provider offer. A sensible start is 1 vCPU, 2 GB RAM, and 20 GB disk. Smaller and larger plans stay on the list.

  2. 02

    Deploy TX-UI

    Launch the Instant App on that plan. The panel and Xray-core come up together. There are no extra form fields.

  3. 03

    Import the client link

    Read the VLESS link from the server, import it in v2rayNG, Hiddify, Happ, or another app below, and confirm the tunnel from the phone.

On the VPS after TX-UI deploys

NodeRings Instant App brings TX-UI and Xray-core up with Docker Compose on the host network. The panel listens on port 80. A VLESS inbound listens on port 8443. TUN is mounted so AmneziaWG can work when you enable it. The admin password and the first client link are written for you.

Open the panel

  • In a browser, go to http://YOUR_SERVER_IP/ using the IPv4 from your order.
  • Sign in with txui_admin_user and txui_admin_pass from the credentials file.
  • The panel account is not the VPN client. Import txui_client_link into a phone or desktop app to connect.
  • Change the panel password after the first sign-in.

Where the password and client link are

Credentials are written on first boot to:

/root/.noderings_password

Read them over SSH:

cat /root/.noderings_password
  • Keys include txui_admin_user, txui_admin_pass, txui_panel_url, txui_core, txui_inbound_protocol, txui_inbound_port, txui_client_email, txui_client_uuid, and txui_client_link.
  • txui_core is xray-core. txui_inbound_protocol is vless. txui_inbound_port is 8443.
  • SSH in as root with the create-flow password or key, then run the command above.

Where files live

Compose project directory

/opt/noderings/tx-ui
/opt/noderings/tx-ui/docker-compose.yml
/opt/noderings/tx-ui/.env

Working directory for Compose, the stack file, and generated admin and client values.

Panel database

/opt/noderings/tx-ui/db

TX-UI data directory, mounted into the container. Inbounds and clients live here.

Certificate directory

/opt/noderings/tx-ui/cert

Present for panel certificates you add later. The first boot does not issue one.

Credentials file

/root/.noderings_password

Written on first boot. Includes the panel password and the first client link.

Boot unit

/etc/systemd/system/noderings-tx-ui.service

Brings Compose up after Docker is ready.

What runs in Docker

One Compose service, tx-ui, runs the panel and Xray-core on the host network. Port 80 is the panel. Port 8443 is the ready VLESS inbound. /dev/net/tun is mounted for AmneziaWG. The container is allowed to manage network interfaces so Xray-core can forward traffic.

  • tx-ui

    Web panel and Xray-core on the host network (TUN available for AmneziaWG).

Container status

cd /opt/noderings/tx-ui && docker compose ps

Live logs

cd /opt/noderings/tx-ui && docker compose logs -f

Restart containers

cd /opt/noderings/tx-ui && docker compose restart

systemd unit status

systemctl status noderings-tx-ui

Add HTTPS with Cloudflare

Your TX-UI panel starts on http://. Cloudflare can give the panel a padlock without installing a certificate on the VPS. This covers the website on ports 80 and 443. It does not carry the VLESS inbound.

  1. Add your domain

    Sign up at Cloudflare and add the domain you want to use for the panel.

  2. Point it at your VPS

    Create an A record to your server IP and leave the orange cloud on.

  3. Open the https panel

    Visit https://your-domain and sign in with the panel password. Keep the VLESS client link pointed at the raw VPS IP and port 8443. Cloudflare's proxy does not forward that raw TCP inbound.

  4. Only allow Cloudflare to the panel

    Optional. With SSH (port 22) allowed, open Cloudflare to ports 80 and 443 for the panel, and leave TCP 8443 open so clients can still reach Xray-core:

    curl -s https://www.cloudflare.com/ips-v4 | while read ip; do sudo ufw allow from "$ip" to any port 80,443 proto tcp; done
    sudo ufw allow 22/tcp
    sudo ufw allow 8443/tcp

Keep port 22 allowed for SSH. Keep TCP 8443 allowed for the ready inbound, or the phone will not connect.

More detail

  • No Instant App form variables. The first inbound is VLESS over TCP with TLS off.
  • NodeRings does not sell TX-UI as a product and is not the TX-UI project.

What size VPS for TX-UI

Xray-core and the panel are light on disk. CPU and bandwidth matter more once several clients are connected, especially with AmneziaWG or REALITY. These rows are starting points, not a filter on the plans above.

Illustrative starting points for TX-UI VPS sizing
WorkloadIllustrative starting pointNote
One or two phones1 vCPU, 2 GB RAM, 20 GB diskMatches the Instant App floor. Enough for the panel and a personal VLESS inbound.
A household or a small team2 vCPU, 4 GB RAM, 40 GB diskMore headroom when several clients are online and you add AmneziaWG or a second inbound.
Many subscription users4 vCPU, 8 GB RAM, 40 GB diskCPU and the provider's bandwidth cap show up before disk does.

Illustrative only. Live plans are not filtered by this table. A filtered network can still block a tunnel that fits on a small VPS.

Who operates what

You get root on a provider VPS. NodeRings lists the plan and deploys TX-UI. The provider runs the machine.

  • You

    Panel password, which inbounds exist, who receives a client link, the host firewall, and the provider's terms. The ready inbound is plain VLESS. Change it if that is not what you want on the public internet.

  • The provider

    The VPS, the network, and the exit IP. Abuse on a public proxy port can get that provider to suspend the server.

  • NodeRings

    The marketplace and the Instant App that deploys TX-UI with Xray-core. NodeRings does not run a VPN service and does not see client traffic.

TX-UI VPS FAQs

Which apps can connect to this TX-UI server?

v2rayNG and NekoBox on Android. Hiddify and Happ on Android, iOS, Windows, macOS, and Linux. Streisand on iOS and macOS. Shadowrocket on iOS. v2rayN on Windows. Clash Meta when you import a Clash subscription. AmneziaWG inbounds need an Amnezia client. OpenVPN Connect will not import a VLESS link.

Will TX-UI help on a filtered network in Iran or China?

People commonly run TX-UI when an ISP filters ordinary VPN apps. The panel includes Iran routing helpers, AmneziaWG 3.1, and MTProto FakeTLS. The ready inbound is VLESS over TCP with no TLS, and many filtered networks block it. Add AmneziaWG, MTProto, REALITY, or another inbound if you need a different path. Expect to test on your own connection.

How do I add another phone or laptop?

In the panel, add another client on the inbound, or import the same link on a second device. One shared link counts as one client unless you set an IP limit. To stop a device, disable or delete that client and save.

How is this different from 3X-UI?

TX-UI is a fork of 3X-UI with AmneziaWG 3.1, MTProto FakeTLS, and Iran-oriented panel features. The Instant App still ships a ready VLESS inbound like the other Xray panels. Prefer 3X-UI or S-UI unless you want this fork's extras.

Which ports have to stay open?

TCP 22 for SSH, TCP 80 for the panel, and TCP 8443 for the ready VLESS inbound. If you add AmneziaWG or other inbounds, open those ports too.

Does NodeRings run the VPN?

NodeRings lists provider plans and deploys the Instant App onto the plan you pick. The provider operates the VPS. You operate TX-UI and Xray-core.

What is the ready client link?

A VLESS URL for the inbound on port 8443, stored as txui_client_link. Import it to test that the phone can reach Xray-core. For a network that filters plain proxies, create AmneziaWG, MTProto, TLS, or REALITY in the panel and hand out that link instead.

Back to live TX-UI plans

Compare provider offers, then launch TX-UI on the plan that fits.