Brickfrog
- 0 Posts
- 119 Comments
1·19 days agoThat’s weird, maybe an update broke something? What I would maybe do is uninstall Xrdp (and maybe remove/rename the old config files just in case), then re-install and configure it. From there if it’s still not working try to see what’s showing up in the log files maybe.
I did notice that Xrdp requires some extra configuration to work properly with Linux Mint Cinnamon, you apparently need to create a .xsession file in the home folder of whichever user(s) you’re trying to remote into. I’m not on Linux Mint myself but maybe searching around will give you some tips e.g. this seems like a good rundown https://gist.github.com/ParkWardRR/2ab9b5d41bbaceca8471d591755a1898
EDIT: You probably already know this from using it before but for RDP on Linux you’d need to remote into a user that is not already logged in… it’s not like in Windows when you can RDP into any user regardless if they’re already logged in or not.
Yup, been using Xrdp in a Debian + GNOME Wayland setup without issue.
I’ve also used GNOME’s built in Remote Desktop (RDP) with Wayland. KDE’s own RDP should work with Wayland too but I haven’t tested that one yet.
RDP (the same protocol Windows Remote Desktop uses) works fine on Linux. I’d suggest investigating why that suddenly stopped working for you.
For what it’s worth Xrdp seems to work well on Linux for enabling a RDP Remote Desktop server… I suspect you are / were(?) already using Xrdp and just need to figure out why it stopped working.
deleted by creator
8·29 days agoI don’t know about “best” but on Android I’ve been using the K-9 mail app for years without problems. Supports multiple email accounts as well as standard IMAP/SMTP email protocols which is all I really need. The project was merged with Thunderbird so now it’s Thunderbird for Android.
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.
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.
111·1 month agoI 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 /verifyonlyif the above tells you there are system files to fix run
sfc /scannowRestart the computer, repeat the above until sfc tells you there’s nothing to fix.
Then run
dism /online /cleanup-image /scanhealthif the above tells you there are files to fix run
dism /online /cleanup-image /restorehealthRestart 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)
2·1 month agoAh 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 0vs 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.
2·2 months agoJust 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.
Seems like it’s down right now.