-
Notifications
You must be signed in to change notification settings - Fork 336
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
InsecureRequestWarning After enabling letsencrypt #454
Comments
I meet the same error
|
I get the same:
|
Same here
|
I think this is resolved by #357! |
This is still happening right now for me. I have just installed TLJH from https://tljh.jupyter.org/bootstrap.py changed some bits of configurations and then I can't apply them since Let me know if I should open a separate issue with more details instead of this "footnote" on closed issue. |
This issue persists with an existing SSL as well. Constant InsecureRequestWarning loop. |
In case others land here and feel stuck, there is still something like a race condition or other issue that cause a loop of these warnings, which eventually clears. That is "normal" (should not, but we can live with it). In some other circumstances, the finite loop becomes infinite. It is very annoying to not see the reason, but double checking everything should allow one to find the solution. In my case, it was an incorrect value set in the field |
This issue still exists. I don't get stuck in a loop, but I keep getting warnings when reloading the hub (not the proxy):
@consideRatio : #357 does not fix this, as it seems to only disable these warnings for upgrades specifically. I assume a similar fix could be done for tljh-config reload. Or maybe some sort of hostname configuration needs to be done, so the SSL requests to 127.0.0.1 get redirected to the domain? |
Sometimes the errors don't go away when I mess with configuration, perhaps implying that other errors are clobbered.
Related, but closed issues, appear to be:
pip freeze output:
Running on Ubuntu LTS on Google Cloud per instructions here https://the-littlest-jupyterhub.readthedocs.io/.
The text was updated successfully, but these errors were encountered: