Skip to content

Quick Start

Jump to bottom
Loren Eteval edited this page Aug 28, 2026 · 1 revision

Quick Start

This guide takes you from an empty Furious installation to a working proxy connection. If Furious is not installed yet, start with Install from PyPI or download a packaged build from GitHub Releases.

1. Open the Home page

Furious starts on Home, whose page title is Server. The main controls are:

  • Connect / Disconnect — starts or stops the selected profile.
  • Routing — chooses a routing policy when the selected backend provides one.
  • Server — adds profiles and exposes import actions.
  • Profile filter — shows all profiles, manual profiles, or one subscription's profiles.
  • Search — filters the table using text or a regular expression.

The table shows each profile's remark, protocol, address, port, transport, TLS mode, subscription, latency, and speed where available.

2. Add or import a profile

Open Server and choose one of these paths.

Add a server manually

Choose the matching Add … Server... action and complete the structured editor. Furious currently provides editors for:

  • VMess
  • VLESS
  • Shadowsocks
  • Trojan
  • SOCKS
  • Hysteria 1
  • Hysteria 2
  • External Core

Use New Empty Configuration only when you intend to work with Furious profile JSON directly.

Import a share link

Copy one or more supported links, then choose Import Share Link From Clipboard. Put multiple links on separate lines.

Supported schemes include:

Protocol URI schemes
VMess vmess://
VLESS vless://
Shadowsocks ss://
Trojan trojan://
SOCKS socks://, socks5://, socks5h://, socks4://
Hysteria 1 hysteria://
Hysteria 2 hy2://, hysteria2://, and supported Realm variants

You can also use Scan QR Code On The Screen, import a Furious JSON configuration from the clipboard, or import a configuration from a file. All share-link entry points use the same plugin-provided protocol parsers.

Add a subscription

Open Subscription from the left navigation rail. A subscription is the best choice when a provider publishes a list that should be synchronized later. See Subscription Management.

3. Select and connect

  1. Select one profile in the Home table.
  2. Choose a routing mode if the routing selector is available.
  3. Click Connect.

Connecting activates the selected profile. A merely highlighted row is not necessarily the active profile until a connection is started.

The connection state progresses through Connecting and Connected. The bottom status area can then show a connectivity result, the active profile remark, and traffic statistics when the backend provides them.

If you double-click a profile, Furious opens its structured editor. The context menu also provides Activate Selected Server and Scroll To Activated Server.

4. Decide how applications reach the proxy

Furious offers two independent host-integration mechanisms.

System Proxy

In Settings, System Proxy can be set to:

  • Automatically Configure System Proxy — Furious applies the active HTTP proxy through the supported operating-system mechanism and removes it during normal disconnection.
  • Do Not Change System Proxy — Furious leaves host proxy settings untouched.

System Proxy only affects applications that honor the operating system's proxy configuration.

TUN Mode

Enable TUN Mode when you need interface-level traffic capture, including applications that ignore System Proxy. TUN may require administrative privileges and may use either a backend's native TUN implementation or Furious's application-managed tun2socks path.

Read TUN Mode before enabling it, especially if you use custom routing.

5. Verify the connection

Useful checks include:

  • The connection button changes to Disconnect.
  • The status area reports Connected and, after the connectivity check, Network OK.
  • Test Ping Latency, Test Tcping Latency, or a download-speed test updates the selected table rows.
  • Metrics displays traffic speed and usage when metrics collection is enabled and the active backend exposes statistics.
  • Log shows application startup, core output, and tun2socks output in filterable categories.

A failed connectivity test can indicate DNS, routing, proxy, or destination reachability problems. Use Troubleshooting and Diagnostics rather than relying on one status label alone.

6. Disconnect cleanly

Click Disconnect before changing host networking or terminating a core manually. Furious then unwinds the active connection resources, including the managed runtime, application tun2socks where used, routes, and automatically managed system proxy state.

Next steps

Clone this wiki locally