Short answer

SSR is the ShadowsocksR node format, often found in older subscriptions or providers maintaining legacy client compatibility. In real use, trust the provider subscription first and then verify whether the selected client core supports this exact type.

What It Means

In Clash/Mihomo configuration, ssr identifies the outbound type used by the node, policy or group. The same display name in a GUI can hide different transport fields, so the YAML or subscription output is more reliable than the node nickname.

Common Fields

type: ssr
server / port
cipher / password
protocol / protocol-param
obfs / obfs-param
udp

When to Use It

Older subscriptions still provide SSR nodes.
Useful for legacy clients or legacy profiles.
Relevant when a provider has not moved to SS, Trojan, VMess or VLESS.

Support Checks Checks

protocol, obfs and their parameters must all match.
Some modern clients hide or reduce SSR support.
Do not convert ssr nodes to ss by simply changing the type.

Minimal Shape

proxies:
- name: "ssr-node"
  type: ssr
  server: server.example.com
  port: 443
  cipher: aes-128-gcm
  password: "password"
  protocol: auth_sha1_v4
  obfs: tls1.2_ticket_auth
  udp: true

Compatibility Notes

Client support changes with the bundled core. A maintained Mihomo-based client usually supports more modern node types than historical Clash clients, but mobile clients and iOS alternatives still vary by app and release.

If a subscription contains this type but the client filters it out, switch to a compatible client, ask the provider for a compatible subscription format, or use a converter only when you understand what fields are being changed.

Official Reference

ShadowsocksR in Mihomo docs

ShadowsocksR Protocol