We are testing a deployment of JupyterHub in Google Cloud. I had SSL working using LetsEncrypt. After about a week things stopped working. My intuition tells me that its related to the rate bounds of LetsEncrypt. We keep tearing down our Hub, so I imagine evrytime we spin it we are requesting a new certificate. LetsEncrypt mentions that in testing phase you can hit their staging servers using the --staging flag. Is there a way to pass this flag in the config.yaml?
Or is there a recommended way to handle SSL for a Hub that we keep deleting/starting frequently?
We are testing a deployment of JupyterHub in Google Cloud. I had SSL working using LetsEncrypt. After about a week things stopped working. My intuition tells me that its related to the rate bounds of LetsEncrypt. We keep tearing down our Hub, so I imagine evrytime we spin it we are requesting a new certificate. LetsEncrypt mentions that in testing phase you can hit their staging servers using the --staging flag. Is there a way to pass this flag in the config.yaml?
Or is there a recommended way to handle SSL for a Hub that we keep deleting/starting frequently?
Thanks!