Open mikropsoft opened 3 months ago
I agree, this is extremely important, but I don't know if it is easy to implement.
You’d have to wait on the Umbrel developers to decide whether they want to implement HTTPS support.
I agree, this is extremely important, but I don't know if it is easy to implement.
I assume what they'd have to do is use certbot
to generate an SSL, and have whatever they use (say nginx) be able to use that SSL.
Is this really a security issue if you're accessing your Umbrel without https via tailscale? Isn't the traffic between you and Umbrel always encrypted as long as connected to Tailscale?
Is this really a security issue if you're accessing your Umbrel without https via tailscale? Isn't the traffic between you and Umbrel always encrypted as long as connected to Tailscale?
I don't think its a major security issue with Tailscale, but still. What if you don't want to use Tailscale?
My contribution: https://r.je/guide-lets-encrypt-certificate-for-local-development
I am still searching for solutions to make a way to run .local domains using SSL. I have found two different approaches using a very useful method to improve security on Umbrel.
https://smallstep.com/blog/private-acme-server/ - It's a private ACME SERVER that can easily run over Traefik.
Nginx Proxy Manager is now available on the app store. You can use that to request SSL certificates and expose certain apps to the internet.
Edit: If you wish to encrypt communications in your local network, I have created a app for that. More Info here
I decided not to create a new issue, I think the situation is similar to mine. The problem is that I need to put Umbrel on the network.
I've done this in several ways:
In all cases I get the same error.
It seems that somewhere in the source code there is a hardcoded address addressing via http, which is not supported under https
@LastSkywalkerER It seems that somewhere in the source code there is a hardcoded address addressing via http, which is not supported under https
Yes you are correct, the http
is currently hardcoded, There is PR open which would fix this: #1841
Most likely, that PR will be merged in the next release. For now the workaround will be to manually add your domain to the file.
@sahilph developed a module for httpsizer the Umbrel. My suggestion is that Umbrel add that module to core.
I want to expose Umbrel to the external network, but when I do so with a domain that has an SSL certificate, I receive a warning similar to the one I mentioned in issue #1832.
Opening Umbrel on the external network via HTTP doesn’t inspire confidence. This support should be implemented urgently. I kindly ask all developers to take this into consideration.