Deluge GTK client often detaches from daemon

[_DH_]

I've not been able to figure out why this is, but since I started using it as a daemon, I've had problems with the client often disconnecting from the daemon. I'm currently running Deluge 1.3.7 on Debian, and even though the daemon keeps running and it doesn't affect the torrents, it's annoying that I have to reconnect to the server quite often to see what torrents are active. Both the daemon and the client are running on the same system, one I connect to through XRDP. Anyone with any ideas? The problem often seems to surface when I've looked away for some time, like it's a timeout or something. Yet I don't see any such setting in the configuration.

[gwodus]

I can confirm this behavior. At first I also thought there is some sort of auto disconnect. But it seems like it stays connected for different amounts of time.

Both, client and daemon, are currently at version 1.3.10. But I had this problem since I am using deluge (since 1.3.6).

My client is on Windows 7, Python 2.6.
My daemon runs on Raspbian, Python 2.7.
Both systems are on the same local network.

Both log files show nothing.

[gggirlgeek]

I am also having this problem. But it happens even while I'm working in the client, so I don't think it's based on inactivity.

Client: Win7x64, Python 2.7, v1.3.13
Daemon on Seedbox: Debian, Python 2.7, v1.1.13

[m-p{3}]

I wish there was an option to auto-reconnect with an interval. I often have to tell my Thin Client to reconnect to the remote daemon.