SecurQbitDocs

Connecting to a Server

Connect to SecurQbit, choose a location or let auto-select pick the fastest server, and understand connection states and what obfuscation does on connect.

Connecting to SecurQbit is a single tap, but the app gives you control over where and how you connect. This page explains location selection, connection states, and what happens behind the scenes when the tunnel comes up.

Connect with one tap

From the home screen, press Connect. By default SecurQbit uses Auto (fastest), which measures latency and load across the network and routes you to the best-performing server for your current location.

[ Connect ]
  Location:  Auto (fastest)
  Protocol:  Obfuscated HTTPS (adaptive)

Choosing a location

Tap the location selector to choose a specific region from SecurQbit's global network of servers. Pick a manual location when you want to:

  • Appear to be in a particular region.
  • Reduce distance to a service you're accessing.
  • Compare performance between servers.

To return to automatic selection, choose Auto (fastest) at the top of the list.

Tip: For the best throughput, a nearby server usually wins. For reaching geo-restricted services, pick the region you need and expect slightly higher latency. See Performance & Networks.

Connection states

SecurQbit reports a clear status throughout the session:

StateMeaning
DisconnectedNo tunnel. Traffic uses your normal network.
ConnectingNegotiating the key exchange and bringing up the obfuscated tunnel.
ConnectedTunnel is active; traffic is encrypted and routed.
ReconnectingThe network changed or the link dropped; the app is re-establishing the tunnel.

What obfuscation does on connect

The moment you connect, SecurQbit's obfuscation layer disguises the session so that DPI sees ordinary HTTPS rather than a VPN handshake:

  1. The client performs a forward-secret key exchange (see Encryption & Protocols).
  2. Outbound packets are wrapped so their size, timing, and byte patterns resemble normal web traffic.
  3. The layer adapts in real time to network conditions and observed interference. If a path is being throttled, SecurQbit reshapes traffic to keep the session alive.

You don't need to configure any of this — obfuscation is always on at full strength and adapts on its own. See Firewall Bypass & Obfuscation for how it defeats even strict networks.

Reconnection and network changes

When you switch from Wi-Fi to cellular or roam between access points, SecurQbit detects the change and transparently re-establishes the tunnel during the brief Reconnecting window.

Next steps