🔁Self-deployed Subconverter subscription conversion front-end and back-end (to address invalid conversions due to too many rulesets and security concerns)
The article discusses self-deploying Subconverter for subscription conversion to address issues like invalid conversions due to excessive rulesets and security concerns. It covers problems with most subscription conversions, steps for backend and frontend deployment, including forking the project, changing domain names, setting parameters, and testing the solution. Additionally, it mentions a self-use subscription rule repository and optional modifications for convenience.
✨
For subscription conversions, there will be Many people feel that converting a subscription with someone else's backend has certain data pitfalls and inability to customize it So today is the day. Self-deploying Subconverter subscription conversions The tutorial.
📝 Main content
1. Problems with most subscription conversions
The main purpose is to address the back-end of others A common problem , since most of the default rules are used, the upper rule set number parameter is kept at the default of 64, which means that when you rule set more than that, it will be Won't use your rules, but rather the default rules
2. Subscription conversion back-end
1. Fork the project and Run
2. Just change the domain name of the subscription conversion link to the domain name of REPLIT.
3. Subscription conversion parameters
💡
Optimization with Rule Providers (Clash Premium core only)
expand The default is false It is recommended that the url end with &expand=false Useful for optimizing rule matching performance
⚠️
expand The parameters are currently problematic when classic is the default false When this is done, the original rule of no-resolve disappearance , resulting in the final rule set facing DNS leaks and contamination risks
classic The default is false ( classical formalized Not conducive to optimizing performance But its wouldn't make The original rule of no-resolve (disappearance)
Used to set whether or not to generate a Clash classical rule-provider
expand
selectable
true / false
Used for processing or transforming Surge, QuantumultX, Clash's rule lists on the API side, i.e. whether to put the full text of the rules into the subscription or not, default is true, set to false will not write the full text of the rules into the subscription.
⚠️
Found to exist as with other backends, there may be issues with automatic subscription updates failing, but manual updates working (exact reason unknown)
4. Test the effectiveness of the solution to the problem of invalid conversion due to too many rule sets
Most subscription conversion backends are unable to use their rules correctly, but after modifying the max_allowed_rulesets After the parameter Can be loaded normally
5. Self-use subscription rule repository (available for reference)
The subscription conversion front-end generates a pure front-end implementation, so you can use someone else's front-end and then use your own back-end
1. Subscription conversion front-end deployment
Front-end for subscription conversions Wasted performance and easy exposure of personal backends So. Not built in with the back end
Note that the default version of Vercel is Node.js 18 and needs to be changed to 16
2. Add a self-built backend, add environment variables (easy to modify, but changes need to be manually redeployed) or modify the parameters in the GitHub personal fork repository
