-
Notifications
You must be signed in to change notification settings - Fork 117
Server Profiles and Sharing
A server profile combines user-facing metadata with a backend connection configuration. Furious keeps those responsibilities separate so subscription ownership, test results, tags, and other profile metadata do not have to be embedded in a core-specific document.
A profile contains two broad kinds of data:
- Metadata — remark/display name, stable profile identity, subscription ownership, test results, and future annotations such as groups or tags.
- Connection configuration — protocol, address, port, credentials, transport, TLS, local proxy listeners, and backend-specific options.
The Home table presents both, but protocol plugins own parsing, validation, editing, and share-link serialization for their configurations.
Open the Server menu on Home.
Choose Add VMess Server..., Add VLESS Server..., or another protocol-specific action. The available actions are discovered from installed protocol and editor capabilities rather than maintained as a fixed list in Home.
A structured editor validates and preserves the fields supported by that protocol. Double-click an existing row to open the corresponding editor.
New Empty Configuration creates a profile intended for direct Furious JSON editing. The Advanced submenu provides Customize JSON Configuration... for an existing profile.
Raw editing is useful for backend features not yet exposed in a structured editor, but it bypasses many editor conveniences. Keep a backup and avoid changing the profile type to an unsupported value.
The Server menu and table context menu expose shared import operations:
- Import Share Link From Clipboard accepts one or more newline-separated protocol URIs.
- Scan QR Code On The Screen decodes supported share URIs visible on the current display.
- Import JSON Configuration From Clipboard imports Furious profile JSON.
- Import From File... reads a configuration from a local file.
URI dispatch is scheme-based and plugin-owned. A malformed URI is reported by its protocol parser rather than being silently interpreted as another protocol.
Subscriptions reuse the same protocol handlers after a subscription decoder has produced individual items. See Subscription Management.
Select one or more rows and use the context menu to:
- move profiles up or down;
- duplicate or delete profiles;
- activate the selected profile;
- scroll to the activated profile;
- run ping, TCP connect, or download-speed tests;
- clear test results;
- edit raw JSON;
- import or share configurations.
Duplicate creates a new independent profile identity. If the source belongs to a subscription, the duplicate becomes a manual profile so a later subscription synchronization does not overwrite it.
The profile filter above the table can show All Profiles, Manual Profiles, or profiles owned by one subscription. Search accepts plain text or a regular expression.
The active profile is the one used by the next connection attempt. Starting a connection activates the single selected row. Selecting another row while disconnected does not by itself rewrite that profile's data.
Changing the routing selector while connected requests a controlled reconnection using the new routing mode. Editing connection fields generally takes effect on the next connection.
Choose Export Share Link To Clipboard for one or more selected profiles. Multiple links are separated by newlines. Export uses one canonical URI per supported protocol and preserves the protocol fields and remark that its codec can represent.
Current shareable protocols include VMess, VLESS, Shadowsocks, Trojan, SOCKS, Hysteria 1, and Hysteria 2. The corresponding parser handles hostnames, IPv4, and protocol-supported IPv6 forms. Reserved characters in credentials and remarks are encoded according to the protocol's URI format.
A profile may be valid for local use but not have a share-link representation. In that case no URI is produced.
Choose Export As QR Code to create one tab per selected profile that has an exportable share URI. The full profile title is available as the tab tooltip when its visible title is elided.
QR codes contain the same URI produced by share-link export; they are not a separate configuration format.
Export JSON Configuration To Clipboard serializes the selected Furious profiles. JSON can preserve configuration that a share URI cannot represent, but it may include credentials, machine-local paths, and backend-specific fields. Review it before sharing.
External Core profiles deliberately have no public URI format and cannot be subscription items. Their internal JSON is machine-local and potentially executable; see External Core.
Treat every exported URI, QR code, subscription response, and JSON profile as sensitive. Depending on the protocol, it may contain passwords, UUIDs, authentication tokens, certificates, public-key parameters, or local environment values.
Before posting diagnostics:
- reproduce the issue with the smallest relevant profile;
- remove credentials and subscription URLs;
- keep the protocol, transport, and non-sensitive error context;
- verify that logs do not contain data copied from an external program.
A subscription profile records its source group. Synchronization may replace its connection configuration with the provider's latest item while preserving the profile identity and supported metadata.
For a lasting local variation:
- duplicate the subscription profile;
- edit the manual duplicate;
- leave the managed original available for future synchronization.
Deleting a subscription also removes the profiles that it owns. Read Subscription Management before reorganizing a managed collection.