Not able to setup HTTPS on jupyterhub on kubernetes


I am not able to set up https on jupyterhub on Kubernetes. I have used helm chart 0.9.0 and 0.9.1. I am using helm 3.

The challenge is that I am not even able to see the auto https pod and my site is only working on HTTP not on https.

Here is my config.yaml

    type: dummy
        password: 'mypassword'
            - user2
        enabled: true
        type: "letsencrypt"
        - jupyter.xxxcom
    secretToken: "xxxx"

And this is my helm command

helm upgrade --cleanup-on-fail --install $RELEASE jupyterhub/jupyterhub --namespace $NAMESPACE --create-namespace --version=0.9.0 --values config.yaml

I can see only these pods

Screenshot 2020-09-09 at 11.51.14 PM

Any pointers on what should I do to enable https?

1 Like

Hi Abhinav,
I’ve run into similar problems with Jupyterhub on Kubernetes. Did you ever make headway on this issue? I had read in another forum that 0.9.0/0.9.1 had issues related to ACMEv2 needs, or something along those lines. I changed to 0.10.6 which did allow for the auto https pod to start up but it unfortunately still failed for reasons that weren’t apparent to me. I ultimately just manually set up the certs as I have before, but it’s something we’re very eager to implement.

It’s been a while since I looked at this myself, but I also ran into some issues using LetsEncrypt; looking at the (proxy?) logs I recall seeing that an ACME error.

My workaround was to serve the challenge payload manually using a VM on the public IP, e.g. GitHub - nginx-proxy/docker-letsencrypt-nginx-proxy-companion: LetsEncrypt companion container for nginx-proxy

1 Like