OK.TEAM LLC

Operator-owned infrastructure

Self-host.
Connect your way.

Install OK Connect Panel on your own server and domain. Create private subscription links for the OK Connect VPN client — without a central OKTEAM account.

OK Connect Panel 1.0.0 · First Linux x86-64 test release · October 16, 2026

1. Download a release

The native bundle is for a Linux x86-64 host running systemd. It contains the panel, a compatible Xray executable and geodata, the corresponding panel source, license notices, and deployment files. This is an initial test release, not a promise of a fully hardened production installation. Test on an isolated server and review the configuration before granting access.

Linux x86-64 bundle · v1.0.0 Complete corresponding source SHA-256 checksums

Download only over HTTPS from a source you trust. Checksums help detect a damaged or mismatched download; a checksum from the same website is not an independent signature or trust guarantee.

The company test administration is restricted to authorized operators. It is not public sign-up, a free VPN account, or a requirement for your own installation.

2. Before you start

  • Use a Linux x86-64 server with systemd and administrative access. The native installer checks the target platform.
  • Point a domain you control, such as panel.example.com, to that server. The installer does not create DNS records.
  • Provide Python 3, GNU checksum tools, standard system-account tools and systemd utilities. Curl and tar are useful for downloading and extracting the bundle.
  • Prepare a trusted HTTPS certificate and reverse proxy for your own hostname. The installer does not install a certificate or modify the proxy.
  • Back up existing site and server configuration. Review the bundled scripts, listen addresses, proxy locations and source notices before running anything as root.

The installer creates an isolated service account, installs files under /opt/okconnect-panel-3xui, stores runtime data under /var/lib/okconnect-panel-3xui, and writes configuration under /etc/okconnect-panel-3xui. Those technical paths are compatibility identifiers, not a different product.

3. Install the native bundle

Download the bundle and checksum manifest into a new working directory on the target server. Review the manifest, then check the downloaded archive before extracting it:

curl --fail --location --output ok-connect-panel-v1.0.0-linux-amd64.tar.gz \
  https://okconnect.net/downloads/ok-connect-panel-v1.0.0-linux-amd64.tar.gz
curl --fail --location --output SHA256SUMS \
  https://okconnect.net/downloads/SHA256SUMS
sha256sum --check --ignore-missing SHA256SUMS
tar -tzf ok-connect-panel-v1.0.0-linux-amd64.tar.gz

Extract into a new directory. If the archive includes a top-level folder, enter that folder. The bundle root must contain ok-connect-panel, bin/, deploy/, source.tar.gz, LICENSE, NOTICE.txt and its own SHA256SUMS.

mkdir okconnect-release
tar -xzf ok-connect-panel-v1.0.0-linux-amd64.tar.gz -C okconnect-release
cd /absolute/path/to/extracted/bundle
sha256sum --check --strict SHA256SUMS
sudo bash deploy/okconnect/install-native.sh \
  --domain panel.example.com \
  --bundle "$PWD" \
  --skip-nginx

Replace panel.example.com and the example directory with your own values. The installer validates the internal manifest, initializes private administrator credentials and a bounded pilot configuration, and starts the panel service. An existing active installation with a different executable is not silently replaced.

This command does not change your website, Nginx, firewall, DNS or certificates. It does not make the panel publicly reachable by itself. Continue with the HTTPS step below.

4. Configure your HTTPS reverse proxy

The installer writes the location snippet /etc/okconnect-panel-3xui/nginx-locations.conf for the hostname you supplied. Review it and add the locations to the appropriate HTTPS server block for your own domain. Keep the existing website root, certificate paths and unrelated locations intact. Do not replace a working site with a whole new server configuration.

The initial layout uses these endpoints:

  • /panel/ → private panel listener at 127.0.0.1:8083.
  • /panel-sub/ → private subscription listener at 127.0.0.1:8084.
  • /okconnect-tunnel/ → the WebSocket connection listener at 127.0.0.1:10000.

