-
Notifications
You must be signed in to change notification settings - Fork 3
Troubleshooting
Start by identifying which stage failed:
- installation or
PATH; - search/episode discovery;
- crypto/bootstrap decoding;
- provider source resolution;
- player launch;
- download transfer/finalization.
The distinction matters: reinstalling will not repair a provider outage, and refreshing crypto will not fix a missing player executable.
Windows portable installations default to:
C:\Users\USER\.local\bin\ani-cli-rs.exe
Check:
Test-Path "$HOME\.local\bin\ani-cli-rs.exe"
[Environment]::GetEnvironmentVariable("Path", "User")
Get-Command ani-cli-rs.exe -ErrorAction SilentlyContinueOpen a new PowerShell or Command Prompt after installation. The current terminal does not automatically inherit persistent PATH changes made by another process.
Linux:
ls -l "$HOME/.local/bin/ani-cli-rs"
printf '%s\n' "$PATH"
command -v ani-cli-rsSource the profile modified by the installer or open a new shell.
Current installer scripts deliberately select the published x64 Windows archive on Windows, including Windows 11 ARM64 systems that can emulate x64. Download the newest install.ps1; older cached copies may still contain architecture detection that rejects some systems.
Useful system information:
[Environment]::Is64BitOperatingSystem
[Environment]::Is64BitProcess
$env:PROCESSOR_ARCHITECTURE
$env:PROCESSOR_ARCHITEW6432
Get-CimInstance Win32_OperatingSystem | Select-Object Caption, Version, BuildNumber, OSArchitectureYour shell is using an old Cargo. Verify:
which cargo
which rustc
cargo --version
rustc --versionAfter installing through rustup:
source "$HOME/.cargo/env"
rustup update stableEnsure $HOME/.cargo/bin appears before /usr/bin in PATH.
Install the exact target:
rustup target add x86_64-unknown-linux-muslor:
rustup target add aarch64-unknown-linux-muslAlso install the corresponding musl linker/toolchain through your distribution.
Try:
ani-cli-rs debug --refresh
ani-cli-rs refresh-cipher-mapThen retry. Common categories:
-
AA_CRYPTO_STALE: frontend and API crypto material disagree or cached material is stale; -
AA_CRYPTO_CROSS_KEY: build/epoch material does not match the API response; -
Too many requests: AllAnime rate limiting; wait before retrying; -
released but no supported sources resolved: episode metadata exists, but all extracted providers failed or are unsupported; -
provider reports video unavailable: the host explicitly reports deletion/blocking; -
provider returned an HTTP error: an AllAnime proxy or video host returned a failing status.
The client retries bounded rate limits and tries dynamic, bundled, legacy, persisted-query, and full-query paths. Repeated rapid retries can prolong upstream throttling.
Different episodes use different third-party hosts. One show can resolve through Wix or OK.ru while another has only deleted or protected Filemoon/VidGuard copies. Include the show ID, episode, mode, version, and sanitized provider categories in a bug report.
Do not include complete signed media URLs.
Likely causes:
- expired signed URL;
- missing provider referrer/origin;
- URL bound to another public IP;
- router, DNS, antivirus, or corporate filtering;
- too many parallel connections.
Resolve the source again. Test another network or VPN only if allowed by your network policy. FortiGuard and similar filters may classify Mkissa/AllAnime or media hosts as adult/streaming content even when ani-cli-rs itself works correctly.
Verify the executable directly:
Get-Command mpv.exe, vlc.exe, syncplay.exe, aria2c.exe, yt-dlp.exe, ffmpeg.exe -ErrorAction SilentlyContinuecommand -v mpv vlc syncplay aria2c yt-dlp ffmpegInstall only the tools needed by your workflow. Direct downloads can fall back to Rust; HLS requires yt-dlp or FFmpeg.
The transfer did not finalize. Rerun the same command to resume where supported. Check free disk space, file permissions, antivirus quarantine, whether another program holds the final filename, and the final aria2/ani-cli-rs error. See Downloads.
Safe report template:
ani-cli-rs version:
OS and architecture:
Command shape (redact title if needed):
Show ID and episode:
Sub or dub:
Provider failure categories:
Expected behavior:
Actual behavior:
Never attach cookies, authorization headers, active signed URLs, raw decrypted episode payloads, or personal paths unless carefully sanitized.