What has to be masked
| Item | Why | What is usually safe to share |
|---|---|---|
| Full subscription URL | Usually carries a token that consumes your quota | Scheme, domain, and a masked path |
| QR code image | May encode the URL, a node config or a credential | Nothing — do not publish it at all |
| One-click import link | Often the same token in another form | That it exists, described in words |
| Password, verification code, payment details | Account access or financial exposure | Nothing |
| Client name, version, error text, time | Useful for diagnosis, no credential value | All of it |
The five steps, in order
- Remove the public content. Delete the post, message or shared file. This limits further copying; it does not revoke the credential.
- Rotate in the provider panel. Reset the subscription link or token. If the panel has no reset entry, contact the provider — this is the only step that invalidates the old value.
- Replace the address in every client. Remove the old entry first, then import the new one. Leaving the old entry behind makes later troubleshooting ambiguous.
- Update and verify. Refresh the profile and confirm a real HTTPS request completes.
- Check for unauthorised use. Look at quota consumption, online devices, login records and subscription fetch history for anomalies.
Screenshot review, area by area
Before publishing any diagnostic screenshot, check each region: the address bar, the subscription URL field, any QR code, the account email, balance, order number, device name, node remarks and the log body. Keep the client version, the exact error text and the time; none of those need a configuration dump or payment details.
Confirming the old credential no longer works
Do it from your own side. An update with the old address should fail, and the new address should succeed. Check whether the panel states that the token was updated. Where the panel exposes them, confirm that old devices or anomalous traffic stopped. The exact behaviour depends on the provider's implementation, so describe what you observed rather than asserting a general rule.
Do not hand the old link to a third party, an online checker or a group chat “to confirm it is dead”. That re-exposes the credential you are trying to retire.
If you used a conversion service
The subconverter documentation states that conversion input can be supplied through a url parameter, and that file-path input is also supported. Submitting your original subscription to an online converter means the converter obtained that input. That fact alone does not prove the service stored, misused or leaked it.
| Link in the chain | What to record | What to check when cleaning up |
|---|---|---|
| Original provider input | Which subscription was submitted, identified by a masked label | Whether the token was rotated |
| Conversion request | Which conversion environment received which input | Whether your own configuration still references the old input |
| Conversion output | Whether you used a result file, an address or something else | Whether any old output is still distributed or used |
| Client-side copies | Which clients are associated with those inputs or outputs | Whether each was updated, and the verification result |
| Other retention | History, clipboard sync, backups, help-desk attachments you actually used | Whether copies still need removal |
The table defines a scope for checking. It does not assert that any particular conversion service stores anything.
“Unverified” is a real status
| Actual situation | Record it as |
|---|---|
| You did not test whether the old link still works | Old link status: not tested |
| You checked but kept no time or response | Checked; time and result not recorded, insufficient to re-verify |
| You checked and kept the result | Time, masked identifier and what you observed |
| You cannot see a third party's internal retention | Third-party retention: unverifiable |
“Not tested” is not “revoked”. “Not recorded” is not evidence of failure. One check supports one object, one time and one result.
Minimum material for support
- OS and client version.
- The exact error text and the time it occurred.
- The scope of impact: one site, one client, or everything.
- The single-variable tests you already ran and their results.
- An account identifier from inside the official ticket system, not a public group message.
Never send a password, a verification code or a full subscription URL in a public channel. Where you have no evidence for a claim, write that instead of filling the gap.
Getting the client itself
Download from the project's official release page and check the platform and version. An unfamiliar installer, a “special optimised build” or a browser pop-up recommendation is not an official release, and installing one creates a second, larger credential problem than the one you were solving.