• 17 Posts
  • 108 Comments
Joined 1 year ago
cake
Cake day: June 10th, 2023

help-circle


  • found the culprit: I’ve connected my jellyfin-media-player apps to a CNAME alias provided by my Pi-hole (jellyfin.box) and a matching nginx proxy entry:

            listen 80;
            listen [::]:80;
    
            server_name jellyfin.box;
    
            location / {
                    proxy_pass http://127.0.0.1:8096/;
           }
    

    so when I disconnected the app from the jellyfin.box server and connected it to the “new” server at server.box:8096 it started working immediately. looks like I’m missing some headers in that proxy so I’ll look into it.

    edit: yepp, adding headers fixed it, I can connect to the jellyfin.box server and have it detected by all other devices on the network.

            location / {
                    proxy_http_version 1.1;
                    proxy_set_header Upgrade $http_upgrade;
                    proxy_set_header Connection $http_connection;
                    proxy_pass http://127.0.0.1:8096/;
            }
    





  • I’ve gone the other way - there is no interacting per se with the media PC; instead, it’s a dumb sink that plays back everything you send it, by way of macast and jellyfin-mpv-shim. you use android apps to send it stuff (e.g. newpipe share to allshare which connects to macast and jellyfin android app which connects to JMS) and to control playback (pause, skip, change subs, etc.). so, all media selection and playback control is done from the mobile device, no need to touch the media PC doing the playback.

    not sure this will fit into your use case because of spotty internet, but that should prompt you to install jellyfin post-haste. then you have two options, the mentioned android app + JMS or just the jellyfin media player which can run in TV mode with a pared down controller (up/down/left/right/enter/back) - I’ve successfully repurposed an ancient Apple Remote that has just those six keys.





  • I mean, OK, it’s a vulnerability and there are interesting implications, but this is hardly significant in any pracitcal sense of the word.

    the potential victim has to run their system without a firewall, has to print to the printer they’ve never interacted with before and then the attacker can run shit with whatever the printing system’s user id is, which shouldn’t be an issue on any reasonably modern distro.

    I routinely remove cups and friends from any system I run because I have no need for printing and it bothers me to see it constantly during every system upgrade.



  • I wanted to write the same thing. have the notes app do the notes thing and handle encryption elsewhere.

    as to apps, I suggest QOwnNotes. it’s markdown, highly configurable so you can make it minimalistic AF, stores notes in invidual files and folders. it also has a bunch functionality like syncing to nexctcolud and such, but I’d advise against it, just use it as a notes editor. you don’t have to selfhost anything, make it use the e.g. Documents/Notes folder and you can use syncthing to securely replicate it to other devices.