Closed kaijagahm closed 8 months ago
Could it be that you have an application that has already taken port 1234? Cytoscape/CyREST listen on than port for RCy3/py4cytoscape requests.
Entirely possible. Do you know how I would go about checking that? I have a very rudimentary understanding of ports.
This would depend on whether you're on a Mac or PC. I don't have a Mac, but the commands would translate closely.
netstat -a | find "1234"
Try this when Cytoscape is not running. If this command produces any output, you know that there's a process already listening on that port.
If you find a listener on port 1234, you can find out which application it is if you have administrator privileges. Use this command:
netstat -ab
This will output to the console. Look for the listener for 1234 and see the application name on the next line.
Good luck!
I tried that, and it looks like there is nothing using port 1234.
This might be a stupid question, but is Cytoscape running? If it is, when Cytoscape starts a dialog may appear that asks if it should allow network connections (be sure to click allow)
Cytoscape is running, yes. But I got no such dialog. I can go digging around in the settings and see if I can find it, though.
Usually a restart of Cytoscape works resolve this issue. If not, I would next try a complete reboot.
I've already tried restarting Cytoscape; you're saying a reboot of the computer? I can try that now.
Aha! That fixed it! I restarted my computer and now the connection works.
Thank you all for your (very prompt) help. I appreciate it.
Hi there! I'm having trouble using any functions in RCy3 because of, apparently, a problem connecting to Cytoscape.
Here is an example:
Created on 2024-02-27 with reprex v2.1.0
I just installed Cytoscape and RCy3 yesterday and reinstalled R today, so I don't think I have old versions. Based on the indicator to check whether CyREST was installed, I attempted to manually install it, but I ran into an error with Java when I did that. Here is my
sessionInfo()
.Created on 2024-02-27 with reprex v2.1.0
Any thoughts on what might be going wrong?