but always struggled with getting it to show which device was making the call
This depends on how you have your devices setup to use your DNS. For e.g, in my home I have my Phone and PC setup to use the IP of my AdGuard server. In AdGuard, I have them as named devices. All other devices on my network use the router as DNS, so all other requests that are not coming from my PC or Phone indicate "router" as the name.
What’s your use case look like?
Home based server running AdGuard forwarded through a caddy reverse_proxy to a domain. Using DoH/3 so even when remote I use my own DNS. Works great.
I would say there's no value in assigning such a tight definition on self-hosting--in saying that you must use your own hardware and have it on premise.
I would define selfhost as setting up software/hardware to work for you, when turn-key solutions exist because of one reason or another.
Netflix exists. But we selfhost Jellyfin. Doesn't matter if its not on our hardware or not. What matters is that we're not using Netflix.
Escaping vendor lock-in. It's why people hate the cloud when it used to be the answer for everything. You make a good product that can only be used with your hardware/software, whatever, and people run from that shit because it's abused more often than not.
Apple is the biggest example of this. Synology is getting worse and worse. Plex not far behind either.
To the surprise of absolutely no one. Tends to happen when you cultivate one of the most tixic online spaces on the net. I've never asked a question on SO, but just the verbiage used to accost people just trying to learn is just insane. Mods don't really care about post content as long as its not perceived as "hostile," so you can be generally as passive aggressive and shitty as you want. It's just...weird.
You can find especially viperis content when you find a question which has been answered, but someone is just like "Well, this isn't the way that I do it!" etc, and then go on a tirade about how the question was asked poorly and the answer doesn't completely answer the question.
This was the winning argument for my boss for migrating to a modern server.
Exceptionally good news! Glad it's working out. Be sure to make a new post when you decide what you go with, I'm sure people here would enjoy hearing about your approach.
If documentation is written in a readable and confluent way, RTFM isn't such a big deal. The issue comes with overly draconian and non-confluent documentation.
Port 8096 is the default HTTP protocol port, and you're trying to access it via HTTPS. Do you have certificates installed and available for your jellyfin instance? If not, it's very likely Cloudflare won't route it correctly.
I'm not saying this is your specific issue, but it'll be the one after you fix this one at least. You may need to mess with the cloudflare "current encryption mode" to get this to work.
Ahh yes, as evidenced by absolutely nothing whatsoever, I mean Jesus Christ, the GNU ideologue is completely antithetical in every possible way to your statement...
GNU's goal is to give computer users freedom and control in their use of their computers and computing devices by collaboratively developing and publishing software that gives everyone the rights to freely run the software, copy and distribute it, study it, and modify it.
You have less than zero idea what you're speaking about....
Because why run one server for all your needs when you can double up, right? /s