Simturax

Possible Causes:

• Stremio isn’t running or you’re not logged in
• The manifest URL is malformed or incomplete
• Browser-to-Stremio communication is blocked

Solutions:

1. Verify Stremio is running – Ensure the Stremio desktop or web app is open and you’re logged into your account.
2. Use the correct installation method – Click the “Install in Stremio” button directly from the configuration page. Do not copy the URL unless the automatic method fails.
3. Manual installation (fallback) – If automatic installation fails:
   • Copy the generated manifest URL from the configuration page
   • Open Stremio
   • Navigate to Addons (puzzle icon) → + Add Addon
   • Paste the URL and click Add
4. Browser compatibility – Try using a different browser (Chrome, Firefox, Edge). Some browsers block the stremio:// protocol handler.
5. Clear Stremio cache – In Stremio, go to Settings → Advanced → Clear Cache, then restart the app and try again.

Possible Causes:

• No debrid service configured and P2P is blocked
• Torrent providers are disabled
• Network restrictions (firewall, ISP blocking)

Solutions:

1. Add a debrid service – The most reliable fix:
   • Go to the Magnetio configuration page
   • Navigate to the Debrid Services section
   • Add your API key for Real-Debrid, Premiumize, AllDebrid, or TorBox
   • Reinstall the addon with the updated configuration
2. Enable P2P fallback – If you prefer not to use debrid:
   • Ensure you haven’t disabled P2P torrent sources
   • Check that your torrent providers are enabled in the configuration
3. Configure a VPN/SOCKS5 proxy – For P2P streaming, enable the Privacy Proxy section and enter your proxy details to mask your IP.
4. Check network restrictions – Some ISPs block torrent traffic. Test with a VPN or try connecting from a different network.
5. Verify provider selection – On the configuration page, confirm that at least one torrent provider is selected. If none are selected, no results will be returned.

Possible Causes:

• Slow internet connection
• P2P streaming without a debrid service (seeding limitations)
• Poor quality settings
• Network congestion

Solutions:

1. Use a debrid service – This is the most effective fix. Debrid services provide direct HTTP streams at full speed with no buffering. Add your API key to the configuration.
2. Check your internet speed – Run a speed test. For HD streaming, you need at least 5-10 Mbps. For 4K, you need 25+ Mbps.
3. Adjust quality filters – Lower your resolution preferences:
   • In the configuration, set Quality Filters to 720p or 1080p instead of 4K
   • You can also filter by file size to avoid very large files
4. Enable background prewarm – This feature automatically adds uncached torrents to your debrid service for future viewing:
   • Set prewarm=1 in the configuration
   • Set prewarmLimit to a reasonable number (e.g., 3-5)
5. Close other bandwidth-heavy apps – Pause downloads, streaming, or gaming on other devices in your network.
6. Restart your router and streaming device – A simple restart can resolve network congestion issues.

Possible Causes:

• Incorrect API URL or key
• Jackett/Prowlarr not running or inaccessible
• Firewall blocking connections

Solutions:

1. Verify the Torznab API URL format – The URL must follow this structure:

   http://<jackett-host>:<port>/api/v2.0/indexers/<indexer-name>/results/torznab/

   Example: http://jackett:9117/api/v2.0/indexers/all/results/torznab/
2. Test the connection – Open the URL in a browser. If the page loads a blank or XML response, the connection is working.
3. Check Jackett/Prowlarr is running – Ensure the service is active and accessible from your Magnetio server:
   • If self-hosting, verify the container is running: docker ps
   • Check logs: docker compose logs jackett
4. Validate your API key – Double-check that you’ve copied the correct API key from Jackett/Prowlarr. There should be no extra spaces.
5. Network reachability – If you’re using Docker, ensure both Magnetio and Jackett are on the same Docker network. If not, use the container name instead of localhost.
6. Firewall/port blocking – Ensure the port (default: 9117 for Jackett) is open and not blocked by your firewall.

Possible Causes:

• No subtitle language selected
• ffsubsync not running (self-hosted)
• Stremio player settings

Solutions:

1. Configure subtitle languages – On the Magnetio configuration page, navigate to the Subtitles section and select your preferred languages (e.g., en for English, es for Spanish).
2. Check the subtitles resource – Magnetio provides a dedicated Stremio subtitles resource. Ensure it’s enabled and appears in your addon list.
3. Verify ffsubsync (self-hosted only) – This service syncs subtitles to the audio:
   • Check if the ffsubsync container is running: docker ps | grep ffsubsync
   • Check logs: docker compose logs ffsubsync
