China, so definitely not the same worker protections; but where I'm at, that kind of deduction isn't legal.
Darkassassin07
Any staff in the country using Android handsets, including those from Huawei or Xiaomi, will be provided with an iPhone 15, as a one-time purchase
Fuck off. If you're mandating what device I'm to use for work; you're going to provide said device free of charge, or shut the fuck up when I use whatever I like.
A Roku stick requires the Roku streaming service to be functioning to be useful. If there wasn't a service with streaming media, the stick would have nothing to stream.
In cases like this; it's still only artificially dependant on Rokus services.
The hardware is perfectly capable of streaming from any number of services, including entirely self-hosted solutions like Emby/Jellyfin/Plex; yet the device can be remotely bricked just by nolonger providing Rokus services to it.
I tend to drop the link into yt1s.com
Sometimes just for audio, sometimes for the full vid.
I'm rarely grabbing more than one video at a time though.
[re-commenting as I meant this to be a top-level comment, not a reply]
127.0.0.1 is the loopback address. Ie it's your computer trying to reach a service its hosting (prowlarr)/talk to itself. Sonarr/Radarr should be using this address as long as prowlarr+sonarr/radarr are on the same machine.
Prowlarr is either not running, or port 8080 is blocked by your firewall.
A paid plex share is a plex server that someone is running + selling access too.
This is against plex' terms, gets plex accounts banned; and in some cases, Plex (co) has taken rather drastic action by blocking entire VPS providers from reaching plex.tv; thus plex server software no longer functions on those VPS's at all.
Naturally, people selling shares want to maximize profit, so they use VPS providers on the cheaper end; resulting in cheaper VPS solutions being blocked for everyone.
Drink less paranoia smoothie...
I've been self-hosting for almost a decade now; never bothered with any of the giants. Just a domain pointed at me, and an open port or two. Never had an issue.
Don't expose anything you don't share with others; monitor the things you do expose with tools like fail2ban. VPN into the LAN for access to everything else.
and using DDNS
As in, running software to update your DNS records automatically based on your current system IP. Great for dynamic IPs, or just moving location.
Sure, cloudflare provides other security benefits; but that's not what OP was talking about. They just wanted/liked the plug+play aspect, which doesn't need cloudflare.
Those 'benefits' are also really not necessary for the vast majority of self hosters. What are you hosting, from your home, that garners that kind of attention?
The only things I host from home are private services for myself or a very limited group; which, as far as 'attacks' goes, just gets the occasional script kiddy looking for exposed endpoints. Nothing that needs mitigation.
Unless you are behind CGNAT; you would have had the same plug+play experience by using your own router instead of the ISP supplied one, and using DDNS.
At least, I did.
Oh god! The Chinese know how tight my shoes are? They could overthrow the entire globe with such devastating info!