Reset server to completely clean state for TLJH install?

I successfully installed TLJH with https access on a cloud server (ubuntu), but something got broken when I tried to configure for auth0. After trying several things that didn’t work to fix it, I tried to go back to a completely clean slate with the following:

sudo systemctl stop jupyterhub
sudo systemctl stop traefik
sudo rm -rf /opt/tljh
sudo rm -rf /usr/local/bin/tljh-config
sudo rm -f /etc/systemd/system/jupyterhub.service
sudo rm -f /etc/systemd/system/traefik.service
sudo systemctl daemon-reload
sudo rm -rf /etc/traefik
sudo rm -rf /etc/letsencrypt
sudo find /opt -name "*tljh*" -exec ls -ld {} \;
sudo find /etc -name "*traefik*" -exec ls -ld {} \;
sudo find /etc -name "*jupyterhub*" -exec ls -ld {} \;
sudo rm -f /etc/systemd/system/traefik.service
sudo rm -f /etc/systemd/system/multi-user.target.wants/traefik.service
sudo systemctl daemon-reload
sudo rm -f /etc/systemd/system/jupyterhub.service
sudo rm -f /etc/systemd/system/jupyterhub.service~
sudo rm -f /etc/systemd/system/multi-user.target.wants/jupyterhub.service
sudo systemctl daemon-reload
sudo rm -f /etc/sudoers.d/jupyterhub-admins

After the above, I reinstalled with
curl -L https://tljh.jupyter.org/bootstrap.py | sudo -E python3 - --admin <admin name>

On the positive side, that did at least get me back to having working http access. Then I ran

sudo tljh-config set https.enabled true
sudo tljh-config set https.letsencrypt.email <my email>
sudo tljh-config add-item https.letsencrypt.domains <my domain>
sudo tljh-config reload

which resulted in the following output

active
Hub not ready: (HTTP status 502)
Hub not ready: (HTTP status 502)
Hub not ready: (HTTP status 502)

… (repeated every second)

And now even http access returns a “bad gateway” error. (I’m able to restore it with
sudo tljh-config set https.enabled false
)

In summary, after breaking my previously successful https setup (with default authentication) by trying to enable auth0, I’m now unable to even get back to that working state. I have to assume that something that should have been cleaned out before reinstalling wasn’t. What am I missing?

It’s possible it’s just a coincidence, reinstalling everything would require a completely new certificate to be requested. Try checking the logs for all components, and share them here if you’re still stuck.

1 Like