Topic guides

Proxy Provider Configuration Guide

Learn how to configure proxy-providers manually in Mihomo or Clash and check node sources.

Last updated
proxy provider generatorproxy-providers generatorclash provider generatormihomo provider config
On this page

When to use it

  • You want remote subscriptions as proxy-providers instead of inline proxies.
  • You need modular proxy source management in Mihomo or Clash configs.
  • You want the client to refresh providers on schedule.

Tip

The current node converter does not generate proxy-providers directly. Configure providers manually in the client configuration.

A node file and a main configuration do different jobs

A node file contains proxies. The main configuration decides where to load it, which groups use it and how traffic is routed. Adding an arbitrary subscription URL to proxy-providers does not convert a web page or another client format. Nodebuf can generate node content; the provider references below must be configured in your own Mihomo main file. The converter does not manage remote providers for you.

In Node Converter, choose Mihomo and node-only output for nodes you are authorized to use. For a structural exercise, save this fictional file as providers/demo.yaml relative to the main configuration directory. It cannot provide internet access:

proxies:
  - name: Provider-Demo
    type: ss
    server: 192.0.2.70
    port: 8388
    cipher: aes-128-gcm
    password: demo-password

Use this main configuration to reference that local file. No remote downloads or additional rule sets are involved:

mixed-port: 7890
allow-lan: false
mode: rule
proxy-providers:
  demo:
    type: file
    path: ./providers/demo.yaml
proxy-groups:
  - name: PROXY
    type: select
    use:
      - demo
rules:
  - MATCH,PROXY

use names the provider, demo; the rule names the group, PROXY. Neither is a node name. Preserve spelling and case. A desktop client may use its own configuration directory: leaving the provider in your Downloads folder will not necessarily satisfy this relative path.

Add remote updates after the local structure works

Following the Mihomo reference, an HTTP provider uses type: http plus a real HTTPS url, cache path and an interval measured in seconds. Its response must be a compatible node file, not a login page, error page or an unrelated full client configuration. Keep the cache within a directory the core permits.

The interval controls downloads; it is neither a latency test nor an availability guarantee. A provider's health-check is a separate configuration with its own destination, frequency and traffic costs. Downloading every few seconds is unnecessary for a source updated once a day.

Follow the references when a list is empty

  1. If downloading fails, inspect HTTP status, authentication, TLS and network reachability. Opening a share page in a browser is a different operation.
  2. If downloading succeeds but there are no nodes, inspect the root proxies key, supported protocols and whether the file accidentally contains only rules.
  3. If the provider has nodes but its group is empty, check use and any selection filters.
  4. If the group is populated but traffic does not use it, inspect the rule target and order. The final MATCH normally belongs last.

Remove demonstration nodes before use. A subscription URL may contain an access secret; screenshots, logs and public repositories can expose it. For a one-time combination of sources, see Clash subscription merging. Referencing providers and copying nodes into one file are different workflows.

Client reference