Sorry to hear that billyboy12
I'm sorry to say that these kinda situations unfortunetly are out of my hands when general deluge issue and so need to be reported upstream as deluge2 issue preferably with debug logs if possible.
I can connect fine here, to both windows and Linux hosts with other libtorrent versions too, so some special annoying hard to debug thing.
I can only build and pack the components up and add little tricks and small fixes here and there, mostly coming from others, but that's unfortunetly also only the entirety of my abilities here. Sadly.
This has been reported before several times with people using this installer, and before there where slight chance it was this installers fault, but not anymore, because the change to newest python fixed that little loophole for issues that where open before(mismatched dll's from system32).
One reported it happened when connecting, and then when I asked him to try with clean config dir, then it didn't happen, but then later said adding a torrent made it crash, which is something reported back all the way from deluge1 too, and never fixed unfortunetly.
Another had this happen on one pc, but not the other, with same installer version installed, and connecting to same other host.
My only small suggestion is delete session.state file if available, from both host and client in there respective profile dirs, as mixing libtorrent versions also is an old potential-crashing bug from deluge1 times never fixed, and I workaround in installer by deleting locally during install. However, when connecting again locally before connecting to remote host, then will need done again, I guess, though I don't know at all if is that issue, but just know can be an issue, though don't know if needs done both places either, but just guessing here.
Its probably not even the above though in your case, and some other general deluge issue, as if searching there are countless different types of crashing reports for deluge, and it's stated to be really hard to solve as not reproducible for the devs, and if finding exact way to reproduce(for all), then submit ticket with logs if possible, though I'd say make tickets regardless, just to inform of problem.
One older post of deluge1 had random crashes and when Cas suggested to try py2.7 instead of py2.6 installer, as been updated, then fixed it atleast in the time tested initially, but I seen this reported here also in the previous py versions, and so it's not a general python problem.
Again, I'm sorry you're having these issues, and that I cannot help you out.