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
ConnectTimeoutError running on mybinder.org #48
Comments
The infrastructure and code was updated to flow all traffic over port 80. mybinder.org now works with our example notebooks. |
Hello, I am having also an apparent connection error icesat2.init("icesat2sliderule.org", verbose=True) Then, I can't connect to server. This is the error: ERROR:sliderule.sliderule:Connection error to endpoint https://sliderule.icesat2sliderule.org/source/version ...retrying request ERROR:sliderule.sliderule:Connection error to endpoint https://sliderule.icesat2sliderule.org/source/version ...retrying request Traceback (most recent call last): Best regards Julius |
Hi @jujara. Thanks for asking and providing error messages. You are pointing to the old endpoint. You want: |
Using the binder link in the repository readme to run sliderule on mybinder.org a user quickly encounters the following error running
icesat2.init("icesat2sliderule.org")
This seems to be related to egress settings on mybinder.org (only certain ports are allowed), because the code runs fine on other deployments such as the pangeo binder on AWS. The mybinder.org configuration is here: https://github.com/jupyterhub/mybinder.org-deploy/blob/f6dfb4ab34af8cc4419fdf52c7e20c9a8eff0b39/mybinder/values.yaml#L48
The docs for those settings are here https://zero-to-jupyterhub.readthedocs.io/en/latest/administrator/security.html?highlight=networkpolicy#limiting-network-access-from-pods-egress
Is port 8500 an arbitrary choice? Is there a possible workaround to run sliderule from systems that have such egress rules set?
#6
The text was updated successfully, but these errors were encountered: