• 18 Posts
  • 64 Comments
Joined 1 year ago
cake
Cake day: June 18th, 2023

help-circle

















  • aldalire@lemmy.dbzer0.comtoSelfhosted@lemmy.worldStarting from zero
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    1
    ·
    7 months ago

    Recommend doing a jellyfin server with an *arr stack! Prowlarr, radarr, sonarr, plus qbittorrent. Bonus if you can integrate i2p in there so you don’t have to rely on a VPN :)

    there’s also Nextcloud AIO docker. I use it to sync my photos and escape Apple’s 5gb max free-tier backup

    Maybe add some assorted services like an invidious instance, Searxng instance?

    Welcome to the self hosting rabbit hole!




  • Haha. Well, I guess I have a ulterior motive for promoting i2p; the more people get in it and contribute to the network (port forward the NTCP2 and SSU2 to accept transit tunnels) the better network speeds will get! Just the act of torrenting through i2p will help the network tremendously.

    I have noticed that speeds in i2pd (c++) are faster than in the original java implementation so maybe you can try that out? It’s fast enough for my use case, but yes streaming torrents in i2p is still far away.

    But the upside is, you don’t have to rely on a VPN to protect yourself against copyright trolls! Plus, putting it on a fully automated *arr stack means you can just add a movie on radarr and let the *arrs take care of everything in about a day or so. I average at about 200-300 KiB / s per well-seeded movie file, and around half that for something poorly seeded.


  • I haven’t tried the i2p docker image, but it shouldd work. Let me know

    There are some German and French content that I see occasionally in Postman. In the actual i2p postman site you can filter for the French and German language.

    If you’re using the docker image the network_mode is set to host, so it should work the same as if i2p was installed without containerization.

    where 7656 is the SAM bridge port. I’m using version 4.6.3 of qbittorrent and it has this feature. The arch package for qbittorrent-nox (the webui edition of qbittorrent) already has this feature. I just checked; the latest docker image for qbittorrent should already have this feature! https://github.com/linuxserver/docker-qbittorrent

    Not too sure about private trackers. Although, due to the fundamental anonymizing feature of i2p there would be no way for copyright trolls to track IP addresses and send mass lawsuits, which private trackers defend against.



  • It’s all free and open source! If you’re on windows it might be a little more difficult so at least having a linux PC you can reliably have on 24/7 would make things easier. I personally use arch (I’ve tried this on my endeavour OS), very easy installation for beginners) for this since it’s rolling release (latest versions of packages!) and the AUR is a godsend. The programs themselves take little ram and cpu, with qbittorrent probably needing the most ram once you have more torrents downloaded (I’m running this on 4 cores of CPU and 4 gigs of ram alongside my minecraft server, a tor relay and a monero node. any old laptop repurposed with endeavour should do the trick)

    the steps I took to do this (on endeavour os) was:

    install i2pd

    • sudo pacman -S i2pd

    Install qbittorrent webui

    • sudo pacman -S qbittorrent-nox

    install prowlarr (optionally sonarr and radarr, which will automatically manage video files for you. Plays reaaaally well with Jellyfin, so you wouldn’t have weirdly formatted files that is being read by Jellyfin)

    • yay -S prowlarr
    • yay -S sonarr
    • yay -S radarr

    Lastly you have to turn enable the *arrs in systemd

    • sudo systemctl enable --now prowlarr
    • (do the same with sonarr and radarr if you have them)

    (or you can also go the docker route with qbittorrent, prowlarr, sonarr and radarr, if you don’t have arch. This is the more universal route and can handle many more devices. Although I have not checked if qbittorrent-docker has i2p integration yet. For that you may need to swap out qbittorrent for vuze, or apply the patch in the comment in the link i posted in the docker container [which is editing the qBittorrent.conf file])

    For the average joe i’d say it’ll be an afternoon’s worth of labor to set up, and the upside is not relying on a VPN to install content and a fully automated Jellyfin server! Plus you get to help the steadily-growing i2p network If you have more questions I’d be happy to answer here :)