This guide covers one task in OpenWrt LuCI: adding a single vmess:// sharing link to OpenClash v0.47.156 with the Mihomo core. It does not describe the import screens in Clash for Windows, Clash Verge Rev, or FlClash. Older OpenClash releases may expose different labels or parsing behavior.

A vmess:// link normally describes one VMess proxy and can contain its server, port, UUID, transport, and TLS parameters. An https:// subscription is a remote endpoint that OpenClash can fetch and update. Pasting a node link into a field that expects a downloadable URL does not turn it into a remote profile.

InputWhat it isUse in this guide
vmess://…One VMess node sharing linkEnable online conversion, or import it locally in the server-node editor
https://…Remote subscription or configuration URLUsually add it directly under Config Subscribe
.yaml / .ymlAn existing configuration fileUse configuration upload or management; it is outside this article

Two supported paths:online conversion is convenient but gives the link to a conversion service. The local importer in v0.47.156 parses the link in the LuCI page and fills the node form without a third-party conversion service. Prefer the local path for private or self-hosted nodes.

Treat a complete VMess sharing link like a password. Do not paste it into public search, a forum, an online YAML checker, or a troubleshooting screenshot. This article uses only a redacted placeholder:

Redacted examplevmess://REDACTED
  1. Confirm that the link comes from a server or provider you trust and are authorized to use.
  2. Record the active profile name, OpenClash status, and a node that currently works.
  3. If considering online conversion, identify who operates the converter and what it logs. Use local import when that cannot be verified.
  4. If the link has already been exposed, revoke or rotate its credentials before importing it.

A one-node link still contains credentials:the VMess UUID is authentication data. The server hostname, port, SNI, WebSocket Host, and path can also be sensitive. Hiding only the display name is not redaction.

Method 1: enable online conversion under Config Subscribe

The OpenClash v0.47.156 subscription editor states that Subscribe Address accepts SS, SSR, VMess, and other node links when Subscribe Convert Online is enabled. The selected converter receives the link, so this path is appropriate only with a converter you operate or have evaluated.

  1. Open Services → OpenClash → Config Subscribe and create a separate test entry, or edit an entry intended for this node.
  2. Give it a recognizable alias and place one complete vmess:// link in Subscribe Address. Do not mix it into a working subscription for the first test.
  3. Enable Subscribe Convert Online and select a verified Convert Address. A preset in the interface is not a privacy endorsement.
  4. Save, return to the subscription list, and update that row, or use Update Config at the bottom. Update Config commits the settings, enables OpenClash, and starts it, so a brief interruption is possible.
  5. Wait for completion, confirm that a profile and VMess node were produced, then run the checks below.

The interface explicitly warns about privacy leakage:online subscription conversion is not an offline router operation. Do not submit the link when the conversion service cannot be trusted.

Method 2: import the sharing link in the local node editor

OpenClash also has a server-node editor. In v0.47.156 it displays SS/SSR/VMESS/TROJAN URL with an Import button, then prompts for a sharing link. Its page source calls parseVmess in browser-side JavaScript and populates the form. This import action does not require a third-party converter, although saving still stores the resulting credentials in the router configuration.

  1. Open Services → OpenClash → Config Manage. On the target YAML row, choose Servers Manage under Actions and select Apply.
  2. On Servers & Groups manage, select Read Config before editing, as the page itself requires, then add one item under Proxies.
  3. Open the new item, select Import on the SS/SSR/VMESS/TROJAN URL row, and paste one complete vmess:// link. Success confirms parsing only, not connectivity.
  4. Confirm that Config File still names the configuration selected earlier. Choose all configurations only when that is intentional.
  5. Select an existing Proxy Group for the target configuration. Do not invent a group name that has not been created.
  6. Review every field and select Commit Settings. Back on Servers & Groups manage, select Apply Settings to write the node to the target YAML, then reload the active runtime configuration.

Local import fits a private single node:it avoids sending the raw link to a conversion service, and the node is not treated as an auto-updating subscription. Credential changes must be edited or re-imported manually.

Verify the VMess fields before saving

The v0.47.156 importer first handles common V2RayN Base64 JSON links and then tries a URI-style VMessAEAD form. It maps known fields and can place some unknown scalar values under other parameters, but it does not reconstruct every unknown object. Compare the result with the server settings and the Mihomo VMess reference.

CheckCommon source keysTypical failure
Server, port, UUIDadd, port, idResolution, connection, or authentication failure
Cipher and Alter IDscy / encryption, aidHandshake failure; do not guess a replacement
TLS, SNI, fingerprinttls / security, sni, fpTLS or certificate error
Transportnet / typeTCP, WebSocket, HTTP/2, or gRPC mismatch
Path, Host, service namepath, host, serviceNameServer is reachable but protocol request fails
Profile and group scopeOpenClash form choicesSaved node is absent from the active profile or group

Check the certificate-verification default:the v0.47.156 new-node form defaults skip-cert-verify to true, while the VMess importer does not actively set it to false when the link lacks an insecure parameter. If the trusted source configuration does not require bypassing verification, change it to false before saving. Do not treat the form default as a server requirement.

Apply once, then verify the node and a real connection

  1. After saving the subscription or server node, update or apply the configuration once and wait for OpenClash to return to a running state.
  2. Read the first profile-parsing, group, or VMess error in the startup log. Do not repeatedly start updates.
  3. Confirm that the new node appears in the intended profile and group. If it is absent, check scope and group selection before changing TLS.
  4. Select the new node manually and make one real request. Confirm the final node and error type in the connection log.
  5. Switch back to the previously working node and test again to separate new-node parameters from a router-wide network problem.

A successful latency check only shows that its health-check target was reachable at that moment. Completion means OpenClash starts, the node appears in the intended profile and group, a real request uses it, and the previous node remains available as a fallback.

Visible but unable to connect:compare UUID, port, TLS, SNI, and transport with the server first. Do not change DNS, Fake-IP, TUN, core, and proxy mode at the same time.

Troubleshoot and roll back only this new item

SymptomCheck firstNext action
Subscription update failsOnline conversion is disabledUse a trusted converter or switch to local import
Local import reports an invalid formatThe link is complete and begins with vmess://Copy it again from the trusted source; do not expose decoded data
Parsing succeeds but no node appearsConfig File and Proxy Group choicesSelect the active profile and an existing group, then apply
The node appears but cannot connectServer, UUID, TLS, SNI, and transportCompare fields with the server and change one variable at a time
OpenClash fails after the updateThe first startup parse errorRemove this new item and restore the previous profile

For a local-import rollback, delete only the new server node, return to Servers & Groups manage, and select Apply Settings again so the removal is written to the target YAML; then reload the runtime configuration. For online conversion, switch to the previously recorded active profile before disabling or deleting the test Config Subscribe entry. That does not delete a generated YAML file. If the file was created only for this test, confirm it is not active, download a backup, and remove it separately in Config Manage. Do not delete the original subscription or clear every node.

If the link was sent to an untrusted converter, deleting it from OpenClash cannot retract that disclosure. Rotate its UUID or regenerate credentials at the server or provider. The site's download page lists related OpenClash and Mihomo entry points, but changing clients cannot correct wrong VMess parameters.

Official sources and version scope

Version numbers, filenames, and interface labels can change. Confirm them in the linked project documentation before making changes.