4. Manual subtitle selection – Within the Stremio player:
   • Click the subtitle icon (speech bubble)
   • Select “Search for subtitles” or choose from the available list
5. Reinstall the addon – Sometimes a reinstall with updated subtitle preferences resolves the issue.
6. Check Stremio subtitle settings – In Stremio, go to Settings → Subtitles and ensure subtitles are enabled and the default language is set correctly.

Possible Causes:

• Port conflicts
• Incorrect environment variables
• Missing dependencies
• Redis connectivity issues

Solutions:

1. Check port conflicts – The addon uses port 7000 and the scraper uses port 8080. Ensure these ports are not in use:

   netstat -tulpn | grep 7000 netstat -tulpn | grep 8080

   If in use, change the ports in your .env file or stop the conflicting service.
2. Verify environment variables – Check your .env file:
   • ADDON_PUBLIC_URL must be a valid HTTPS URL (e.g., https://magnetio.yourdomain.com)
   • No trailing slashes or special characters
3. View container logs – This is the most useful diagnostic command:

   docker compose logs

   Look for specific error messages (e.g., “connection refused”, “port already in use”).
4. Redis connectivity test – Redis is critical for caching and session management:

   docker compose exec addon redis-cli -h redis ping

   This should return PONG. If it fails, check your Redis configuration and network settings.
5. Update Docker – Ensure Docker and Docker Compose are up to date:

   docker --version docker compose --version

   If outdated, update your Docker installation.
6. Full restart – Stop everything and start fresh:

   docker compose down docker compose up -d

7. Check disk space – Insufficient disk space can prevent containers from starting. Check with:

   df -h

Possible Causes:

• No HTTPS configured (Stremio requires it)
• Self-signed certificates (not supported)
• Certificate expiration or invalidity

Solutions:

1. Understand the requirement – Stremio mandates that addon manifests use https://. HTTP will not work.
2. Use Caddy – The simplest automated solution:
   • Install Caddy and point it to your Magnetio service
   • Caddy automatically provisions and renews SSL certificates
   • Example Caddyfile:

     magnetio.yourdomain.com { reverse_proxy localhost:7000 }

3. Use Cloudflare Tunnel – If you’re behind a firewall or don’t want to expose ports:
   • Install cloudflared
   • Run: cloudflared tunnel --url http://localhost:7000
   • Cloudflare provides a secure HTTPS URL automatically
4. Purchase an SSL certificate – For manual configuration, buy a certificate from a trusted CA (e.g., Let’s Encrypt is free).
5. Important: Self-signed certificates will NOT work – Stremio’s security model rejects self-signed certificates. You must use a certificate from a trusted Certificate Authority.
6. Check certificate validity – Ensure your certificate is not expired:

   openssl x509 -in /path/to/cert.pem -text -noout | grep -A2 "Validity"

Possible Causes:

• Too many providers enabled
• High scraper concurrency
• Resource constraints on your hardware

Solutions:

1. Limit concurrent scrapers – In the configuration, reduce the number of concurrent providers from 4 to 2 or 3.
2. Disable unused providers – Only keep the torrent providers you actually use. Each enabled provider adds to the scraping load.
3. Reduce result limit – Lower the limit parameter from 10 to 5 or even 3. This reduces the workload on the scraper.
4. Adjust timeout settings – Lower the scraper timeout from 22 seconds to a faster value like 10-15 seconds if you have a fast internet connection.
5. Upgrade your hardware – If running on a Raspberry Pi, consider moving to a more powerful device like an Intel NUC or a cloud VPS.
6. Monitor resource usage – Check Docker container resource usage:

   docker stats

   Identify which service is consuming the most resources and investigate accordingly.

Possible Causes:

• Configuration changes not applied
• Browser cache issues
• Stremio caching the old manifest

Solutions:

1. Reinstall the addon – This is the most reliable fix:
   • Go back to the configuration page
   • Make your changes
   • Click “Install in Stremio” again
   • Confirm the installation – it will replace the existing version
2. Clear browser cache – Your browser may be caching the old configuration page. Try:
   • Hard refresh: Ctrl + F5 (Windows/Linux) or Cmd + Shift + R (Mac)
   • Or use incognito/private browsing mode
3. Clear Stremio cache – In Stremio:
   • Go to Settings → Advanced → Clear Cache
   • Restart Stremio
4. Uninstall and reinstall completely – If the above fails:
   • In Stremio, go to Addons → find Magnetio → click the trash icon
   • Reinstall from the configuration page
5. Force refresh the manifest – Stremio caches addon manifests. Wait a few minutes or restart Stremio to force a refresh.