CloudStream Repository Won’t Add — Every Cause and Fix
The fastest fix: stop using the URL and type the shortcode instead. That alone solves most cases, because it removes every possible typing error.
The second most common cause: using a GitHub web page link instead of the raw JSON link. Those look almost identical but only one works.
Table of Contents
ShowHide
Which symptom do you have?
Different failures point to different causes. Find yours.
| What happens | Most likely cause | Go to |
|---|---|---|
| Nothing at all — the dialog just closes | Typo, or wrong URL type | Fixes 1–3 |
| An error or failure message appears | Host unreachable, or blocked | Fixes 4–5 |
| It adds, but shows no extensions | Repository is dead or moved | Empty list |
| The app hangs or freezes | Slow host, or app needs updating | Fixes 4 and 7 |
| It worked last week, not now | Repository shut down or moved | Worked before |
The fixes, in order
Work down the list. Stop when it adds successfully.
Use the shortcode instead of the URL
This is the fastest and most reliable fix.
- A shortcode is a few characters that the app expands into the full URL automatically.
- No long link to mistype, no hidden characters, no wrong URL type.
- Enter it in the same box where you would paste a URL.
- Shortcodes are case-sensitive — type them exactly as written.
Full list of shortcodes: CloudStream repositories
On a TV or Firestick this is not optional. Typing a long URL with a directional remote almost guarantees a mistake.
Check you are using the raw JSON link
The single biggest cause of silent failures.
- A repository is a JSON file. The app needs a link to the file itself, not to the web page displaying it.
- Raw links contain raw.githubusercontent.com, or a /raw/ segment.
- Web page links contain /blob/ and open in a browser as a formatted page.
- See right vs wrong URL below for the exact difference.
Check for typos and stray characters
- Copy-paste often picks up a trailing space or a line break.
- Delete anything after the final character of the link.
- Watch for autocorrect capitalising the first letter — links are case-sensitive.
- Make sure the link starts with https:// and nothing before it.
- If you typed it manually, retype it or switch to the shortcode.
Switch networks
- Some ISPs, DNS providers and public networks block GitHub raw content and similar hosts.
- Turn Wi-Fi off and try on mobile data, or the other way round.
- If it works on one network and not the other, that network is blocking the host.
- Changing your device’s DNS to a public resolver often fixes this permanently.
- If you use a VPN, try with it off — and if that fails, try with it on.
Test the URL in a browser
- Paste the exact link into any browser on any device.
- You should see raw text — lines of JSON code. That means the file exists and is reachable.
- A formatted web page? You have the wrong link type. Go back to fix 2.
- A 404 or “not found”? The repository has been deleted or moved.
- Nothing loads at all? The host is down or blocked on your network.
Confirm the repository still exists
- Open the project’s source page — GitHub, Codeberg or GitLab.
- Check whether it has been archived or deleted.
- Look at the most recent commit date. Over a year old usually means abandoned.
- Repositories move without notice, and old links stop working.
Update CloudStream
- Older app builds can fail on newer repository formats.
- Check your version: Settings → scroll to the bottom.
- Get the current build: download CloudStream
Restart the app and try again
- Close CloudStream fully — swipe it away from recent apps.
- Reopen and try once more.
- Clears stuck network states that occasionally block the request.
Right URL vs wrong URL
This trips up almost everyone, because the two links look nearly identical.
| Correct | Wrong | |
|---|---|---|
| Contains | raw.githubusercontent.com or /raw/ | /blob/ |
| Opens in a browser as | Plain text — lines of code | A formatted page with buttons and menus |
| Ends with | .json | .json (looks the same) |
| Works in the app | ✅ | ❌ |
How to get the right one from GitHub
- Open the repository page in a browser.
- Click on the .json file to open it.
- Look for a Raw button, usually at the top right of the file view.
- Click it. The page now shows plain text.
- Copy the address from your browser’s address bar. That is the link the app needs.
The quick test: if the page has GitHub’s interface around it, it is the wrong link. If it is just text on a plain background, it is the right one.
Or skip all of this and use the shortcode.
Nothing happens when you tap Add
The dialog simply closes and no repository appears.
- A silent failure is almost always a bad URL. The app could not reach a valid JSON file.
- Work through fixes 1 to 3 above.
- Check the repository list in Settings → Extensions — occasionally it did add and just did not refresh. Pull down to refresh, or leave and re-enter the screen.
- Try adding a known-good repository like cspr as a test. If that works, your original link is the problem, not the app.
It adds but the extension list is empty
The repository appears in your list, but opening it shows nothing.
- The repository is most likely dead. It exists as a file but has no working extensions left in it.
- Check its source page for recent activity.
- Some repositories are restructured and left as empty shells after the maintainer moves on.
- Remove it and use an active alternative: repository list
This is not something you can fix from your side. An empty repository is empty for everyone.
It worked before and now fails
A repository you have used for months suddenly stops adding.
- The maintainer moved it. Repositories relocate between GitHub, Codeberg and GitLab fairly often. Search for the current location.
- It was deleted or archived. Check the source page.
- The host had an outage. Try again in a few hours before assuming the worst.
- Your network started blocking it. Test on mobile data.
- You updated the app and the repository format is no longer supported. Unusual, but possible with very old repositories.
Already-installed extensions may keep working for a while even after the repository disappears — but they will stop receiving updates and will decay.
Where to find working repository links
- Our maintained list — CloudStream repositories, with shortcodes, checked regularly.
- The official project — the recloudstream organisation publishes the official extensions repository.
- The community wiki and Discord — where maintainers usually announce moves.
Be careful with:
- Random forum posts from years ago. Most of those links are dead.
- Sites that list fifty repositories with no dates. They are rarely re-checked.
- Anything asking you to download a file before giving you a link.
A useful habit: before troubleshooting a repository link at all, check when the source was last updated. If it has been quiet for a year, the link is not the problem — the project is.
When the repository is genuinely gone
Some things cannot be fixed, and recognising them saves time.
- The source page returns 404. It has been deleted. No workaround.
- The project is archived. It is frozen and will not be updated again.
- No commits for over a year. Treat it as dead even if the link still loads.
- The maintainer announced they had stopped. Believe them.
What to do instead
- Find an active repository covering the same language or category.
- Two or three maintained repositories will always beat chasing dead links.
- Remove the dead entry from your app — it slows down searches for no benefit.
