-
Notifications
You must be signed in to change notification settings - Fork 8
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
Unable to connect to kachery nodes from network with restricted web access #20
Comments
@alexmorley anything else I should add here? |
Hi @shashwatsridhar, you mention you have "restricted web access". Maybe you are not able to establish an outgoing connection to that IP address? Are you able to use a different computer or a different network? |
I am able to use a different computer (my own) which is not in the Janelia network, and I am able to download datasets. Moreover, when I route my traffic through the Janelia VPN, I cannot access the dataset descriptions on laboratorybox.org (for eg. this). The page loads, but only the text "Loading..." is shown. I am wondering if the two issues are related, and maybe provide more insight into what might be wrong? I could download the datasets to a system outside the network (say, to my PC), and re-upload them to the remote system via ssh, but that's a pretty inefficient method to access the data. So I thought I'd post an issue and see if there are any solutions you might have (like choosing the right port, or so). |
Sounds to me like the Janelia network is blocking websocket connections (which would affect both the website and the kachery daemon). I don't have a solution at the moment, unfortunately. |
@shashwatsridhar can you open the "network" tab of developer tools and click reload and post a screenshot while on labbox? It might be because the websockets don't use ssl (they are ws:// as opposed to wss://) which would be fixable. |
I can confirm it is using ws:// rather than wss:// @alexmorley, perhaps we can chat about how to convert this to wss. I am deploying using kubernetes (and linode). Maybe there is an easy way to adjust this. I only have one reference to ws:// in the source code. So maybe we just add an "s" and update something on the kube config? |
Hey,
I'm unable to download datasets to a system connected to a network with restricted web access (located at the Janelia campus). The
kachery-p2p-start-daemon
command issued from the system fails to initiate the connection required to access datasets. The output is as follows:I'm trying to download the datasets using the script provided at scripts/download_recordings.py, which obviously fails with the following error:
The conda environment used was created using the instructions given in the readme for this repo. No additional packages were installed.
Thanks!
The text was updated successfully, but these errors were encountered: