Subscriptions
Maintain provider profiles, node visibility, updates, usage, and expiry.
A subscription is a provider profile that can contain many nodes and optional profile information. Tunna fetches the profile, processes the nodes, and shows them in Outbound under that subscription. This is how Tunna keeps managed node lists usable without asking you to edit every server by hand.
Adding a subscription
What the subscription screen shows
Use these cards as a map of the visible labels in this view. Each card names one field, control, or status item and explains what it is for before you change it or rely on it.
General Settings
Use these fields to name the provider profile and control how Tunna fetches and displays it.
Name
The local label for the profile. Provider titles can fill it when the name is still blank or default.
Auto Update
Lets Tunna refresh the profile when the provider interval has elapsed and the app has a chance to check it. Use Update when you want the latest nodes, usage, expiry, or provider links immediately.
User Agent
Choose Tunna, Chrome, Firefox, Safari, iOS, Android, or Edge for the request identity. Keep Tunna unless the provider requires another choice.
Node Visibility
Choose All, Active, or Top 10 to decide which subscription nodes appear in Outbound.
Source
The remote URL is the provider address Tunna fetches. Paste in the Source field fills the URL for this subscription and starts a fetch after a valid URL is submitted and the network is available.
Status footer
A colored status line shows Ready to fetch, Fetching data, Processing data, Active, Failed, or Expired. Failed rows show the error message when Tunna has one.
Update
The Update button fetches the current remote URL again. It is disabled for new profiles, empty URLs, and fetches already in progress.
Profile and Support
These bottom buttons open provider links only when the fetched profile includes them.
Node Visibility
| Choice | What Outbound shows | Best for |
|---|---|---|
| All | Every selectable node from the subscription. | Browsing or manually choosing from the full list. |
| Active | Nodes with recent successful checks, with a fallback when none are active. | Hiding stale nodes without losing a safety fallback. |
| Top 10 | The ten best nodes by recent latency. | Large subscriptions where the fastest choices should be visible first. |
What a fetch updates
During a fetch, Tunna sends the selected User Agent, downloads the provider profile, reads provider metadata when available, then parses node links from the response. If no usable nodes are found, the subscription is marked failed. When a provider sends metadata, Tunna can update usage, expiry, profile link, support link, profile title, and profile update interval.