ErrorVaultHQ

Solved Error

How to Fix: 'Source error: java.net.ConnectException: Failed to connect to /127.0.0.1:11470' in Stremio

Quick Fix

This error means Stremio can't reach its built-in streaming server. Restarting the app restarts the server, which clears the error in most cases. On Android, Android TV and Fire TV the server is part of the Stremio app, so there is nothing extra to install.

  1. 1Force stop Stremio. On Android, Android TV or Fire TV: open Settings > Apps > Stremio > Force stop. On a PC, quit Stremio completely.
  2. 2Reopen Stremio. Launch the app again and try to play a stream.
  3. 3Check the server status. Open the server or streaming settings in Stremio. If the status still says Error, follow the Cause that matches your setup below.

What this error means

Stremio plays most streams through a small streaming server. By default it runs on the same device at 127.0.0.1 on port 11470. This error means the player tried to reach that server and got no answer. The server may not be running, may have crashed, may be blocked, or may be on another device that can't be reached. It is not a Java problem on your device, and it usually isn't a problem with the movie source itself.

Likely Causes

  • Local streaming server stopped or never started. On Android TV, Fire TV and Chromecast, the built-in server can fail to start after a cold boot or a new app version. The settings then show an Error status.
  • Remote server unreachable on the LAN. When another device is the server, it may be asleep or blocked by a firewall. A guest network or AP/client isolation on the router can also hide it from the other device.
  • Desktop networking conflict. On Windows, v5 showed an Error server status in one report that began around the time Docker was installed for WSL. A proxy, firewall or antivirus can also block local port 11470.
  • A specific source stalls the server. Some Usenet (NNTP) streams make the internal server accept a request and then never answer.

Step-by-Step Guide

Cause 1: The streaming server isn't running on the device you're using

  1. 1Force stop and relaunch. On Android, Android TV or Fire TV: go to Settings > Apps > Stremio > Force stop, then open Stremio again. One Chromecast with Google TV user who powered the TV off nightly got the error on the first launch of the day. Force stopping and reopening fixed it for that session.
  2. 2Restart the server from Stremio's settings. On Android TV or Fire TV: open Settings > Server in Stremio and check the status. If it says Error, turn on Run in the background. Stremio restarts, and one user saw the status change to Connected and playback work again. Another user in the same thread pointed out that the restart is what helps, not the toggle itself.
  3. 3Check the server status on desktop. On Windows, macOS or Linux: open Settings > Streaming and look at the Streaming server status for http://127.0.0.1:11470. If it shows Error, quit Stremio completely and reopen it.
  4. 4Install Stremio Service if the app asks for it. On Windows, macOS or Linux: if Stremio shows a banner saying the streaming server is not available, install Stremio Service from the link in that banner (www.stremio.com/download-service). Make sure it is running afterward. Don't do this on Android, Android TV or Fire TV, because the server is built into the app there.
  5. 5Restart the device. Restart the phone, TV box or PC, then open Stremio again. If the error keeps coming back, clearing Stremio's app data in your device's app settings is a last resort: you will have to sign in again, and one Fire TV Stick user found it helped only until the next day.
  6. 6Update Stremio. Install the latest Stremio version for your platform. Several reports of this error are tied to specific app versions, so a newer release may behave differently.
  7. 7Reinstall Stremio. If nothing above works, uninstall Stremio and install it again from the official source. On desktop, also reinstall Stremio Service if you use it.

Cause 2: Another device on your network is acting as the streaming server

  1. 1Make sure the server device is on and awake. The PC, NAS or mini-PC that runs the streaming server must be powered on and not asleep. If it is off, the TV or phone can't connect.
  2. 2Copy the exact server address. On the server PC: open Stremio and go to Settings > Streaming. Note the Streaming Server URL. It looks like http://192.168.x.x:11470. Enter that exact address in the Streaming settings on the other device.
  3. 3Test the server from a browser on the server PC. On the server PC: open a browser and go to http://localhost:11470. If the page doesn't open, the service isn't running or something on the PC is blocking it, such as a proxy, firewall or antivirus.
  4. 4Test the server from another device. On a phone connected to the same network, open http://PC_IP:11470, replacing PC_IP with the server PC's local IP. If it doesn't load, the problem is in the network or firewall, not Stremio.
  5. 5Allow port 11470 through the firewall. On the server PC: add a firewall rule that allows inbound connections on port 11470 from devices on your local network. If you turn the firewall off to test, turn it back on afterwards and add the allow rule instead.
  6. 6Check for guest Wi-Fi or AP/client isolation. Make sure both devices are on the same network. A guest Wi-Fi network, or AP/client isolation enabled on the router, stops devices from seeing each other even when both show the same Wi-Fi name. Move both devices to the main network or turn isolation off in the router settings.
  7. 7Check the Docker container. If the server runs in Docker on a NAS or mini-PC: confirm the container is running and that port 11470 is published, for example 11470:11470. If the container has crashed, nothing is listening on 11470.

Cause 3: The error started after installing Stremio v5, Docker or WSL

  1. 1Look at the server status. On Windows: open Settings > Streaming in Stremio v5. In one reported case the default URL http://127.0.0.1:11470 showed Error, even though the same URL worked in Stremio v4 on that PC.
  2. 2Close Docker Desktop and WSL, then restart Stremio. On Windows: quit Docker Desktop completely and relaunch Stremio. In the reported case, the problem started around the time Docker was installed for WSL. Closing Docker or reinstalling Stremio did not fix it for that user, so this may not work for you.
  3. 3Check whether something is blocking local port 11470. Open http://127.0.0.1:11470 in a browser on the same PC. If the page doesn't open, a Stremio developer said something on the PC is blocking the streaming service, such as a proxy, firewall or antivirus. Check those, and check any VPN or virtual network software.
  4. 4Report the bug. If it still fails, report it on the Stremio/stremio-bugs GitHub tracker with your Stremio version and whether Docker or WSL is installed. The Docker and WSL conflict is a reported issue there.

Cause 4: Only certain streams or Usenet sources hang

  1. 1Try a different stream. If only one stream fails, go back and pick another source or release of the same title. If another source plays, the problem is the original source, not your setup.
  2. 2Know that some Usenet streams can stall the server. A GitHub report describes Stremio's built-in Usenet (NNTP) streaming hanging on certain NZB releases. The streaming server at 127.0.0.1:11470 accepted the request and then never replied, with no error. Other releases from the same provider played fine.
  3. 3Check your provider outside Stremio. Test your Usenet provider and indexer login in another download client, such as SABnzbd. In the report above, the provider worked in other tools, which shows the hang came from the stream or Stremio, not the account.
  4. 4Switch to another release or provider. Pick a different release, or a different Usenet provider if you have one. Another report found freezes with providers on one particular backbone, while other providers worked.

When to seek further help

If the error keeps coming back on every stream, report it on Stremio's official GitHub issue tracker (Stremio/stremio-bugs). Include your platform, your Stremio app version and the exact error text. Say what the server status shows in the settings (for example Error). Mention whether you use a separate server such as a PC, NAS or Docker container. Similar reports are open there, including on Android TV and Fire TV.

Heads up: this guide was drafted with AI assistance from the real sources listed below, and structured by our team for clarity. It may not cover every possible cause — if it doesn't fix your issue, let us know and we'll take a closer look. See how we create our fixes.

Was this fix helpful?

Related Error Fixes