Successful import means only that the client read some content. Confirm that the configuration includes proxies, proxy-groups, and rules and that its format is compatible with the current core. Reimport the address as a complete configuration and ask the provider to generate a format readable by your current core. A rule-provider file belongs in the rule-set interface, not the subscription interface.
Confirm that you imported a complete proxy configuration
Open the subscription preview and search for proxies and proxy-groups. If there are 0 nodes or a group references missing names, the problem is in the returned content, not the proxy switch.
- Does the configuration contain a proxies array?(See Outbound proxy configuration)
- Does proxy-groups reference existing node names?(See Rule configuration)
- Does the final item in rules provide a fallback?
- Did the client import the subscription as a rule set instead of a proxy configuration?
Make nodes and policy groups reappear on the Proxies page
- Open the configuration preview or logs and confirm the proxies count
- Check that node names referenced by policy groups use identical spelling
- Confirm that the subscription is a proxy configuration, not a standalone rule-provider
- Use a client that supports the configuration format, or ask the provider to convert it
Empty nodes usually indicate a problem with the configuration or subscription response
Clients use different names for remote configurations, overrides, and profiles
Do not manually change subscription URL parameters other than the token unless the provider instructs you to