For some reason, when sockets are reset on the remote server running serialization, they don't seem to correctly pick back up the signal. This will require some more testing to understand what exactly is happening. This issue is likely related to the fact that the server that is requested is built on the same exact hosting system. Perhaps localhost should be used instead.
This issue was unrelated to server serialization and instead and issue with a certain previous version of the serialization code. Updating to the most recent versions fixed this problem.
For some reason, when sockets are reset on the remote server running serialization, they don't seem to correctly pick back up the signal. This will require some more testing to understand what exactly is happening. This issue is likely related to the fact that the server that is requested is built on the same exact hosting system. Perhaps
localhost
should be used instead.