@possiblylinux127 Only when you have a valid domain name.
Not everybody can or wants to pay for a domain name, when it is not really necessary.
@possiblylinux127 Only when you have a valid domain name.
Not everybody can or wants to pay for a domain name, when it is not really necessary.
@inquanto Theoretically, when you are alone in your own network it can be ok, to go only with http. But login passwords over http are transferred without encryption.
The problem with https are valid certificates, so that clients can connect to your selfhosted services without issues.
For example, I was not able to connect with a KDE PIM program to a Nextcloud with a self signed certificate or with http only.
With step-ca there can be a solution for this problem:
https://jan.wildeboer.net/2025/07/letsencrypt-homelab-stepca/

@captcha_incorrect Currently I’m running my personal services similar to you using Podman Quadlets and I really like it.
I have also a testing installation of Proxmox on another system, but I’m also not so clear, if it would be a good way for my purposes.
@possiblylinux127 A domain creates dependencies on external infrastructure.
Let’s Encrypt and the Internet Security Research Group are U.S. organizations that rely on donations and can very likely be restricted by instructions from the American government.
Don’t get me wrong, if you want to use your own domain, you could do so.
But this creates dependencies for self-hosting, which may not be wanted and/or probably also not necessary.