Skip to content

Troubleshooting

Current released packages (Stable 1.2.3 and Beta 2.0.0-beta.2) use the Kodi menu name NZB-DAV. In those builds, choose that name wherever these instructions show NeNeTeePee-Stream-Kodi. Renamed source builds use the new name.

Start with the section that matches what you see. Work through the steps in order.

Redact secrets before sharing logs

Remove API keys, passwords, tokens, private hostnames, and full NZB URLs from any log you post publicly. NeNeTeePee-Stream-Kodi redacts credentials in its own log lines, but other add-ons and Kodi itself may not.

Finding NeNeTeePee-Stream-Kodi in kodi.log

Renamed source builds use the log prefix NeNeTeePee-Stream-Kodi:. Stable 1.2.3 and Beta 2.0.0-beta.2 use NZB-DAV:. Search for the prefix used by your installed build. Kodi writes kodi.log to its temp folder (/storage/.kodi/temp/kodi.log on CoreELEC and LibreELEC). Some detail, such as the filter summary, is logged only when Kodi's debug logging is on (Settings → System → Logging).

NeNeTeePee-Stream-Kodi stopped updating

If you installed NeNeTeePee-Stream-Kodi from the old NZB-DAV Repository (legacy) (https://appz4fun.github.io/nzbdavkodi/), you won't get any more updates. That address no longer supplies add-on metadata.

To fix it, install the Appz4Fun repository and move NeNeTeePee-Stream-Kodi over to it. The steps are in Upgrading from the legacy Kodi repository. Your settings are kept.

A manual zip install never updates on its own. Use the same steps to move it onto a repository.

Return from the beta channel to the stable channel

Kodi never downgrades an add-on automatically. If you're on 2.0.0-beta.x, switching to the Stable channel won't bring back 1.2.3 by itself.

  1. Make sure the Stable repository add-on (Appz4Fun Repository) is installed.
  2. Open Settings → Add-ons → My add-ons → Video add-ons → NeNeTeePee-Stream-Kodi and choose Versions. Pick 1.2.3 from Appz4Fun Repository.
  3. Uninstall the Appz4Fun Repository (Beta) add-on. While it's installed, the beta build stays in the Versions list, and it's easy to reinstall it by accident.

Settings that are new in 2.0.0 aren't in 1.2.3. For example, the NZBGet backend, the read-ahead buffer, and the fallback submit delay don't exist there. See Beta channel and beta features.

NeNeTeePee-Stream-Kodi doesn't appear in TMDBHelper

TMDBHelper lists NeNeTeePee-Stream-Kodi only after NeNeTeePee-Stream-Kodi's player file is installed.

  1. Open My add-ons → Video add-ons → NeNeTeePee-Stream-Kodi → Configure → Player Installation, then select Install TMDBHelper Player. You can also open the add-on itself and pick Install TMDBHelper Player from its menu.
  2. Wait for the notification. Player installed to: TMDBHelper means it worked. Failed to install to: TMDBHelper means the write failed.
  3. Restart Kodi, or run Players → Update players in TMDBHelper.
  4. Confirm the player file exists at special://profile/addon_data/plugin.video.themoviedb.helper/players/nzbdav.json. On CoreELEC that's /storage/.kodi/userdata/addon_data/plugin.video.themoviedb.helper/players/nzbdav.json.
  5. Check kodi.log for these messages:
    • NeNeTeePee-Stream-Kodi: Installing player to TMDBHelper at …: the install started.
    • NeNeTeePee-Stream-Kodi: Player installed successfully: the file was written.
    • NeNeTeePee-Stream-Kodi: Player already installed at schema v…; preserving existing file: a current file was already there, so it was left alone.
    • NeNeTeePee-Stream-Kodi: Refusing to install player outside addon_data or NeNeTeePee-Stream-Kodi: Failed to install player: …: the install was blocked or failed.

Installing the player also switches on a TMDBHelper setting (only_resolve_strm) so that TMDBHelper runs NeNeTeePee-Stream-Kodi's script player directly. If you reset TMDBHelper's settings, run Install TMDBHelper Player again.

Placing the player file by hand is an advanced recovery step. Use it only if the button and the player refresh both fail.

TMDBHelper opens but the picker never appears

Confirm TMDBHelper is actually using NeNeTeePee-Stream-Kodi for the item type you chose.

  1. Open TheMovieDb Helper → Configure → Players.
  2. Set Default player (Movies) to NeNeTeePee-Stream-Kodi.
  3. Set Default player (TV Shows) to NeNeTeePee-Stream-Kodi.
  4. If the default is Choose, pick NeNeTeePee-Stream-Kodi from the player dialog.
  5. Reinstall the player file and refresh players.

If TMDBHelper calls NeNeTeePee-Stream-Kodi but Kodi returns immediately, collect the kodi.log lines around the play attempt.

No results, or every result is filtered out

If you see No results found for …, no search provider returned anything. Check the search backend first:

  1. Confirm NZBHydra2, Prowlarr, or your direct indexers are reachable from the Kodi device.
  2. Run the matching test action and read the notification:
    • Test NZBHydra Connection or Test Prowlarr Connection: … connection OK means it works. …: unexpected response means the server answered but didn't accept the request, often because of a wrong API key. … URL not configured means the URL is empty. Any other message is the connection error itself.
    • Test Direct Indexers: Direct indexers OK: n/n means every enabled indexer answered. Direct indexers failed: … names the first failure.
  3. For Prowlarr, fill in Prowlarr Indexer IDs (comma-separated). NeNeTeePee-Stream-Kodi skips the Prowlarr search when it's empty.
  4. Search results are cached for Cache duration (Advanced → Search Cache, default 60 s). After you fix a provider, open the NeNeTeePee-Stream-Kodi add-on, choose Clear Cache, and search again.
  5. Try a popular movie or episode that you know has a Usenet release.

If the search found results but your filters rejected all of them, the picker opens straight into its show-all view, with the header Showing all N sources (filters off). Each rejected row carries a FILTERED: tag that names the first filter that rejected it (resolution, HDR, audio, codec, language, keyword, group, or size). Loosen that filter. If some results do pass, press C (the context-menu key) in the picker to switch between filtered and all results. On Linux and CoreELEC, you can also hold OK for five seconds to turn the filters off.

The Other / Unknown option in each filter group lets through releases whose title doesn't name a recognized value. Turning it off, or turning off SDR, often removes more than you expect. See Quality filtering.

nzbdav submission waits too long or fails

Check nzbdav before you change any NeNeTeePee-Stream-Kodi settings.

  1. Run Test nzbdav Connection. It reads nzbdav's queue with your API key.
  2. Confirm the API Key in the NeNeTeePee-Stream-Kodi Playback backend settings matches nzbdav's key.
  3. In the nzbdav UI, check whether the job was accepted, failed, or is still queued.
  4. If nzbdav reports a failed import or missing articles, pick another release.

A slow submit isn't always a failure. nzbdav fetches and parses the NZB before it replies, which can take a while on a large remux. NeNeTeePee-Stream-Kodi waits up to NZB submit timeout (seconds) (Advanced → Polling, default 300) and takes over a job that nzbdav accepted slowly.

Messages you may see:

  • nzbdav rejected the submission (HTTP …). Server message: … Check nzbdav's logs.
  • … blocked the NZB download: too many requests. Your indexer is rate-limiting you. Wait, or choose a release from another indexer.
  • Download timed out after N seconds. The job didn't finish within Download timeout (seconds) (default 3600).

WebDAV or authentication errors

NeNeTeePee-Stream-Kodi needs both the nzbdav API credentials and the WebDAV credentials.

  1. Confirm nzbdav URL points to the nzbdav server.
  2. If WebDAV uses the same address as nzbdav URL, clear the WebDAV URL so NeNeTeePee-Stream-Kodi reuses the nzbdav URL. On 2.0.0 builds this field defaults to http://localhost:8080 (on 1.2.3 it starts empty). Leaving that default in place when Kodi can't reach WebDAV there is the most common cause of WebDAV errors.
  3. If you use a separate WebDAV endpoint, confirm WebDAV URL points to it.
  4. Confirm the WebDAV Username and Password match nzbdav's WebDAV settings.
  5. Run Test WebDAV Connection:
    • WebDAV connection OK: the connection works.
    • WebDAV authentication failed. Check credentials.: the username or password is wrong (HTTP 401/403).
    • WebDAV server error. Check server logs.: nzbdav returned a 5xx error.
    • WebDAV connection error. Check server.: the address is unreachable or wrong.
  6. If a download completes but you see Video file not found in WebDAV folder: …, check the preceding WebDAV settings. Also make sure the download actually completed on nzbdav. If the message is Download completed but the video file is incomplete, nzbdav is missing articles from the middle of the file. Check your provider's retention, or pick another release.

NZBGet backend problems

Beta feature

The NZBGet backend was added in 2.0.0-beta.1. It's available on the Beta channel.

  • NZBGet not configured: NZBGet URL or the completed folder is empty.
  • NZBGet connection failed (from Test NZBGet Connection): check the URL, NZBGet Username, and NZBGet Password.
  • Completed folder not reachable (from Test Completed Folder): Kodi can't see the completed folder. Check the smb:// URL and its credentials, or check your mount.
  • Video file is listed but not readable. If this persists, check the share or mount and restart Kodi. The file shows up in the folder but won't open. After a download, NeNeTeePee-Stream-Kodi keeps trying to read the file for up to 60 seconds before it gives up. A file that stays unreadable is usually Kodi's cached SMB session going stale: new SMB sessions can read the file, but Kodi's cached one gets "Permission denied." Restarting Kodi resets that session. To avoid it altogether, mount the completed folder as an NFS hard mount instead of using smb://. kodi.log shows NeNeTeePee-Stream-Kodi: video is listable but not readable through Kodi's VFS: ….
  • No video file found in completed folder: check NZBGet Category. NZBGet puts completed downloads in a subfolder named after the category. Also check that the completed folder points at NZBGet's completed-downloads folder.
  • NZBGet HealthCheck=Pause: set it to Delete, None, or Park …: automatic duplicate failover can't work while NZBGet pauses broken downloads. Change HealthCheck in NZBGet.
  • Download failed in NZBGet: NZBGet couldn't repair or unpack the release, and no duplicate backup took over. Pick another release.

For the full setup, see NZBGet backend.

Playback starts, then fails

With nzbdav or InfiniDysk, playback goes through NeNeTeePee-Stream-Kodi's local proxy so Kodi can avoid WebDAV and large-file edge cases. In NZBGet mode there is no proxy: Kodi plays the finished file straight from the completed folder, so check the share or mount first (see NZBGet backend problems).

  1. Try another release for the same title.
  2. Confirm the source is still available on your backend.
  3. If you set Large non-MP4 stream mode to Matroska remux or fMP4 HLS (Advanced → Proxy), confirm ffmpeg is installed on the Kodi device. If it isn't, you'll see Failed to start ffmpeg. The default, Direct pass-through, doesn't use ffmpeg. Force ffmpeg remux above (MB, 0=off) only sets the size at which the chosen remux mode starts.
  4. On CoreELEC, or with large files, start with the default pass-through settings before you try the remux modes.
  5. For full seeking on large files, set Kodi's cache to 0. See advancedsettings.xml and seeking. If a stream you start from TMDBHelper is remuxed and this setting is missing, NeNeTeePee-Stream-Kodi shows the snippet in a dialog, at most once per Kodi session (or never again if you choose Never ask). It never edits the file itself.
  6. Check kodi.log for proxy, WebDAV, ffmpeg, or fallback messages.

Notifications during playback tell you what the proxy is doing:

Notification Meaning
nzbdav unreachable — playback may glitch The proxy lost its connection to nzbdav. Check that nzbdav is running and reachable.
nzbdav can't keep up — playback stalled nzbdav couldn't deliver data fast enough. Your Usenet provider or nzbdav may be overloaded.
fall back to candidate #N successful / was a failure A backup release took over, or failed to. See Fallback streams.
Skipped N bytes across N recoveries The proxy skipped missing articles. You may notice a brief glitch.
Stream aborted after repeated zero-fill recovery Too much of the file was unreadable. Pick another release.

For the internals behind these behaviors, see How it works → Stream proxy.

What to include in a bug report

  • Kodi version and platform.
  • NeNeTeePee-Stream-Kodi add-on version, and whether you're on the Stable or Beta channel.
  • Whether the problem affects all titles or just one.
  • Which search providers and which backend (nzbdav, InfiniDysk, or NZBGet) you use.
  • Whether your backend accepted, completed, or failed the job.
  • Sanitized NeNeTeePee-Stream-Kodi settings relevant to the failure.
  • Relevant kodi.log lines (the NeNeTeePee-Stream-Kodi: or NZB-DAV: lines around the failure), with secrets removed.

Report issues at the NeNeTeePee-Stream-Kodi issue tracker.