Brickfrog

They have a reputation for deleting free accounts. If you plan to use Tuta for more than a few months be sure to use their paid plans, not free.

e.g. https://lemmy.ml/post/41480556

maybe the comments in this post help? https://lemmy.ml/post/40864672 and/or consider posting in one of the jellyfin communities like /c/jellyfin@lemmy.ml or /c/jellyfin@lemmy.world ?

My guess is you probably need to go into terminal and probably fix the folder/file permissions for your media library folders (using chmod), then remove/re-add that media library in jellyfin itself so it can scan the folder properly. But that’s just a guess without really knowing your actual set up.

PS - Don’t worry about Ubuntu, once you get your initial setup figured out everything will run stable.

I don’t remember how Jellyfin installs on Windows nowadays but if it’s just the Jellyfin tray icon executable giving you issues maybe a simple fix is just to remove it from being autostarted? This is assuming the rest of Jellyfin starts up fine without needing that tray icon in the Windows taskbar.

If that doesn’t help it might be that .NET is broken on your system. That’s a lot harder to fix unfortunately… you could try to see if the Windows add/remove programs gives you an option to re-install/fix the current .net installation but that may not help you out much.

You could also check that your Windows system files aren’t themselves broken. Google around for running SFC and DISM, offhand I typically do something like (in an elevated cmd.exe window):

sfc /verifyonly

if the above tells you there are system files to fix run

sfc /scannow

Restart the computer, repeat the above until sfc tells you there’s nothing to fix.

Then run

dism /online /cleanup-image /scanhealth

if the above tells you there are files to fix run

dism /online /cleanup-image /restorehealth

Restart the computer, repeat the above until dism tells you there’s nothing to fix.

If none of the above fixed anything then it may be time to consider reformatting and re-installing Windows fresh.

(at home I’m on Linux myself but still support Windows systems at work every day)

Ah true, Fopnu is his other non-bittorrent p2p app. In some ways Fopnu is the spiritual successor to WinMX. It is clearnet only so it’s a bit outside the scope of I2P.

