# Question regarding setting up HTTPS with Tailscale

**URL:** <https://community.umbrel.com/t/question-regarding-setting-up-https-with-tailscale/9114>\
**Category:** Support and Troubleshooting\
**Created:** [August 17, 2022, 12:25pm UTC](https://community.umbrel.com/t/question-regarding-setting-up-https-with-tailscale/9114 "2022-08-17T12:25:42Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![BharatKalluri](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.umbrel.com/bharatkalluri/32/3151_2.png) [@BharatKalluri](https://community.umbrel.com/u/BharatKalluri)\
**Post date:** [August 17, 2022, 12:25pm UTC](https://community.umbrel.com/t/question-regarding-setting-up-https-with-tailscale/9114/1 "2022-08-17T12:25:42Z")

</div>

Hi, I’ve installed Umbrel. Setup Nextcloud & Tailscale on the install. Later enabled MagicDNS and switched on HTTPS on Tailscale admin console.

Later ran `tailscale cert <domain>` inside the Tailscale docker instance, it succeeded. But when I try to visit the https domain I get an err saying `ERR_CONNECTION_RESET `. I ran the same command from the instance where I installed umbrel (on the host machine, not the docker) and that also seems to not make a difference. I don’t think I fully understand as of yet how certs are managed by Tailscale.

What am I missing?

---

<div class="post-metadata">

**Author:** ![ravine.storewide416](https://avatars.discourse-cdn.com/v4/letter/r/bc79bd/32.png) [@ravine.storewide416](https://community.umbrel.com/u/ravine.storewide416)\
**Post date:** [August 30, 2022, 12:51pm UTC](https://community.umbrel.com/t/question-regarding-setting-up-https-with-tailscale/9114/2 "2022-08-30T12:51:43Z")

</div>

I’m attempting the same thing but can’t even figure out how to run ‘tailscale cert’ to assign a certificate.

How did you manage it?

---

<div class="post-metadata">

**Author:** ![ravine.storewide416](https://avatars.discourse-cdn.com/v4/letter/r/bc79bd/32.png) [@ravine.storewide416](https://community.umbrel.com/u/ravine.storewide416)\
**Post date:** [August 30, 2022, 2:49pm UTC](https://community.umbrel.com/t/question-regarding-setting-up-https-with-tailscale/9114/3 "2022-08-30T14:49:12Z")

</div>

Update just for reference, I managed to obtain the certificate by running the following command whilst ssh’ed into Umbrel:

`sudo docker exec -it tailscale_web_1 tailscale cert [tailscale machine name].[tailnet domain alias]`

Where tailscale machine name and tailnet domain alias were assigned in the [Tailscale.com](http://Tailscale.com) machines and DNS settings.

I found the name of the docker container using `sudo docker ps` which listed a container name for both web and Tor and ran the command in the non-Tor container.

This appeared to run successfully and create the necessary files on the server, but as with OP when I attempted to visit the domain whilst connected to Tailscale I also received the message:

`ERR_CONNECTION_RESET`

Any Tailscale/DNS/TLS/HTTPS experts amongst us?

---

<div class="post-metadata">

**Author:** ![boosterstage](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.umbrel.com/boosterstage/32/1021_2.png) [@boosterstage](https://community.umbrel.com/u/boosterstage)\
**Post date:** [September 19, 2022, 2:17pm UTC](https://community.umbrel.com/t/question-regarding-setting-up-https-with-tailscale/9114/4 "2022-09-19T14:17:35Z")

</div>

In the Tailscale admin console, under Services, a list is presented of all running services. In mine, port 443 is not listed. I think the solution is to open port 443 in the Nginx config. However, the nginx.conf file will be overwritten when the software is updated, so this is not a good solution.

> [@Request: Support Tailscale HTTPS](http://community.umbrel.com/t/request-support-tailscale-https/9519):
>
> Tailscale now supports HTTPS ([https://tailscale.com/kb/1153/enabling-https/](https://tailscale.com/kb/1153/enabling-https/)). This is useful for some apps that could be exposed through the Tailscale tunnel, such as the Bitwarden desktop app, which does not support Tor. Currently, the Umbrel Nginx config does not expose port 443. This can be done by modifying the nginx.conf file, but this is not recommended. It would be great if the Tailscale app, when installed, would open up port 443 and advertise it as a Tailscale service.

---

<div class="post-metadata">

**Author:** ![John2](https://avatars.discourse-cdn.com/v4/letter/j/f0a364/32.png) [@John2](https://community.umbrel.com/u/John2)\
**Post date:** [September 26, 2022, 6:32am UTC](https://community.umbrel.com/t/question-regarding-setting-up-https-with-tailscale/9114/5 "2022-09-26T06:32:34Z")

</div>

Using Tailscale HTTPS would be fast, secure and convenient were it supported on Umbrel. Using Tailscale means we don’t need to open up ports to the internet which is very appealing to users like me.

And Tailscale is much much much faster than Tor. By a long shot.

Please work on this feature. It would be of huge benefit to many users.

---

<div class="post-metadata">

**Author:** ![Jufg](https://avatars.discourse-cdn.com/v4/letter/j/57b2e6/32.png) [@Jufg](https://community.umbrel.com/u/Jufg)\
**Post date:** [February 13, 2023, 5:41pm UTC](https://community.umbrel.com/t/question-regarding-setting-up-https-with-tailscale/9114/6 "2023-02-13T17:41:16Z")

</div>

Does anyone know how I need to override the Nginx conf to make tailscale HTTPS work? Even if I would have to do it again after each update?

---

<div class="post-metadata">

**Author:** ![AirHache](https://avatars.discourse-cdn.com/v4/letter/a/8dc957/32.png) [@AirHache](https://community.umbrel.com/u/AirHache)\
**Post date:** [June 29, 2024, 9:45am UTC](https://community.umbrel.com/t/question-regarding-setting-up-https-with-tailscale/9114/7 "2024-06-29T09:45:14Z")

</div>

Hello,

Bumping this topic. Is there a way to make HTTPS work?  
I can’t see a way to enable it on Umbrel console, and I’m not willing to modify nginx conf.
