CloudStream “No Links Found” — Why It Happens and How to Fix It
Table of Contents
ShowHide
What the error actually means
CloudStream does not host anything. When you press play, this is what happens:
- The app asks your installed extension to find a playable link.
- The extension visits the source website it was written for.
- It reads that page and pulls out a video link.
- It hands that link back to the app to play.
“No links found” means step three failed. The extension went looking and came back empty.
- The source website changed its page layout, so the extension no longer knows where to look.
- The specific title is not on that source at all.
- The source is down, or blocked on your network.
- The extension is out of date and needs an update that already exists.
- Your app is not broken.
- Your installation is not corrupted.
- You do not need to reinstall CloudStream.
- Clearing your data will not help, and will cost you your library.
First, narrow it down
Two quick checks tell you exactly which fix you need. Do these before anything else.
- Open the title, and switch to another installed provider.
- It works? → one extension is broken. Skip to one provider fails.
- Still nothing? → continue to check 2.
- Pick something popular and mainstream.
- It works? → the first title simply is not available on that source. Nothing is broken.
- Still nothing? → that provider is down, or something wider is wrong. See every provider fails.
This takes about thirty seconds and saves you working through fixes you do not need.
The fixes, in order
Work down this list. Stop when it starts working.
- 1. Update all your extensions
This is the single most effective fix, and most people skip it.
- Go to Settings → Extensions.
- Tap Update all.
- Go back and try again.
Why it works: when a source website changes, the extension author usually pushes a fix within days. If you have not updated, you are running the broken version while the fix sits waiting.
Turn on automatic updates in the same screen so this happens on launch from now on.
- 2. Try a different provider
- Open the title.
- Switch providers using the selector.
- Different extensions read different websites, so one failing tells you nothing about the others.
This is normal behaviour, not a fault. Even a well-maintained setup will have individual providers failing on any given day.
- 3. Restart the app
- Close CloudStream completely — swipe it away from recent apps, not just press back.
- Reopen it and try again.
Clears stuck sessions and expired tokens, which cause this more often than you would expect.
- 4. Clear the cache
- Go to Settings → Apps → CloudStream → Storage → Clear cache.
- This is safe. It keeps your library, settings and extensions.
- Do not tap Clear data — that wipes everything.
- 5. Reinstall the extension
- Go to Settings → Extensions.
- Uninstall the failing extension.
- Install it again from the same repository.
Fixes cases where an extension updated badly or its files got corrupted.
- 6. Check whether the repository is still alive
If updating did nothing, the repository behind the extension may have been abandoned.
- Open its source page in a browser — GitHub, Codeberg or GitLab.
- Look at the most recent commit date.
- Within 3 months → actively maintained, not your problem.
- 6 months to a year → slowing down, expect failures.
- Over a year, or archived → dead. Replace it.
Active alternatives: repository list
- 7. Check your network and region
- Switch between Wi-Fi and mobile data. Some ISPs block certain source domains.
- Some sources are region-restricted. A VPN may change the result.
- Public, school and office networks block a lot of this by default.
- 8. Update CloudStream itself
- Extensions are built against current app versions.
- If you are several releases behind, newer extensions may not load properly.
- Get the current build: download CloudStream
Only one title fails
Everything else plays fine, but one film or episode returns nothing.
Most likely, it is simply not on that source.
- Use global search instead — the Search tab queries every installed extension at once.
- Try a provider that specialises in that content type or language.
- Very new releases often have no working sources yet.
- Very old or obscure titles may have none at all.
- For series, check whether the specific episode exists. Sometimes a season is incomplete.
This is not an error. No source has everything, and the app has no way to tell you “this title is not here” versus “I could not read the page”.
One provider fails on everything
That provider returns nothing regardless of what you pick, while your other providers work normally.
The extension is broken. In order:
- Update all extensions.
- Uninstall and reinstall that specific extension.
- Check whether its repository is still active.
- Check the repository’s issue tracker — if the source website shut down, someone has probably already said so.
- If it has been failing for weeks, remove it.
Remove dead providers rather than leaving them installed. The app queries every provider during global search and waits for each one to time out. A few dead extensions make every search noticeably slower.
Every provider fails
Nothing works anywhere. Usually something basic rather than something serious.
- Check your internet. Open a browser and load any page.
- Check you actually have extensions installed. Settings → Extensions. Repositories alone are not enough — you need extensions installed from them.
- Check the provider selector. If it still says None, nothing is installed.
- Switch networks. Wi-Fi to mobile data, or vice versa.
- Check the date and time on your device. A wrong clock breaks secure connections and causes exactly this.
- Disable a VPN temporarily if you use one. Some sources block known VPN addresses.
If none of that helps, add a fresh repository and install one extension from it as a test. If that works, your old extensions are the problem.
It worked yesterday
Very common, and there are only a handful of causes.
- The source website changed overnight. By far the most likely. Update extensions and wait for the fix.
- You updated the app. Plugin systems change between versions and extensions may need reinstalling. See extensions disappeared.
- The repository went down. Check its source page.
- Your ISP started blocking the domain. Test on mobile data.
- The source is having an outage. Try again in a few hours.
The most useful habit: when something breaks suddenly, wait a day before troubleshooting hard. A large share of these fix themselves through an extension update.
When it cannot be fixed
Being honest about this saves people hours of pointless effort.
- The source website shut down permanently. The extension has nothing left to read. No fix exists.
- The repository was abandoned. Its extensions will keep decaying. Replace it.
- The extension author stopped maintaining it. Fixes only come if someone else volunteers.
- The title was removed from every source you have. Nothing to find.
- Your region blocks the source at network level. A VPN is a workaround, not a fix.
The rule of thumb: if other providers work on the same title, the problem is that one extension. If no provider anywhere has ever had it, the content simply is not available to you through the sources you installed.
How to stop it happening so often
You cannot eliminate this — it is inherent to how the app works — but you can make it rare.
- Turn on automatic extension updates. Settings → Extensions. This alone prevents most cases.
- Install two providers for anything you care about. When one breaks, the other usually does not.
- Use maintained repositories. Check the commit date before adding one.
- Remove dead extensions promptly. They slow everything down and give you nothing.
- Set provider priority so your most reliable sources are checked first: source priority guide.
- Keep the app updated. Old builds lose extension compatibility.
- Keep three or four repositories, not twenty. More repositories does not mean more results — it means slower searches and more dead providers.