Selfhosted

You don't. Unless you want your hobby to turn into a 24/7 support job.

Once you agree to letting friends and family access your hosted services, you become the tech support for any problems. Whether that be your fault, user error, etc. You should absolutely limit who you give access to. In my case, only three people can and that's immediate family. No friends, no extended family. I don't wanna deal with all that mess when I deal with it at work. Don't over extend yourself by being nice.

Using Cloudflare is against the ToS when used for services like Jellyfin. Your account can be limited, closed, or find yourself getting a several hundred dollar bill for data usage because you've breached the terms of service. Additionally, streaming content on free accounts incurs higher latency which I've confirmed myself Argo smart routing massively reduces. https://github.com/jellyfin/jellyfin/issues/9295 - Don't abuse what's free or you may lose it.

Google shouldn't be indexing your domains anyway. If it's flagged your domain, it's been indexed and scanned. Alternatively, it could indicate you have a weak point somewhere on your server and you've been breached. Google's scan picked up whatever it was. Though I doubt this is the case and just a false positive. Double check your robots.txt files and disallow everything. Most index bots respect this. You can use a community sourced bot blocker. https://github.com/mitchellkrogza/nginx-ultimate-bad-bot-blocker

I've been running my own self hosted services for almost a decade. Though I have a background in IT directly doing this kind of stuff daily at work. As long as you have a strong firewall, modern TLS, relevant security headers, automatic tools like fail2ban, and have a strong grasp on permissions, you should be fine. Before I moved everything to non-root docker, it was given its own service user and SELinux policy. Using direct DNS isn't so much of a problem. You shouldn't have any issues. Feel free to reach out if you have any questions.

i have a public ip and my own domain attached to that. i use subdomains for each service and a dashboard on the root domain.

i don't use authelia etc, and rely on the autentication page of each service. but i have fail2ban.

i did help them set up the apps, but they took from there. the dashboard on the root domain helps them navigate all services without having to remember the full url.

Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:

[Thread #99 for this sub, first seen 1st Sep 2023, 07:25] [FAQ] [Full list] [Contact] [Source code]

I haven't tried this yet I've only read about it. You can add an authenticator app + reverse proxy in front of HTTP services like Jellyfin. The combination Authelia + Traefik is often mentioned. When the person tries to open up the Jellyfin web app they see an Authelia screen asking for username + password, which when provided goes away and whitelists their public IP for a configurable time period. They don't have to input the user+pass on the TV, they can visit the Jellyfin web app on their phone or laptop, then it will work for all devices behind that public IP. This would allow things like TV sets or Chromecast to work transparently.

How did you get your domain flagged as malicious? Are you on a noip or similar domain?

I don't have any answers for the jellyfish, but I host my seafile on the internet, so my family can access it, and haven't had any issues yet 🤞

I share my Home Assistant with family, Nextcloud and Jellyfin with family and friends and websites/blog with the entire world.

I do it with a domain and a subdomain for each service. Each website/service has it's own Let's Encrypt SSL cert managed by Traefik. So all the family members and friends need is the URL and usernames and passwords. Like any other service. I don't know what you did to become flagged as malicious by Google, but my services have run for years without such an issue. So maybe it's just time to switch to a different domain name?

I have a domain which points to my router (over dynamic DNS). My parents' Router connects to my home network via Wireguard using that. All my services have subdomains, for which I have set static DNS records that point to the local address (192.168...) of my server. This way, I only need to expose Wireguard to the public.

In regards to media server, may want to go with Plex over Jellyfin as you will find it much easier for those users who are not as technical and will offer support to far more devices which sounds like what you are looking for.