← Directory

Ygege

Ygege - high-performance public YGG indexer relay for Prowlarr and Jackett.

  • Downloaders
  • Network Services
  • Tools & Utilities
Ygege - high-performance public YGG indexer relay for Prowlarr and Jackett.

Platform availability

Available on 1 of 9 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

54/100 Fair

Maintained
64last commit 110 days ago
Popular
54508 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today, links checked 9 days ago

GitHub stars
508
Open issues
12
Last commit
2026-06-27
Latest release
v0.9.1
License
MIT
Activity
stale

Checked 7 days ago - source: GitHub (UwUDev/ygege)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 17 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Enter your YGG Torrent login first Before starting Ygégé, put your YGG Torrent username and password in the Docker Compose file (the file that tells Docker what to run) or config.json. Without these required credentials, it cannot fetch torrents from YGG. source
  • Keep your config folder safe Store the local folder that is shared into the app as /config, such as ~/ygege/config, somewhere you can back up. It holds your settings and login details, so losing it can break your Ygégé setup. source
  • Check port 8715 if it won't start If Ygégé fails to start or won't answer, check its logs and see whether port 8715 (the port it listens on) is already in use. A taken or blocked port can stop the web interface and API from working. source

Fetched today - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How do I configure relays for Ygege on first launch?

Ygege ships with no relays configured, so you must provide at least one Nostr NIP-35 relay before first use. You can set it in config.json or via the RELAYS environment variable, using multiple relays as a JSON array or a comma-separated list.

Do I need an account or authentication for the relays?

No, the relays are configurable without an account or authentication. You can optionally set allowed_pubkeys to trust specific publisher keys; the default is the U2P publisher, and an empty array accepts any valid signed event.

What should I back up?

Preserve the config.json file, which is generated on first launch and stores your relay endpoints plus optional allowed_pubkeys and web_base_url settings.

Can Ygege be used with Prowlarr or Jackett?

Yes, it is compatible with Prowlarr, Jackett, and all *arr applications.

What if Ygege login fails with 403 or a missing ygg cookie?

In the fork, when wreq alone can no longer pass the Cloudflare challenge, Ygege can automatically use a FlareSolverr container to obtain bypass cookies and reinject them into the wreq client to continue login.

Answers sourced from github.com, github.com

Community

Collected 16 days ago - public community threads