Yes, Google has miss reported my websites in the past, all of which were valid, but the person I'm replying to seemed to assume no-SSL is a requirement of the feature, and he doesn't understand that a wrong/missing SSL is indistinguishable from a Phishing attack, and that the SSL error page is the one that warns you about phishing (with reason).
Nibodhika
joined 2 years ago
It is for pull requests. A user makes a change to the documentation, they want to be able to see the changes on a web page.
So? What that has to do with SSL certificates? Do you think GitHub loses SSL when viewing PRs?
If you don't have them on the open web, developers and pull request authors can't see the previews.
You can have them in the open, but without SSL you can't be sure what you're accessing, i.e. it's trivial to make a malicious site to take it's place an MitM whoever tries to access the real one.
The issue they had was being marked as phishing, not the SSL certificate warning page.
Yes, a website without SSL is very likely a phishing attack, it means someone might be impersonating the real website and so it shouldn't be trusted. Even if by a fluke of chance you hit the right site, all of your communication with it is unencrypted, so anyone in the path can see it clearly.
While YUNO is a great way to get started, I strongly encourage you to understand basic concepts, like docker, and maybe try to run something outside of it for fun. While not even remotely the same thing since YUNO is just the OS and "app store", you would be very similarly tied to that ecosystem the same way you are to Google now. Not to mean that YUNO would have any control over your stuff, but you would be dependent on them for what you can self host.
Ok, so, there are multiple things you should be aware.
First of all you've set that DNS to be 10.0.0.41, that range of IPs is reserved for lan, similar to 192.168.0.41 would be. Only people in the same local network as you might be able to access it.
Also, usually your home router doesn't use the 10.x.x.x range, but some ISPs might do it in their internal network, which means your router doesn't get an internet IP, instead your ISP router does and it shares the same external IP with different houses, so you would need to use something like https://www.whatsmyip.org/ to know what your external IP is.
But there's more, since you don't control that router putting that external IP in the DNS won't work either.
You need to do something more complicated, I recommend you read on cloud flare tunnels for example.
And one final piece of advice, don't share your urls with randoms on the internet, security by obscurity is not security and all, but publicly advertising your url is asking for trouble, even without doing that you will see several attempts of logging into your servers constantly.
I have Jellyfin running for years too and it has never broken for me, I use Linuxserver image, so maybe they delay the updates a bit?... Now, Immich has broken so many times that nowadays is the only docker I don't keep at latest (and I know using latest is a bad practice, I understand the reasons, but the convenience of not worrying about the versions beats all that for me)
It would be very tedious to type all of that on my TV, even if I could get mpv on it, and my TV/projector had hardware capabilities to decode the media, not to mention the difficulty in keeping my history between different devices or for different people. You're clearly not understanding the problem Jellyfin solves, it's like someone saying "why do we need Lemmy when we can write files on our samba shares" (which btw you should definitely not expose to the internet)