Jupiter-notebook – LarryLai https://larrylai.com 兼聽則明 偏聽則暗 Sat, 02 Apr 2022 01:24:13 +0000 en-GB hourly 1 https://larrylai.com/wp-content/uploads/2017/03/larrylai_com-favicon.png Jupiter-notebook – LarryLai https://larrylai.com 32 32 SSL Key Ownership https://larrylai.com/ssl-key-ownership/ https://larrylai.com/ssl-key-ownership/#respond Sun, 09 Feb 2020 07:39:51 +0000 http://larrylai.com/?p=3775 Issue: After receiving renewal notice from Let’s Encrypt for Jupyter server, go to the virtual machine hosting Jupyter and renew the key successfully. But cannot login to the jupyter notebook from https. Solution Remove the symbolic link of privkey.pem under /etc/letsencrypt/live/[mydomain]/privkey.pem recreate the symbolic link with the dedicated user running Jupyter notebook. Run command as […]

The post SSL Key Ownership appeared first on LarryLai.

]]> Issue:
After receiving renewal notice from Let’s Encrypt for Jupyter server, go to the virtual machine hosting Jupyter and renew the key successfully. But cannot login to the jupyter notebook from https.

Solution

    1. Remove the symbolic link of privkey.pem under 
      /etc/letsencrypt/live/[mydomain]/privkey.pem
    2. recreate the symbolic link with the dedicated user running Jupyter notebook.
    3. Run command as root: 
      systemctl restart jupyterhub

Tricks

      • As the jupyter server is run by the ownership of a dedicated user, after the renewal, the private key, i.e. privkey.pem must be owned by this user. However, I run the command: 
        certbot renew --standalone

        under root.

      • note that let’s encrypt command for CentOS 6 is quite different from CentOS7

Config

    • OS: CentOS 7
    • Jupyter-notebook: 5.7.8

The post SSL Key Ownership appeared first on LarryLai.

]]> https://larrylai.com/ssl-key-ownership/feed/ 0