HTTPS access after basic installation
Hello, I am new to Runtipi - after giving Cosmos a quick try.
My objective is to set-up a local Homelab reachable only from my local network (not Internet reachable/no remote access need so far)
I've installed 4.3 release and later upgraded to 4.4.0-beta.4 version.
So far i've faced 2 issues :
- RunTipi Home icon not working as expected : known bug. https://github.com/runtipi/runtipi/issues/2260 Fixed in 4.4.x releases. I confirm it is now fixed.
- HTTPS access not working : I always get a 404 page not found page.
I've tried to change my SSL port, change the domain (replace example.com by a Dyndns hostname)
My state/settings.json is pretty basic
sudo docker logs runtipi-reverse-proxy mentions ERR Unable to obtain ACME certificate for domains error. I wonder if it is related.
Having HTTPS access to Runtipi working out of the box is of interest for all people having security in mind. How do you do get it working ?
Thanks for any help guys.
GitHub
[REQUEST] Clicking the logo should link to dashboard · Issue #2260...
Is your feature request related to a problem? Please describe. I'm always frustrated when I click the Runtipi logo in the navbar expecting to go to the dashboard, but it currently links to the ...
7 Replies
I have the same issue
If you want to access your homelab only from your local network, you have multiple solutions. In all cases, you need to keep the default 80 and 443 ports. Here are the 3 solutions:
1. Use IP + Port, this is by far the easiest, downside is that you have to remember IPs and ports or use the dashboard each time. Traffic is not encrypted. Could be read by someone else on your network
2. Use a local domain. This is a good in between solution, you setup your local domain in the settings like
tipi.lan
and you download the certificate and install it on all your devices. It requires you to setup a custom DNS in your network or write in the hosts files of all of your devices to point tipi.lan
-> runtipi IP. Can be a bit annoying to maintain on all devices and renew certificates when they expire. Guide: https://runtipi.io/docs/guides/local-certificate.
3. Use a DNS challenge. By far the best solution but requires you to own a domain and to tweak the runtipi traefik config to setup a DNS challenge. With this solution, you'll have automatic working domain + SSL for all devices in your network with one central setup on the runtipi server. Guide: https://runtipi.io/docs/guides/dns-challenge-cloudflareThanks a lot @Nicolas . Solution 2 is the one I was trying to set-up. I forgot to add tipi.local in my /etc/hosts (compulsory). https://IP-addresss does not work we have to use https;//tipi.local . And For those who use Firefox don't forget to add the Certificate to Firefox CA store - it does not use system CA store. Will now try to get more & more familiar with RunTipi (alternate stores, create my own store) and will contribute.
Hello Nicolas. Thanks for your answer. I don’t want to hijack the thread of @numero6 but for me I choose the option with the dns-01 challenge.However, it would be great to have an improved documentation in this regards because the current one is not really clear in my opinion especially when it comes to runtipi own dashboard. I was able to get it working but I don’t know if what I’ve done is the best.
Yes i agree, it would be nice to rewrite the docs
can you please make a separate post and delete this one here? thx
Done