How do I setup jupyter notebook public server using let's encrypt on Windows? I have zero knowledge about DNS, certbot, IIS.
http://jupyter-notebook.readthedocs.io/en/latest/public_server.html#using-let-s-encrypt the problem is that certbot does not work on Windows and there are plenty of unofficial clients for Windows. On Monday, May 2, 2016 at 6:29:54 PM UTC-5, Rob Pollock wrote: > > Hi Carol, > > I had a look at what you wrote and it seems to follow what I did pretty > well, so it should be fine for people to follow. > > One thing regarding letsencrypt is that, after installing the letsencrypt > client you can just run `letsencrypt certonly` at the command line (as > root, on linux). Then the script produces the certificates in a default > location, and you can then refer to that location in the jupyter config > file, or copy the certificates to an appropriate location. > > I'm not sure happens if you can't login as root or what you do if you're > running on windows (should still work I suspect). But if you have root > access, and you own the domain name (and you're running letsencrypt from > the host with that domain name!), it works very straightforwardly. > > Maybe it would be a good idea to investigate what happens if you're not > root, and what to do if you don't own the domain name. Probably talk > nicely to your local system administrator (as would advisable in any case). > > Best Wishes > Rob. > > On 3 May 2016 at 10:38, Carol Willing <will...@gmail.com <javascript:>> > wrote: > >> Hi Rob, >> >> Thanks for sharing your tips with all of us. I’ve opened a PR to document >> “Using Let’s Encrypt”. If you have time to review it, I would appreciate it. >> >> https://github.com/jupyter/notebook/pull/1417 >> >> Thanks, >> Carol >> >> Carol Willing >> Research Software Engineer, Project Jupyter @ Cal Poly >> Director, Python Software Foundation >> >> >> On 2 May 2016, at 14:44, Rob Pollock wrote: >> >> The problem was the way that I set up my certificates... it works fine >>> with >>> tornado (the web server that's used with jupyter). >>> >>> Basically, you just use the "fullchain.pem" (from let's encrypt) as your >>> "certfile" and "privkey.pem" as you key. >>> >>> Pretty obvious really, no different to using a self-signed certificate. >>> I >>> was just getting hung up over the 'c.NotebookApp.client_ca' option... I >>> put path to "fullchain.pem" there and tried to use "cert.pem" as my >>> certfile. To be honest, given the naming scheme it makes sense, >>> however >>> posts on the letsencrypt forum set me straight. >>> >>> Just in case someone else has this issue. >>> >>> The cool thing is with letsencrypt you can access your (jupyter) notebook >>> from anywhere, and since the certificate is in a signed keychain >>> authority, >>> browsers don't complain. >>> >>> > -- You received this message because you are subscribed to the Google Groups "Project Jupyter" group. To unsubscribe from this group and stop receiving emails from it, send an email to jupyter+unsubscr...@googlegroups.com. To post to this group, send email to jupyter@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/eb4bda6f-bd96-4be3-8924-25c2c7c203b6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
