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.
I always advocate for HTTPS. I run a caddy proxy and sidestep cloudflare all-together.
https://jellyfin:8096/
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.
It depends on the composition of the battery. The faster you charge the worse it is on the battery.
Not really surprising. It's always DNS. 😡
Likely. What I said has more to do with "we're next." If this is successful in France, other countries will follow suit or at the very least get pressure from the IP lobby to follow.
lmao this is exactly what I've been lookin for... Thanks! I just knew if I was a lazy fuck and sat on my hands someone would do the work for me eventually!
Because there are hot self-hosts in your area.
This is grim talk, but Wawa's is so great.
Ignoring the Constitution is how we got here. Ignoring it again because "we're the good guys" doesn't help. That's the exact same mentality Trump has....
Aaaand there it is...
Article II, Section 1: Function and Selection, Clause 8: Presidential Oath of Office;
Before he enter on the Execution of his Office, he shall take the following Oath or Affirmation:– I do solemnly swear (or affirm) that I will faithfully execute the Office of President of the United States, and will to the best of my Ability, preserve, protect and defend the Constitution of the United States.
Correct. Mine is 'jelly.domain.com' which bidirectionally forwards traffic between my domain and my home server.