Skip to content

About

The universal eMule daemon: a headless, asynchronous Rust eD2K/Kad client for Windows x64/ARM64, Linux x64/ARM64 (DEB, AppImage and static-musl builds), macOS Intel/Apple Silicon, and multiarchitecture Docker/OCI containers, plus experimental Android APK and native Termux builds—with a browser operations console and authenticated REST API.

Topics

Resources

Contributing

Security policy

Stars

11 stars

Watchers

0 watching

Forks

Repository files navigation

eMuleBB Rust: eD2K and Kad with browser control on Windows, Linux and macOS

eMuleBB Rust

eD2K and Kad. Browser control. REST automation.
Search, download and share with one headless IPv4 daemon.

Use eMuleBB Rust  ·  Develop with eMuleBB Rust

Nightly downloads · Platforms · REST API · Roadmap · Help

Rust CI CodeQL workflow GPL-2.0-only

Active beta. Dated nightly prereleases are the current public testing channel. Prebuilt packages need no Rust toolchain.

What you can do

Search and transfer

Search eD2K/Kad, add downloads and follow transfer progress from the packaged browser console.

Share chosen folders

Monitor recursive folder trees, review hashing and manage sharing settings.

Automate through REST

Connect integrations to an authenticated API with a documented OpenAPI contract.

Inspect your client

Review network status, diagnostics, logs and source-bound package checksums.

Downloads and platforms

Choose a runnable asset from the nightly releases, then compare its exact filename against that release's SHA256SUMS. The platform run guide owns installation commands, profile paths, requirements and qualification scope.

Platform Choose Install and run
Windows x64 or ARM64 ZIP Extract and launch
Linux x64 or ARM64 DEB, AppImage or static-musl tar/zstd Choose a Linux variant
macOS Intel or Apple Silicon DMG Copy and launch the app
Docker / OCI Linux amd64 or arm64; Ubuntu or Alpine Run with persistent volumes
Android APK Universal ARM64 + x86_64; Android 12+ Permissions, manual Start and WebUI
Android / Termux native Experimental android-arm64-v8a.tar.zst or android-x86_64.tar.zst Extract under private HOME and launch

The macOS app is unsigned and not notarized. For containers, both ghcr.io/emulebb/emulebb-rust variants publish versioned tags and moving nightly / nightly-ubuntu / nightly-alpine aliases; there is no latest tag.

Android remains experimental. The nightly release contract includes the signed Android 12+ APK and both native archives, android-arm64-v8a.tar.zst and android-x86_64.tar.zst. Follow the platform guide for installation and manual foreground-service start, including after reboot. The native archives target API 28 for compilation; compile and ELF checks do not qualify Termux or Fire OS runtime. Termux runtime, Fire OS, automatic boot-resume and 24-hour endurance remain unqualified. See Android evidence and remaining acceptance.

Get started

  1. Follow your platform's run instructions. Keep the complete extracted archive layout, including webui.
  2. Open http://127.0.0.1:20017/ on the daemon host. The default listener is 0.0.0.0:20017. Native packages use the ready key change_me_123change_me_123change_me_123; the APK supplies a generated key through Copy API key and Open WebUI.
  3. Review network, incoming and shared-folder settings, then search or add a download. Default P2P ports are TCP 20019 and UDP 20020.

Direct daemon launches keep the profile beside the executable, independently of the working directory. Select another writable profile with --profile. Desktop launchers, containers and the APK explicitly choose their documented profile paths. The private emulebb-rust-settings.toml owns REST bootstrap settings; mutable client settings live in the profile database.

Startup may fetch discovery inputs and start configured networking. During beta, an incompatible database requires an entirely fresh profile; preserve the stopped old profile, payloads and matching binary for rollback. The getting-started guide covers everyday operation, shutdown and troubleshooting.

Use the API

All /api/v1 routes use the X-API-Key header. Start with read-only GET /api/v1/capabilities and GET /api/v1/status; keep credentials in headers.

The beta API is still evolving; use the contract for your selected build.

Android native HTTPS trust

Native CLI bundles verify certificates and hostnames with packaged Mozilla CA roots, without a JVM. Android/Termux CA stores and SSL_CERT_FILE do not extend this trust set. Updated roots arrive with new client builds.

Develop and contribute

Work on the client

Improve the daemon, browser console, tests or documentation.

Build and validation guide · Contributing

Find the next change

Review current work and coordinate an actionable issue before implementation.

Roadmap · Issues

Help and security

Diagnostic bundles are private operator evidence and can contain credentials, paths, identifiers and logs. Review them before sharing publicly.

License

GPL-2.0-only. Dependencies retain their own licenses; see third-party notices.

About

The universal eMule daemon: a headless, asynchronous Rust eD2K/Kad client for Windows x64/ARM64, Linux x64/ARM64 (DEB, AppImage and static-musl builds), macOS Intel/Apple Silicon, and multiarchitecture Docker/OCI containers, plus experimental Android APK and native Termux builds—with a browser operations console and authenticated REST API.

Topics

Resources

Contributing

Security policy

Stars

11 stars

Watchers

0 watching

Forks

Releases

Packages

Used by

Contributors

Languages