Seeing Failed to Add Profile, Unexpected Connection Error, or “unable to determine subscription link type” during an import does not necessarily mean every node is unavailable. The failure may occur while downloading the subscription, validating HTTPS, recognizing its content format, or saving the configuration.

Windows users have reported the same messages in the official repository. Issue #1661 records Failed to Add Profile / Unexpected Connection Error, while Issue #2037 records a Clash-format subscription that could not be recognized. These are user cases; they do not prove that every device has the same root cause.

Symptoms

An error appears immediately after selecting “Add from clipboard.”
Entering a URL manually produces an unexpected connection error.
A link imports in an older version or on another device but fails on the current device.
The app cannot determine the subscription type, or no nodes appear after import.
“Check for updates” and “Add profile” both produce network errors.

If the profile already exists and only its refresh fails, see Subscription update failed instead.

Two-minute diagnosis

Copy the subscription address again from the provider’s dashboard. Confirm that it begins with https:// or a supported single-node scheme and contains no spaces, line breaks, or missing characters.
Do not publish the link. Open the HTTPS address in a trusted browser and observe whether it returns configuration content or redirects to a login, CAPTCHA, error, or certificate-warning page.
Switch once between Wi-Fi and a mobile hotspot. If it fails only on one network, investigate DNS, TLS, or access restrictions on that network first.
Import the same link on another device, or import another known-good subscription on the current device. Use the cross-test to distinguish a device problem from a subscription problem.
Record the complete error text and time. Do not repeatedly reinstall the app, switch cores, and change every advanced setting.

Troubleshoot by layer

Client: verify the input method and version

The official documentation describes two basic methods: add from the clipboard, or enter a name and URL manually. See the official HiddifyApp usage guide for the steps.

Paste the link into a local plain-text editor to inspect its beginning, end, and unexpected line breaks, then delete that temporary text immediately.
If adding from the clipboard fails, use “Add manually” with the same complete URL. This test only rules out a clipboard-content problem.
Check the current stable version and correct package for the platform in the official Releases.
Preserve existing working profiles before upgrading. Do not begin by clearing app data, which may delete the only usable local configuration.
“Enable debug mode” suggestions in individual Issue comments are not universal fixes. Debug mode is mainly useful for obtaining a more specific error log.

Subscription: confirm the response is a configuration, not a webpage

Check the account expiry, remaining traffic, and concurrent-device limit.
Confirm that you copied the “subscription link,” not the provider dashboard, payment page, or tutorial page.
If the browser returns an HTML login page, CAPTCHA, WAF block page, blank page, or error JSON, the provider must correct the response.
If a link claims to contain Clash, sing-box, or single-node data, its response must match that declaration. The official guide lists multiple subscription and protocol formats supported by Hiddify, but “supported” does not mean arbitrary text can be parsed.

DNS/TLS: preserve the HTTPS security boundary

Correct the operating system’s date, time, and time zone.
Check whether the browser reports a hostname mismatch, expired certificate, untrusted certificate chain, or TLS handshake failure.
Test on another network first, then handle DNS according to the log. Do not mistake a certificate problem for a node failure.
Do not disable system certificate validation or install a root certificate from an unknown source.

Never change a subscription from https:// to http://. Even if a user comment describes it as a temporary workaround, HTTP exposes the subscription token and node details in plaintext. Hiddify’s official HISTORY also records the security decision to disable HTTP subscription links in 4.x: view the changelog.

Server: ask the provider to inspect the actual response

If the same link cannot be imported on multiple devices and networks, ask the provider to check:

whether the HTTPS certificate is valid and its chain is complete;
whether the request returns 200 rather than a 3xx loop, 401, 403, 404, or 5xx;
whether the redirect destination remains securely reachable;
whether the response body contains valid Clash, sing-box, or node configuration;
whether the token, account, traffic quota, and device limit are valid.

When migrating a subscription domain, the provider can follow the moved-permanently-to mechanism in Hiddify’s official URL Scheme documentation instead of asking users to downgrade to HTTP.

Verification

After resolving the problem, all of the following should be true:

Remove duplicate profiles created by testing, but keep the confirmed working profile.
Import or refresh the same HTTPS link three consecutive times without the original error.
The profile shows nodes, and at least one node completes both a latency test and a real website request.
The profile remains after restarting the application.
The same download, certificate, or parsing error no longer appears in the log.

If the import succeeds but there is no network access after connecting, continue with Hiddify connected but no internet.

When to contact the provider

Contact the subscription provider directly if the browser shows a certificate warning, the link returns a login or error page, the account has expired, multiple clients cannot read the link, or several nodes from the same provider fail together.

If the link works in other clients and on other devices but consistently fails in one Hiddify version, submit the operating system version, Hiddify version, installation source, exact error, reproduction steps, and redacted logs to the official Issues. Do not include the complete subscription URL, token, UUID, QR code, or server credentials.

Hiddify Cannot Import a Subscription: Failed to Add Profile