Hey everyone,
I’m one of the people who still used proton and am now in the process of switching everything and trying to selfhost more.
I sucessfully setup Vaultwarden. I also decided I should move away from having my dockers publicly exposed with nginx reverse proxy and switched everything over to netbird. Im using their proxy feature now to access everything with custom domains and followed a tutorial to setup a bring your own proxy server on a vps. So now all my services are only accessible when my netbird vpn is active. I also spun up a pihole docker and added that to my netbird dns servers to try and get ad blocking on my mobile devices. So far so good.
I wonder however that while some webui’s like vaultwarden run with https, others like radarr dont. Is this a problem or does it not matter so much since i have the vpn running?
I dont really understand how I would go about making them https though. Im on unraid for my dockers and don’t see why some use https and others don’t.
Sorry if this is a convoluted post, I’m quite in over my head with all the networking and dns stuff and just hoping I’m not doing something stupid.
Thanks for your help!
53 comments
log in to comment.
short answer (and the safest one) is yes, use HTTPS always.
However, if and only if a service you are using is confined locally or via your privately hosted VPN (this just means not available over the public internet) you are probably OK without, unless there are other people on your local network who might be interested in snooping.
with your VPN (looks like netbird in this case) you should be OK, as the VPN handles encryption in the absense of HTTPS.
For more research checkout LetsEncrypt. its a super simple way to setup SSL (Which generally makes up the S part in HTTPS) and it’s free.
i think many of us started like you. you’ll get there, you’re just about to learn a lot of stuff before you do.
I just want to point out that it’s not just other people who might be interested in snooping. Compromised smart home equipment is a big potential vector of attack if services are unencrypted on your home network.
Relevant XKCD: xkcd.com/1966/
Websites exist just to look through exposed pc’s files and webcams, or used to at least
And that’s why IMHO they all need to be segregated in a VLAN with limited/no Internet access.
I suggest you should treat your own network as at least a little compromised.
Most houses run something that has a residential proxy, browsers like Chrome are happy to snoop on your local network, and apps and smart devices are completely free to use your network as they see fit by default.
Anything that has sensitive data should be handled via https.
agreed. this is part of the reason i have separate VLANs for my server, IoT network, Management network, guests, and home computers. I also consciously try not to use programs like Chrome and all my traffic goes through OPNSense/Unbound DNS.
i realize not everyone has the equipment for / can do all of that though. And that despite all of that and more, I’m still compromised to anyone with dedication. or a fucking ai
Just to add, to avoid connecting via HTTP outside the VPN by accident, you can set the firewall/docker to accept connections into that port only through the VPN’s ip address
if you’re accessing over the internet, always use TLS/HTTPS.
if you’re accessing over LAN, you should still use TLS/HTTPS.
just because you’re hosting the app locally doesn’t mean the JS embedded in the page is safe. HTTPS will ensure that all your traffic is encrypted so only you and the server knows what it contains.
if the JS on the page is unsafe then HTTPS wouldn’t help right? The JS could scrape all the info client-side and extradite it.
AFAIK the reason why you’d use HTTPS on your LAN is if you’re afraid of middleman attacks in your LAN, like a malicious device that pretends to be the internet router.
it would if it’s importing something else.
let’s say your site is on app.home.com and your js is locally sourced. then that JS was injected with an import from vuln.evil.com.
I’m pretty sure your browser would block it based on the fact that the document domain is using HTTPS and HSTS would block it based on not using HTTPS.
I think. never really tried this out tbh.
Wait what does embedded JS have to do with it? If it’s HTTPS the JS will still run and still be able to do whatever it did before AFAIK.
Adding to this, the only time I dont use HTTPS/TLS is when I am accessing localhost, prior to moving a service to a subdomain to give it HTTPS/TLS…
Always use HTTPS. Especially if you’re using your services on mobile.
Imagine you’re on your friend’s WiFi, and you disconnect from your net bird/tailscale/wireguard connection to your self hosted network… Any and all mobile apps that require that secure connection, is going to attempt requests to your internal services and sending auth/session token details along the requests.
A bad actor on your friend’s WiFi network, could, in theory, capture these requests and now you’re at the mercy of how well those services are written.
This all may sound a bit paranoid, but it is what we are trying to mitigate here.
It’s not even that hard to imagine, this is exactly what rogue wifi access points do. It’s surprisingly common for wifi access at places like coffee shops to be compromised and used to silently conduct these types of attacks. The people that set them up are not very knowledgeable and also they don’t ever check up on them as long as they keep working.
This is also why you want to enable HSTS on top of your HTTPS, so that rogue requests to downgrade the connection to plain HTTP are ignored.
Another good idea is to place all the services that should only be accessed over VPN only in private DNS (home LAN DNS and the VPN’s DNS), never in public DNS. A simple and effective way of doing that is to place them on a deep subdomain like
*.private.example.comrather than*.example.com. That way if your VPN drops when you try to resolve those subdomains you don’t get any response anymore and there’s no connection for the rogue wifi to hijack.Yep! Definitely don’t add any of your internal domains on public DNS services. Be careful requesting SSL certs for the child subdomains too. They will show up on transparency logs like on shodan.io. Use internal DNS, and wild card certs for these things. And obviously, do not expose your ports publically.
I’m not sure I understand this. If I’m on my phone and connect using wire guard or teleport and I’m connected to a public wifi, I don’t understand the risks. Can you explain them? Thanks, I genuinely don’t understand. I thought encrypted tunnels were safe?
Sometimes your connection might not work correctly, and you’re not connected to your secure network. Like how VPNs will have kill switches (prevents you from accessing the Internet if the connection to the VPN isn’t successful) to prevent leaks during those spotty connections. Without HTTPS, during those spotty connection times, you’re sending your auth/session details plain-text on an unsafe network.
Yes, always use HTTPS, even on local networks if there ever are more than one device on the network.
The way to handle services with/without HTTPS is to put everything behind a reverse proxy that automatically handles certificates. Since you’re using NGINX, you can try setup certbot, or switch to something like Caddy that has certificate handling built in. If you have all your Docker containers on one server, you can look at Traefik.
Question: I have a remote VPS running Caddy, which sends requests through a WireGuard tunnel to my OPNsense router, which then forwards them on to my VMs running Nextcloud and Jellyfin. Is it possible to use the same certificate locally? Whenever I access the services locally, I have to use http because apparently generating a self-signed certificate locally conflicted with the Caddy-generated certbot certificate.
Probably if you move Caddy to the local VM and then forward the ports 80 and 443 to the VPS through WG. So the VPS receives all requests, but instead of going through Caddy first and then through WG, they go straight through WG and into Caddy on your local VM. Then you can access Caddy both locally and externally through the VPS-WG tunnel.
I have no experience setting this up though, I don’t have a VPS in front of my lab.
If you’re not using https, then anyone who can see the traffic in your VPN can see everything you do.
Whether that’s a problem depends. In principle, as long as access to your VPN is restricted to people you trust, then http inside it is fine. In practice, if your security isn’t perfect, and someone gets access to your VPN, then https provides a meaningful second line of defense.
My recommendation would be to never use http for anything where a breach would be really painful. It’s good that vaultwarden is on https. Beyond that, https is absolutely the best practice, but if someone getting access to your service is only a mild inconvenience, then leaving it on http is fine as long as it’s only accessible inside your VPN - the risk is relatively low, and the consequences aren’t bad.
A reverse proxy like Caddy can get a ssl cert via dns challenge and add ssl to all your internal self hosted services, provided you have a domain hosted somewhere supported.
With everything behind tailscale, and hence no need for opening the firewall, my DNS challenge failed when I tried to set it up last time using certbot.
Yes, because an attacker already in your network will be able to view non SSL traffic.
I even have my unRAID endpoints using https. You can do self signed, or you can use something like let’s encrypt to do it for you. I use wildcard certs as any signed certs with the full subdomain can expose what services I host internally (since signed certificate provisioning is, by design, a public process).
Yes you do.
First of all, there are services that will refuse to work properly on http only. Specially if you want an SSO like authelia, will not work over http
Second, modern browsers will complain when using plain http if the website has forms to fill or passwords to write … very annoying, but it’s the way it is.
Third, having the “this site is not secure” broken lock is not very nice for users. At best they might complain, at worse they will get used to “unsecured” websites and .ight end up easier prey for fake sites in the future. Yes I mean wife or kids. These are things normal users should not see as normal…
Last, if you expose anything to the web, please never ever do that without proper https with certificates from let’s encrypt.
Yes especially since https is to setup and maintain.
It’s not a problem, but it does matter. With plain HTTP traffic everything you send and receive from a given site is unencrypted, so anyone in the chain delivering your package can read what you’re doing, collect your passwords and do all kinds of shenanigans. If it’s just your local network which is secured from the public internet then it’s pretty much just you who can intercept that traffic and it’s generally fine, as you already have all the passwords and such. And if you connect to the services via VPN that takes care of ‘secured from public interenet’ -part of the equation.
HTTPS is the same traffic, but encrypted with certificates. To achieve that you’ll need to have a server certificate and then browsers can use the public part of certificate to encrypt your traffic. With docker that’s commonly achieved either with docker-proxy or external proxy like nginx. Your computer already has a bunch of certificate authorities which it trusts and they are bundled in your operating system and/or browser. Without a trusted certificate your browser throws a warning about it, but if you proceed with ‘untrusted’ certificate the traffic will still be just as strongly encrypted as it would be with a ‘known’ certificate. The catch is that anyone can create their own certificates, so there’s no guarantee if the server actually is what it claims to be. For example I could sign my own certificate for gmail.com and offer that to users and steal their passwords. That would of course be trivial to figure out as the browser wouldn’t show the “good” lock symbol on address bar, but the certificate would be technically speaking a working certificate.
Now, to get a certificate for your own services you need to either build your own certificate authority and add that to trusted list of your devices or obtain a certificate from a already known authority like letsencrypt. With letsencrypt (and other similar services) you need to provide a proof that you own a domain which you’re obtaining the certificate for, so with those you can’t get a certificate for gmail.com or any other random domain name. Letsencrypt uses ‘certbot’ tool to validate certs, other services ask for spesific DNS entry or something else for proof that the domain is actually yours. But the main part is that all the ‘commonly known’ certificate authorities work only on publicly available services and domains (a bit simplified explanation, but that’s roughly it).
But once you have the certificate you’ll need to configure something on your network to use it. Actual best practice and configuration depends on the service you’re running. If your services run only on your local network and they are never allowed to public internet you’re likely fine to run everything without HTTPS encryption, but it’s still good to understand the differences and effects between unencrypted and encrypted traffic.
HTTPS for everything means you have to buy into the cartel of “identity providers” that manage DNS and certificates, even if there are some mostly-good actors in there such as Let’s Encrypt, you still have the external dependency. As we have seen with cases such as Austistici, having that dependency can be a problem. It’s your call if it is in your case or not, but I wanted to raise this point because no one has pointed out that particular weakness vector so far in the thread.
In a very general sense, if your services are under a netbird or any sort of VPN where you control who gets account access or not, you “should not need” HTTPS. Might still be convenient to have.
Well you could technically also use self signed certificates. But it requires a bit more work as well as installing your own custom CA cert.
Self signed isn’t quite the same as a internal CA
Yeah I oversimplified but doing the whole thing your self is possible.
All you need is a DNS name. You can buy one for a few dollars.
Even if you refuse to buy a domain you could always run your own certificate chain
That sounds interesting. But then you have to convince your peers to install your certificate root, right?
No, you would only use this internally. Overall doing this is a bad idea (if the root gets stolen encryption is useless) but is technically possible if you are looking for a learning exercise. It would be about the same amount of work as Let’s encrypt since you would probably still want to run ACME with fairly short certificate lifetimes.
I use tailscale serve for my selfhosted stuff. (Safari on my phone won’t let me open http sometimes)
Get a better browser? HTTP is as legit a transmission protocol as HTTPS and email are.
All mobile browsers are safari wrappers on iphone
Hmmm, I’d… say… “get a better phone”, but there’s not much of a better alternative there.
Get a desktop / laptop computer?
Are you joking? I use my phone to access frontends I host on my pc lol, why would I use my phone if im at my pc
There’s no cartel, you can buy a HTTPS cert from lots of places all over the world. Most domain registrars can set you up. It just won’t be free like Let’s Encrypt and also will have a very different renewal process (most likely once a year manually rather than every 90 days automatically).
It’s a cartel in the sense that the CA/Browser forum determines, on their own whim, which CA gets featured or revoked in your browser. And single-handedly impose technical restrictions like shorter cert lifetimes and less features. Stuff like eMudhra being able to compromise everyone shows its quite a vulnerable group of single-point failures as well, but still condoned by almost everyone.
ZeroSSL and Komodo does have free certs if I remember correctly. They’re still bound by the 90 days (soon to be 47) limit though
So, HTTPS prevents people on the network from hijacking the connection or spying on what you do with the website or your passwords. If you have a VPN and no evil devices inside your network you are likely fine, and many things don’t need HTTPS-level of safety.
That said, browsers make using HTTP almost unusable nowadays, because over the internet you really want your connection to not be hyjacked, and almost nobody self-hosts (sadly).
I would reccommend to set up a reverse proxy to do https for all services you host, even if you only use it via lan/vpn. Adding a new service then becomes just hosting it over HTTP, and have your reverse proxy converting the connection to HTTPS.
If you have a domain, you can request a wildcard cert from let’s encrypt and use that also for internal domains (they don’t need to be reachable from the public internet, but you might need to expose the ACME challenge file).
If you want to learn a lot about certificates you can go the self-signed route, but you’ll have to install the certificate on every device you use to access your services (guests will get huge warnings when trying to access your pages, if you give them access to them). Once set up it’s more flexible though, and if you configure your dns server you can have whatever domain you want, even nonexistent or unavailable ones.
Back when I joined Lemmy (and before I understood what .ml was), I tried to contribute to the project. I suggested updating a link (possibly to docs) that was using an HTTP connection. The goal at the time was to make Lemmy approachable for normal users. As a user, I have non-secure sites blocked in my browser, so I have to manually proceed… and seeing that warning makes me not want to use a site. The devs told me that the link didn’t matter because the site was static. That was the end of my being willing to contribute, and my monetary support for the project ended as soon as I understood the dev’s beliefs and personalities.
For me, everything exposed to the internet is https (that is http + Apache reverse proxy using Let’s Encrypt), and everything that is not (and I access via my tailnet) is http.
If the access is only over VPN then http is fine, that’s how I access my arr setup. You can create certificates and manually upload them to radarr and other sites but it’s not necessary.
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:
[Thread #162 for this comm, first seen 8th Nov 2026, 18:10] [FAQ] [Full list] [Contact] [Source code]
[deleted]
If nothing’s exposed and it’s all behind Netbird, you don’t strictly need it. I still would, because apps like Vaultwarden’s web vault won’t load without a secure context. A wildcard cert via DNS challenge is a one-time setup. Everything else is optional.
Even though it’s not strictly required if you’re only using your services over your local network or a VPN, your browser won’t know that’s what you’re doing. The security warnings got so incredibly annoying for me that I switched to using https on everything.
There are also some specific web features that only work over https (including some optional upgrades needed for Nextcloud iirc)
Some features like copying to your clipboard will only work if you’re using https
Most (if not all) reverse proxies will allow you to add a certificate for your sites locally. I run everything over wireguard when I’m outside my network, and have NGINX Proxy Manager for all my routing and certificate needs. Works flawlessly so far.
Https with X.509 is full of holes.
You should be using client side encryption using a pinned certificate.
If nothing else, use Tor Onion Services.
Bro what? The exit nodes see all traffic unencrypted in Tor
Nope. Onion Service’s traffic is end to end encrypted.
And it’s a pinned key that cannot be mistaken, because the .onion address is a derivative of the hash of the Key’s fingerprint.