Preserve the path prefixes and WebSocket upgrade headers from the supplied snippet. Do not publish the loopback listener ports directly. Review your firewall and expose only the required public services. After applying your own certificate and proxy configuration, test it before reloading:

sudo nginx -t
sudo systemctl reload nginx

Run the reload only if validation succeeds and you have reviewed the change. A different reverse proxy can be used if it preserves the same routing, HTTPS and WebSocket requirements.

5. Create access and connect a client

Retrieve the generated username and password privately on the server from /etc/okconnect-panel-3xui/private/credentials.json. This file is root-only and contains other secrets too. Do not publish its contents or paste it into a public support conversation.

  1. Open https://panel.example.com/panel/ and sign in with your generated administrator credentials. The authenticated administration UI is under /panel/panel/.
  2. Review the configured inbound endpoint and create a client with an expiry date and an appropriate traffic allowance.
  3. Copy that client's private subscription URL or display its QR code. The pilot created by the installer is temporary and bounded, not a permanent review account.
  4. In the OK Connect client, choose Add from clipboard or Scan QR code. Select an endpoint and tap Connect.
  5. Confirm an actual authenticated tunnel and traffic through your endpoint. A green administration page or successful subscription download alone does not prove that the VPN works.

Your users do not need the administrator password. Give each intended user only the access they need. Treat subscription links, client keys and QR codes as credentials; revoke or replace them if exposed.

6. Build from the corresponding source

Download the source archive for this release and verify it against the published manifest. Use the source root containing go.mod, frontend/ and internal/. If you maintain a Git mirror, clone your verified mirror of this exact modified release; no separate public OK Connect Git repository is advertised here.

Building requires the Go toolchain selected by go.mod (Go 1.27.2 for this release), Node.js 26, npm, and a C compiler for SQLite. A Linux cross-build also requires a compatible C cross-compiler. Turning CGo off does not produce a working SQLite installation.

cd /absolute/path/to/corresponding-source
cd frontend
npm ci
npm run build
cd ..
CGO_ENABLED=1 go build -trimpath -o ok-connect-panel .

The frontend build produces the assets embedded into the panel executable. The panel still needs its compatible Xray binary, geodata, deployment files and license notices; building the Go executable alone is not a complete native release bundle. Review the source README and deployment instructions before packaging or installing your own build.

7. Operate and maintain your installation

You are responsible for server security, access policy, backups, software updates, user support and an accurate privacy notice. Monitor actual resource use and connection behavior before increasing the number of users. The panel's traffic counters do not replace a review of all enabled logs and integrations.

Automatic upstream panel replacement is disabled in this distribution. Install reviewed OK Connect releases manually, back up data first and keep a tested rollback. Xray updates are separate and must remain compatible with your configuration. Do not run unrelated upstream install/update scripts expecting them to preserve this branded installation.

Use the encrypted connection for infrastructure and networks you are authorized to access. It can help protect the path from your device to your endpoint on public Wi-Fi; it does not guarantee anonymity, stop malware or secure traffic after that endpoint. Continue using HTTPS and appropriate device security.

8. License and modification notice

OK Connect Panel 1.0.0 is a modified distribution of 3x-ui v3.10.2, pinned to revision 608ef4e4010bf83e2e78328e08f77efc051ad4d7. OKTEAM LLC prepared branding and integration changes on October 16, 2026. This fork is not endorsed by the upstream project.

The panel's original GNU General Public License v3 is preserved, together with upstream attribution and a modification notice. The software is provided without warranty. Xray and other dependencies retain their respective licenses. Read the bundled LICENSE and NOTICE.txt before redistributing a release.

The company installation provides the panel license, modification notices and the corresponding source without an administrator login. Your own installation includes equivalent public paths at its configured base prefix. Keep the exact corresponding source and required notices available when distributing or modifying the software.

For the app and company-operated services, read our Privacy Policy and Terms. An independent operator must provide information appropriate to its own installation.