Effective troubleshooting requires controlled variables: use the same configuration with another client, the same client with another configuration, and the same device on another network. Change one condition at a time and record the error time to isolate responsibility. Start with the easiest set to reproduce and stop expanding tests once a difference appears. Send the one changed variable and redacted logs to the relevant project or provider.
What does each of the three comparison tests rule out?
Prepare three comparisons: the original configuration in another client, another working configuration in the original client, and the original device on another network. Change one condition in each test and record the result.
- Can the same subscription be imported on another device?
- Can the same client import another configuration successfully?
- Can the subscription address be reached without a proxy?
- Did the error begin after upgrading the client or system?
Use a minimum configuration to isolate the client, configuration, or network
- Back up the current configuration and logs first
- Use a minimum configuration to test one node and one MATCH rule(See Configuration reference)
- Switch networks or use a hotspot to test subscription updates and node connections
- If the failure occurs only in one client, report it to that client project with the version number(See Client directory)
Changing DNS, TUN, rules, and nodes at the same time makes diagnosis harder
Redacted logs are more useful than a description in a public report
Contact the relevant service or configuration maintainer for subscription-provider problems