Pycharm 4.5.3 remote console "cannot connect to remote process"

Starting today, for no apparent reason, the Pycharm remote will not connect to the remote server.

All other functions work fine, SSH session, deployment configuration, skeleton updates, file syncing, etc. I am running Pycharm 4.5.3 on Windows7x64 on a remote server running Centos6.5x64 on AWS, please note that this setup has been working fine for a couple of months until today.

In the console window, when starting the remote console, the following output appears: timeout takes about a minute:

sftp://user@FQDN:22/home/user/Envs/lab1/bin/python2.7 -u /home/user/.pycharm_helpers/pydev/pydevconsole.py 0 0
Couldn't connect to console process.
Process finished with exit code -1

      

Invalid log output (C: \ Users \ user \ .PyCharm40 \ system \ log \ idea.txt):

2015-07-09 17:15:07,910 [ 236325]   INFO - esdk.transport.JschExecProcess - Executing ssh command: env "PYTHONIOENCODING"="UTF-8" "JETBRAINS_REMOTE_RUN"="1" "IPYTHONENABLE"="True" "PYTHONUNBUFFERED"="1" /home/user/Envs/lab1/bin/python2.7 -u /home/user/.pycharm_helpers/pydev/pydevconsole.py 0 0 for user@FQDN:22

      

The following troubleshooting steps yielded nothing: workstation / server, reboot, fresh Virtualenv, different Python version, reinstalling iPython, uninstalling iPython, reset console / deployment config, connecting from another workstation with the same version from Pycharm, update Pycharm from 4.5.2 to 4.5.3.

Suggestions for further troubleshooting steps are happily welcome while I wait for Jetbrains support to get around my ticket!

+3


source to share


1 answer


The problem was with the security configuration on AWS.

My AWS instance has a friendly FQDN to go with an unfriendly AWS internal name which seems to be causing some havoc with how their NAT works unless you have a rule to allow traffic from an IP bound to the FQDN. back server. I created an issue yesterday when my office router was reset, to a new IP address, I had to overwrite the recursive rule with a rule allowing my new IP address in this instance.



So add a rule allowing the server's public IP for all traffic and Pycharm reconnects when specified in the FQDN.

+1


source







All Articles