April 16, 2015 at 7:57 am #36757
Ray identified the bug causing this yesterday night and if you update your copy the issue should be gone.
This was due to a change that modified how the non blocking socket was established.
Let us know if the update fixes it. Thanks.