Back to home

Troubleshooting Guide

Clash subscription not working: how to fix import, refresh, and connection problems

Use this page when a Clash profile does not import, does not refresh, or loads successfully but still fails to connect.

Open Clash Guide Check Live Status Open Clash YAML

Correct Clash subscription URL

https://raw.githubusercontent.com/Au1rxx/free-vpn-subscriptions/main/output/clash.yaml

If your client supports refreshable remote profiles, this is the URL it should keep. If you only imported a downloaded file once, auto-refresh may never work.

Most common causes

  • The app expects a remote YAML profile but the link was imported incorrectly.
  • The profile was saved as a local one-time import instead of a subscription source.
  • The client is using stale cached nodes and needs a manual refresh.
  • The selected node is unhealthy and the status page was never checked.

What to verify first

  • The client is a Clash or Mihomo-compatible app.
  • The profile source is the raw Clash YAML URL.
  • The profile can still be refreshed manually.
  • The target region looks healthy on the live status page.

Step-by-step troubleshooting path

  1. Confirm the app actually supports Clash YAML remote profiles.
  2. Re-open the profile source and make sure the raw Clash URL is still saved.
  3. Run one manual refresh and verify that nodes update without errors.
  4. Switch to another region or node before rewriting DNS or routing rules.
  5. Check the status dashboard to see whether the problem is client-side or node-side.

When the Clash profile imports but still does not connect

Related guides