Docs Config Proxy Provider Content

Proxy Provider Content

Subscription files downloaded by proxy-providers support three formats — if you're building your own subscription server, you can generate a file in any one of these three formats.

YAML Format

Exactly the same format as writing proxies directly under proxies, just wrapped in a top-level proxies::

provider1.yaml YAML

proxies:
  - name: "ss1"
    type: ss
    server: server
    port: 443
    cipher: chacha20-ietf-poly1305
    password: "password"
  - name: "ss2"
    type: ss
    server: server
    port: 443
    cipher: chacha20-ietf-poly1305
    password: "password"

URI Format

One share link per line, matching the format most clients use for "scan/paste to import a single node":

provider1.txt URI

ss://YWVzLTI1Ni1nY206bWV0YUAxMjcuMC4wLjE6NDQz#home
vmess://eyJhZGQiOiIxMjcuMC4wLjEiLCJhaWQiOiIwIiwiYWxwbiI6IiIsImZwIjoiIiwiaG9zdCI6IiIsImlkIjoiMTIyMzQ1Njc4OSIsIm5ldCI6InRjcCIsInBhdGgiOiIiLCJwb3J0IjoiNDQzIiwicHMiOiJ2bWVzcyIsInNjeSI6ImF1dG8iLCJzbmkiOiIiLCJ0bHMiOiIiLCJ0eXBlIjoibm9uZSIsInYiOiIyIn0=

This format doesn't need a proxies: field — just one link per line.

Base64 Format

Base64-encoding that entire URI text again gives you the "subscription link" format most commonly used by proxy providers:

provider1.txt Base64

c3M6Ly9ZV1Z6TFRJMU5pMW5ZMjA2YldWMFlVQXhNamN1TUM0d0xqRTZORFF6I2hvbWUKdm1lc3M6Ly9leUpoWkdRaU9pSXhNamN1TUM0d0xqRWlMQ0poYVdRaU9pSXdJaXdpWVd4d2JpSTZJaUlzSW1ad0lqb2lJaXdpYUc5emRDSTZJaUlzSW1sa0lqb2lNVEl5TXpRMU5qYzRPU0lzSW01bGRDSTZJblJqY0NJc0luQmhkR2dpT2lJaUxDSndiM0owSWpvaU5EUXpJaXdpY0hNaU9pSjJiV1Z6Y3lJc0luTmplU0k2SW1GMWRHOGlMQ0p6Ym1raU9pSWlMQ0owYkhNaU9pSWlMQ0owZVhCbElqb2libTl1WlNJc0luWWlPaUl5SW4wPQ==

The YAML / URI / Base64 formats can't be mixed within the same file. URI and Base64 formats don't need a proxies: field — you can just write the content directly. The Base64 format is usually what providers give out as subscription link content for v2ray/xray clients, and you can use it directly as the url for a proxy-providers entry.