The same dev did also create DarkMX (https://darkmx.app/) which was Tor only up until more recently when he added I2P support around the same time frame he was adding I2P to Tixati. DarkMX (IMO) seems more interesting for I2P users since it was designed from the beginning to work within darknets. Haven’t had a chance to play around with it so can’t say that it has much of a user base but could be worth a look.

Not un-useful, but the number of Tixati users is already limited on the open internet (and heavily slanted towards certain unsavoury interests). Finding other Tixati users on i2p just limits your potential peer group further.

To be fair Tixati is a bittorrent client using the same standard bittorrent protocol that other clients use. So it will connect to bittorrent swarms, peers, trackers, etc. just like any other I2P bittorrent client. So Tixati users will connect to I2P bittorrent peers using I2PSnark, XD, qBittorrent, and BiglyBT. (and any others I missed)

The big limitation is that there are less bittorrent peers on the I2P network vs the clearnet internet… it’s a big difference. It’ll probably stay that way until there’s more people keeping torrents active within I2P, hopefully in the future.

Other minor limitation is that I2PSnark (& and maybe Tixati) are the only bittorrent clients that can use the bittorrent DHT within I2P, all the other bittorrent clients can only find peers using bittorrent trackers. It’s not a big deal as long as people remember to add I2P trackers to their torrents but it does make things less decentralized. Tixati does claim I2P DHT support but I’m not sure how well it works in practice.

Interesting, I did not realize Tixati had I2P support. Actually it has had I2P support since January 15 2025 so it’s had that for a year now.

Tixati itself is not new, the torrent client has been around since 2009 (surprisingly the developer kept all those release news updates on the website https://tixati.com/news).

For darknet p2p file transfers the same developer did create DarkMX (https://darkmx.app/), that itself has had I2P support since June 2025. It used to be Tor only up until then… I haven’t used it personally but it would make more sense for people to use DarkMX rather than Tixati since DarkMX was developed from the beginning without requiring clearnet internet. Using Tixati with I2P is fine but you’re still relying on the Bittorrent protocol for Tixati to work.

Fun fact: This is the same developer that created WinMX back in the day (Kevin Hearn), his software has never been open source but he’s been developing p2p software for a long time now.

Feels like this should have already been resolved with standard Linux permissions, any user on your system should be able to read/traverse that folder and files with the r-x permission on world.

From your earlier comment one of the parent directories is listing with “+” permission so it sounds like you are using extra permissions outside of the standard Linux, probably ACL permissions. I haven’t worked with ACL permissions on Linux enough to offer much advice but what you may want to do is run something like getfacl d64ea996-98aa-4eef-8a93-0a2ba2246f0f as well as run it on one of your media files, that might give you some clues on what the ACL permissions look like.

Also - I’m assuming you already did this - but if you didn’t already make sure your jellyfin service is actually launching with the expected user and user group. Based on your setup you may want to be sure the “jellyfin” Linux user is added to the “video” user group, and then make sure that’s what is being referenced in jellyfin.service.conf (by default is usually in /etc/systemd/system/jellyfin.service.d). If you edit that file be sure to stop the jellyfin service first and then restart it after editing e.g. “systemctl stop jellyfin” and “systemctl start jellyfin”.

Only other thing I can think of is that maybe there’s something wrong with the way your system is mounting the drive and folder. Since you seem to be using the autogenerated UUID for the mounted folder name (d64ea996-98aa-4eef-8a93-0a2ba2246f0f) maybe it’s better to edit fstab yourself and set up your mount as something more permanent with a normal name, and also double-check the permissions everything is mounting as.

Four spaces before the line you want to codify :)

e.g.

UUID=“your uuid” /mnt/external exfat defaults,uid=1000,gid=“your group id”,umask=002,nofail 0 0

vs non-formatted

UUID=“your uuid” /mnt/external exfat defaults,uid=1000,gid=“your group id”,umask=002,nofail 0 0

Are the files within the folders the media folder also with permissions 775 (rwxrwxr-x)? The actual .mkv .mp4 or whatever files themselves should be the same permissions as the parent folder(s). Could be worth doing a chmod -R 0775 d64ea996-98aa-4eef-8a93-0a2ba2246f0f if you’re not sure.

You probably already tried this but just in case: In the Jellyfin admin pages, in Libraries, try removing that media library, then re-add the media library and when adding Folders paste in your entire media folder path/name: /media/velummortis/d64ea996-98aa-4eef-8a93-0a2ba2246f0f

The reason I mention that is that I did a quick test here with a bad permissioned folder, added the media folder, Jellyfin couldn’t see anything in it obviously. But even after I fixed the folder permissions Jellyfin still wasn’t seeing the media - I had to remove the library entirely and then re-add it to force Jellyfin to attempt to scan the folder with new 775 world permissions.

Also using Debian + Jellyfin normal install with basic permissions (in the future maybe I’ll try this with ACL permissions).

Starting out I tinkered with creating a specific user group for jellyfin but it never quite worked right… in the end I reset the jellyfin user/service back to defaults and set permissions on my media folders to 0775 so that the jellyfin service can read/execute (no write) as the world permission bit. Also made sure to set permissions recursively (chmod -R). For me it’s fine though keep in mind setting 5 for world does mean all users with access to your system can read and traverse through those media folders.

Just to be sure, did you already test that the port is actually open and forwarded? e.g. with your torrent client running browse to a port test website like https://canyouseeme.org/ , https://www.yougetsignal.com/tools/open-ports/ , etc. put in your torrent client’s incoming port and check if the website can “see” your open port at your torrent client.

And the ISP (or router) itself isn’t doing anything weird to block torrents, right? In your torrent client if you click any working public torrent, click on the Trackers tab, you should see DHT as working along with whatever open trackers are on the public torrent. In other words you won’t see anything like “waiting” something (I forget the exact message you’ll see when DHT is being blocked but it’ll definitely not be working).

EDIT: Also if it’s a new ISP with new router it might have firewall rules set up that are slowing things down, something to check.

The copy protections on Blu rays are exceptionally annoying, to the extent where there is really only one closed source software – MakeMKV – that can work around them.

Not quite, RedFox formerly SlySoft (RIP) used to market their own Blu-ray ripper and it worked quite well. What it used to do is on-the-fly decryption so you’d run it in the background and could use any other software to read the decrypted Blu-ray (e.g. using Handbrake or whatever). It did also have an option to just rip to a file IIRC. Unfortunately they randomly disappeared so their software is pretty much done. (some background on wikipedia https://en.wikipedia.org/wiki/RedFox)

That aside they always a competitor, DVDFab, that still exists today. Their Passkey software is the rough equivalent of what the old RedFox/SlySoft software used to do but they also sell a standalone Blu-ray ripper if that’s more your thing (see https://www.dvdfab.cn/).

But yeah, in some ways you’re stuck with MakeMKV, DVDFab, and maybe some others (?).

I’d have to dig it out but I actually bought a Blu-ray drive a while back that was on the list of drives compatible with these rippers but honestly it’s been a few years since I’ve tried using it. Most times someone else already ripped a Blu-ray I’d be interested in.

Speaking of - If anyone knows offhand, how do people do this stuff on Linux? Does the Linux version of MakeMKV work well for this and/or are there other tools (?)

Wake on LAN is a LAN feature, not WAN, so you’d need to issue that over the local LAN there at the house. You’re going to have a hard time trying to get that working over the WAN (if that’s even possible).

The other comments mentioning a scheduled boot would be a much easier/simple solution if it works for you.

But I’ll throw this in, the super basic least tech solution to this is to open a port forward to the house’s network router. Yes, I know you don’t want to do that, but it’s probably the only network device at that house that’s actually on 24/7 right? And by all means lock it down however you like. My simple method is to open the router login to a non-standard port number, with a IP whitelist, add my own home IP address to that IP whitelist, and bam you now have access to that remote home’s router for just your IP address. Log in remotely, issue a wake on LAN via the router’s own web ui, done.

It’s perfectly reasonable to make this a bit more secure if you wanted but it gets slightly more complicated - open a non-standard port for SSH access to the remote router’s SSH port that only allows SSH login with key. Generate a SSH key and share that key with yourself, then you can log in remotely to that remote house via non-standard SSH port using the SSH key (no user/passwords). From there you’d have to see if you can issue Wake on LAN on the SSH command line, or set up a SSH tunnel from that remote LAN to yours so you can proxy into the router login page and do your Wake on LAN from there. … yes I realize this got complicated :/ But you’ve got a few things to explore given your patience for tinkering with this stuff :)

Of course much of this relies on that house’s router having any of these features to enable and configure. The main takeaway here is that Wake on LAN requires something on 24/7 at that remote LAN for you to enable remote access into and issue a Wake on LAN command within that LAN. How to actually accomplish that is the tricky bit.

That’s fair, I don’t use Tailscale either but was thinking that would affect the WAN side of things rather than the LAN that the phone and Chromecast are on. Looking into it a bit more it sort of seems like OP would need to configure Subnet routing on their Tailscale configuration to enable their Tailscale to forward traffic to devices on the local LAN?

https://tailscale.com/kb/1019/subnets

That was just from some quick searching around but since I don’t use Tailscale I can’t say for sure if that’s a solution (or even if Tailscale is the culprit here).

And yes for sure if OP doesn’t specifically need/want Tailscale then maybe a different remote solution would be something to try like reverse proxy or whatever they decide on.

Yes pretty much, there isn’t really anything extra to configure for casting. I think to get it working

• Both the Google Chromecast and your phone must be connected to the same home network (in other words the same home wifi)
• The TV itself should be on and set to HDMI-1 or whatever port the Chromecast is plugged into
• The Chromecast itself should already be set up, connected to the network, etc. (I’ve never needed to do this but I suspect there’s a few basic steps to get it set up and connected to wifi, etc.)

Do you know if the Chromecast there was accepting other casts from other apps / phones? I wonder if there’s just something configured oddly at that network, or their Chromecast just wasn’t working correctly like maybe it was offline. My Pixel 7 also has a feature to cast the phone screen itself so if your phone can do that it’s something you can test next time you’re able to. (that might just be for Google Pixel phones, other phones might not do screen casting in that way).

I don’t own a Chromecast myself so can’t really think of other things to try, they usually just work if they’re on and online.

Hi. What’s the best way to access my content from a remote location? I’ve got tailscale set up

Are you already able to access your JF content remotely? Wasn’t sure what you meant by saying that you set up tailscale but still asking about accessing content remotely.

If your JF app can already stream your content remotely on your phone, say when you’re out traveling outside your own home, then you already have the ability to cast. Just be sure to have your phone connect to the same network connection that the Google Chromecast is connected to (e.g. that home’s wifi network) then tap the cast icon at the top of the JF app. The Google Chromecast will appear there and you can tap it to start casting whatever you are playing on the JF app to the TV the Chromecast is connected to.

That’s how I do it when traveling to other locations that have a Google Chromecast set up on their TV.

Minor update, I edited my original comment above. The app does seem to work with Jellyfin 10.11.1.

Maybe I’m not the best test candidate LOL… I usually use the Android Jellyfin apps for music so my original test was with a Jellyfin user with only music libraries enabled… Findroid does not like that apparently. Once I logged in with a user with TV/Movie libraries enabled it seems to load and play video.

I don’t normally use that app but I figured I could do a quick test for you - the stable version (0.15.3) does not seem to work on my end. It does connect to the Jellyfin server (10.11.1) but nothing loads after that.

It doesn’t look like findroid has had any stable releases in over a year so it may indeed be showing some incompatibility issues.

EDIT: Re-tested, it does seem to work as long as you have video libraries enabled on the Jellyfin user (e.g. Movies/TV). My earlier test was with a Jellyfin user that only has Music enabled, I did not know Findroid does not play music. (most of my Jellyfin mobile use is for music)

Always good to double check, but yes, I used canyouseeme and the port is definitely open.

That means TCP should be working as expected with the current configuration. Note those port test websites are only testing TCP, not UDP.

A few menu options below the one for port forwarding

I’m not familiar with ProtonVPN configuration so can’t guide you much there, presumably if the port forwarding option only allows for one setting then maybe it’s doing both TCP/UDP? I dunno…

there’s another for configuring the connection as OpenVPN(TCP), OpenVPN(UDP), or Wireguard.

Don’t worry about that one, that’s for configuring the VPN client you will be using to connect to the VPN server. It should not affect the port forward itself unless ProtonVPN is doing something odd.

I’ve had other issues in the past and Transmission’s internal port testing thing

Yeah I wouldn’t rely on that, the internet port test inside the torrent client isn’t always reliable. But in theory it should show up as open all the time if you have a stable open port :/

Could I be missing a step with the trackers?

Doubt it being a tracker issue, they update themselves on their own schedule usually.

I also have a client I’m trying to test uploading to, but it can’t seem to connect to the seedbox

Maybe should have asked this before - can the test torrent client see that there is a seed on the torrent? Or does it load the torrent but just isn’t seeing any seeds or peers at all? The open trackers take a bit to update themselves with a new torrent hash so sometimes it just takes a bit before the torrent client sees a seed and begins downloading from it.

Just to double-check did you already test that the open port is actually open and connectable from the internet? e.g. use any port test website & see if it can connect to your seedbox Transmission open port e.g. https://www.canyouseeme.org/ , https://portchecker.co/ or similar.

Also, not sure how the open port itself was configured but make sure it is open for both TCP and UDP traffic if you needed to specify that during your firewall setup.