Use encryption with jupyter notebook batch job

Feature Requests and Roadmap Discussion
1

Hello,

every time I spawned a new jupyter server I am seeing this warning message in the output.log file:

[W 09:29:06.320 LabApp] WARNING: The notebook server is listening on all IP addresses and not using encryption. This is not recommended.

I was wondering if it’s possible to enable jupyter encrypted notebooks on OpenOnDemand.

So I edited my before.sh.erb:

openssl comand to generate mycert.pem and mykey.key
...
cat > "${CONFIG_FILE}" << EOL
c.NotebookApp.ip = '*'
c.NotebookApp.port = ${port}
c.NotebookApp.certfile = u'${HOME}/mycert.pem' 
c.NotebookApp.keyfile = u'${HOME}/mykey.key'
...
rest of the file

But now when I launch the jupyter server, I am getting:

[W 12:21:05.158 LabApp] SSL Error on 9 (‘10.80.65.122’, 37846): [SSL: HTTP_REQUEST] http request (_ssl.c:1076)
[W 12:21:05.405 LabApp] SSL Error on 9 (‘10.80.65.122’, 37848): [SSL: HTTP_REQUEST] http request (_ssl.c:1076)

And the jupyter fails.

Any ideas?
Thanks a lot,
Daniel.

2

No one can help me?
Thank you,

3

Hi, sorry for the delay. Unfortunately, I don’t believe we support https backends right now. I’ll move this into the feature request category.

I wish I had more for you, I just don’t. There’s the technical aspect of determining when a backend is https and when it’s http that’s not very easy to fix right now.

4

Alright, I understand. Thanks a lot for your answer Jeff!

5

One of the things we are planning for OnDemand 2.0 is adding a sidecar proxy to run alongside apps like Jupyter so that the sidecar proxy can provide both the authentication and encryption instead of the Jupyter notebook itself. This might address your end goal, though in a different way than configuring Jupyter itself to use encryption.

1 Like