First time here? Check out the FAQ!

How reconnect to remote host after losing connection?

Is there a way to reconnect a remote debugging session without losing the current state?

I'm running WingIDE Pro v6.1.5-1, and I'm using remote debugging between my Windows 10 Pro host system and an AWS EC2 instance. For some reason (thank you, aws!), the SSH connection seems to have been lost. The project thinks some state hasn't been saved.

The editor thinks it's saved my files, but when I attempt to close the file I get a complaint that says "Failed to write remote project file tms_dev_covid_project:covid_project.wpr (opt.covid): <class 'filenotfounderror'=""> [Errno 2] No such file or directory: 'opt.covid/covid_project.wpr'" followed by another complaint that says "Some remote files could not be saved within 15 seconds. Please check the network and try again: tms_dev_covid_project:covid_project.wpr (opt.covid) The timeout for this is configured with the Network > Hung Connection Timeout preference."

The remote files are still there and have apparently already been updated.

Is there a way to reconnect, or should I just kill the local IDE instance (using task manager) and restart?

SomervilleTom's avatar
asked 2020-08-10 14:13:38 -0500
Wingware Support's avatar
Wingware Support
updated 2020-08-10 21:47:53 -0500
edit flag offensive 0 remove flag close merge delete


add a comment see more comments

1 Answer


You could try reconnecting from the Remote Hosts dialog by selecting the host and using the probe icon (the rightmost one), but it may not solve it if it's confusion on the IDE side and not the lack of connection This code has been rewritten and greatly improved in Wing 7, where it should just reestablish a connection to the remote agent and keep going (most of the time, anyway).

Wingware Support's avatar
Wingware Support
answered 2020-08-11 09:03:07 -0500
edit flag offensive 0 remove flag delete link


I do have W7 but the effect is still there. Killing the remote (by reboot or whatever) makes the debugger loose connection. The offered Probe does not re-setablish the connection. However switching between default and remote project does. It looks like the probe uses the same IP6 address which will have changed due to a reboot?

qwerty_ww's avatar qwerty_ww (2021-09-21 16:44:49 -0500) edit

What is the error from the probe in the Remote Hosts dialog? Wing generally uses ip4 not ip6. It's unlikely the ip4 address would change from a reboot even if using DHCP but you can check it with 'ip address' on the remote side (or possibly 'ifconfig' depending on type of system). Also, note that any debug connection is separate from the remote agent connection and even if the remote agent reconnect you need to separately restart the debugger or the Python Shell.

Wingware Support's avatar Wingware Support (2021-09-22 07:53:31 -0500) edit
add a comment see more comments

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account. This space is reserved only for answers. If you would like to engage in a discussion, please instead post a comment under the question or an answer that you would like to discuss.

Add Answer