• 0 Posts
  • 120 Comments
Joined 3 years ago
cake
Cake day: June 13th, 2023

help-circle
  • 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.



  • Brickfrog@lemmy.dbzer0.comtoPrivacy@lemmy.ml*Permanently Deleted*
    link
    fedilink
    arrow-up
    11
    arrow-down
    1
    ·
    1 month ago

    Just curious was this a Tuta paid account, or a free one?

    Tuta is very strict with the free accounts and flag them for all sorts of reasons. They take their time to “approve” free accounts just to be able to use them. And on top of that they might nuke your account anyway if they think it is being used for spam/illegal activity/whatever or they think it’s not being used.

    But I thought those are just issues with their free accounts, presumably their paid accounts don’t get flagged for those things… or so I thought.

    Also to echo the other comments - best to buy and own your own domain for your email, that way it doesn’t matter where the email is being hosted in case you need to switch email providers.




  • 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)


  • Like some of the other comments, if you really need a DE then maybe give XFCE or LXQt a try. The distro itself won’t matter too much in your scenario.

    I do have an old laptop that has run Debian/Ubuntu + Gnome fine, not at all fast but usable for my needs. Mines has 4 GB RAM, get the feeling that going under 4 GB may be a bit much.

    Otherwise Linux is perfectly usable without a DE if you’re willing to stick to the terminal for all your usage.



  • Pretty sure Strawberry does everything you are looking for.

    re: #1 I kind of had the same issue but with multiple music folders, most of the default music apps only let you use one folder. Strawberry lets you add as many music folders as you like, I’ve been happy with it.

    On Windows I used to use foobar2000 which was great, and in theory I could get it running under Linux, but I’d rather just use something coded for Linux compatibility from the start.


  • Working fine here, the app connects to the Jellyfin 10.11.1 server over the internet without issue.

    I’d suggest maybe double-check and make sure you still have a port forward from the internet to your Jellyfin server? Usually for me when the app gets stuck trying to connect it’s because it can’t see and connect to the Jellyfin server for some reason. Also in the 10.11.0 release notes they did mention that they removed the ability for the Jellyfin server to auto port forward so it’s possible that affected you? See https://github.com/jellyfin/jellyfin/releases

    Other random idea: Maybe somehow the data for your app got messed up? You can reset it and make it start fresh by bringing up its App Info (long-press the Jellyfin Android app), go to Storage & Cache, once there clear the storage and cache. When you re-attempt to launch the Jellyfin app it’ll start fresh and need you to re-enter your Jellyfin server details.



  • One thing you may want to update - listing Tor’s logging policy as “No Logs” is a bit misleading, that’s really more of a voluntary recommendation for individual Tor exit relay operators.

    Tor exit relay operators absolutely can store logs of outgoing connections if they choose to. And technically they could even snoop on non-secure traffic if they choose, there’s a reason you should be using HTTPS if you’re going to use Tor for clearnet browsing.

    Of course most Tor exit relay operators aren’t going to do these things but it’s all voluntary, seems incorrect to claim all exit relay operators follow no log principles.

    EDIT: Also AFAIK you can’t forward a port from the clearnet through a Tor exit relay’s public IP address back to your own Tor client, Tor doesn’t do port forwarding like that. It’s definitely not needed to run Tor Browser (and Tor VPN I think) but that isn’t needed for any of the other VPNs either, a bit confusing how you listed that one.


  • Agreed, if OP is going to add Tor in a “VPN” list then may as well add I2P. I2P + outproxies are pretty much the same thing as Tor + Tor Exit Relay. It’s not the best way to utilize I2P but the option does exist.

    Then again neither Tor nor I2P should be in a “VPN” list, the whole thing seems more of a VPN provider topic.



  • My Sony Trinitron served me well back in the day - But no, I don’t miss the CRT era. Just too huge and heavy. And honestly I don’t remember the generic non-Trinitron CRTs being anything special, they were kind of shitty.

    Anyways I thought the CRT thing is just collectors/old school gamers looking to display older media on a proper CRT? Obviously people with a lot of space, garages, basements, etc… people in tiny rooms and apartments need not apply LOL.

    This whole article seems a bit off.