# Setting Up HTTPS for Jupyterhub on Kubernetes

**URL:** <https://discourse.jupyter.org/t/setting-up-https-for-jupyterhub-on-kubernetes/292>\
**Category:** JupyterHub\
**Created:** [January 1, 2019, 7:37pm UTC](https://discourse.jupyter.org/t/setting-up-https-for-jupyterhub-on-kubernetes/292 "2019-01-01T19:37:47Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![ethan92429](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.jupyter.org/ethan92429/32/166_2.png) [@ethan92429](https://discourse.jupyter.org/u/ethan92429)\
**Post date:** [January 1, 2019, 7:37pm UTC](https://discourse.jupyter.org/t/setting-up-https-for-jupyterhub-on-kubernetes/292/1 "2019-01-01T19:37:48Z")

</div>

Hello, when I use [https://zero-to-jupyterhub.readthedocs.io/en/latest/security.html](https://zero-to-jupyterhub.readthedocs.io/en/latest/security.html) to set up https, I get the following error:

Upon putting the following instructions into my config.yml for my google kubernetes cluster setup with the defaults from the guide:

```auto
https:
    hosts:
      - my_domain.com
    letsencrypt:
      contactEmail: my_email

```

under the proxy entry within the config.yaml, I get the error: `UPGRADE FAILED: no ConfigMap with the name "nginx-proxy-config" found`. If I remove these lines and run the entry again, the upgrade succeeds… any suggestions on what could be causing this error?

---

<div class="post-metadata">

**Author:** ![yuvipanda](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.jupyter.org/yuvipanda/32/17_2.png) [@yuvipanda](https://discourse.jupyter.org/u/yuvipanda)\
**Post date:** [January 1, 2019, 9:14pm UTC](https://discourse.jupyter.org/t/setting-up-https-for-jupyterhub-on-kubernetes/292/2 "2019-01-01T21:14:31Z")

</div>

Heya! I think you are running into this helm bug: [https://github.com/jupyterhub/zero-to-jupyterhub-k8s/pull/620](https://github.com/jupyterhub/zero-to-jupyterhub-k8s/pull/620)

If your upgrade succeeds after you remove it, can you add it back and try again? Usually that works for me.

---

<div class="post-metadata">

**Author:** ![ethan92429](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.jupyter.org/ethan92429/32/166_2.png) [@ethan92429](https://discourse.jupyter.org/u/ethan92429)\
**Post date:** [January 1, 2019, 11:36pm UTC](https://discourse.jupyter.org/t/setting-up-https-for-jupyterhub-on-kubernetes/292/3 "2019-01-01T23:36:42Z")

</div>

Hi @yuvipanda thanks for the reply!

I just tried commenting out the https, upgrading the chart and waiting for deployed status, then I uncommented the https code, attempted to upgrade the chart, and I got the same error as before. Any other suggestions?

---

<div class="post-metadata">

**Author:** ![yuvipanda](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.jupyter.org/yuvipanda/32/17_2.png) [@yuvipanda](https://discourse.jupyter.org/u/yuvipanda)\
**Post date:** [January 1, 2019, 11:48pm UTC](https://discourse.jupyter.org/t/setting-up-https-for-jupyterhub-on-kubernetes/292/4 "2019-01-01T23:48:12Z")

</div>

Hmm, can you pass --debug and --dry-run flags to the helm upgrade command and show us the output? Note that this is going to have some secrets you might wanna strip out…

Another thing to try is to do a `helm list`, find the revision number of your release that is failing, and then do a `helm rollback` to earlier revision numbers until it works fine. I’ve used that with success many times.

Also make sure you’re on the latest version of helm. The issue is a fundamental architectural problem in helm, and should be removed with helm 3.

---

<div class="post-metadata">

**Author:** ![ethan92429](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.jupyter.org/ethan92429/32/166_2.png) [@ethan92429](https://discourse.jupyter.org/u/ethan92429)\
**Post date:** [January 10, 2019, 4:04am UTC](https://discourse.jupyter.org/t/setting-up-https-for-jupyterhub-on-kubernetes/292/5 "2019-01-10T04:04:20Z")

</div>

Hi @yuvipanda, just got back into trying this. I ran with the flags you mentioned and I got [this log.](https://gist.github.com/ethan92429/d7e098c522db17dcffd9148a2f64272d) This is a totally vanilla installation… I tried your suggestions, and the suggestions in the PR you linked, but the deploy with https options stays failed. Any other suggestions? Thanks for all your help thus far! If it makes any difference, I’m using gke.

---

<div class="post-metadata">

**Author:** ![minrk](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.jupyter.org/minrk/32/13_2.png) [@minrk](https://discourse.jupyter.org/u/minrk)\
**Post date:** [January 10, 2019, 10:20am UTC](https://discourse.jupyter.org/t/setting-up-https-for-jupyterhub-on-kubernetes/292/6 "2019-01-10T10:20:17Z")

</div>

extraConfig expects to be a dict of configs:

hub:  
extraConfig:  
part1: |  
…

Maybe that will fix the latest error?

---

<div class="post-metadata">

**Author:** ![ethan92429](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.jupyter.org/ethan92429/32/166_2.png) [@ethan92429](https://discourse.jupyter.org/u/ethan92429)\
**Post date:** [January 20, 2019, 5:00pm UTC](https://discourse.jupyter.org/t/setting-up-https-for-jupyterhub-on-kubernetes/292/7 "2019-01-20T17:00:04Z")

</div>

I ended up rolling back on helm to the last working version, then updating again and that seemed to do the trick. I guess I hadn’t been rolling back correctly before. Thank you very much for the help!

---

<div class="post-metadata">

**Author:** ![aurashn](https://avatars.discourse-cdn.com/v4/letter/a/a6a055/32.png) [@aurashn](https://discourse.jupyter.org/u/aurashn)\
**Post date:** [April 18, 2019, 5:06pm UTC](https://discourse.jupyter.org/t/setting-up-https-for-jupyterhub-on-kubernetes/292/8 "2019-04-18T17:06:06Z")

</div>

Hey @ethan92429, Did you actually make any change or just try the upgrade again and it worked?