Hello cosmos,
Thank you for your message.
Our developers are currently looking into the information and log files that Rob had provided regarding the issue. However, please note that similar issue had occurred in the previous version of RU Server (3.1) for some users - this issue was already fixed in the most recent update for RU Server (version 3.2.0.0) which resolved the issue for everyone who has reported it to us before the update was released. Perhaps, in this specific case the issue might be caused by something else.
Meanwhile, you can try updating your current RU Server installation to the most recent version
3.2 - the issue should not occur after the update since it was already fixed in the latest update, but even if it does - we will make sure to assist you in resolving it as fast as possible and you can always temporarily downgrade your RU Server back to the previous version without losing any connections/settings.
The latest version of RU Server 3.2 is available for download on
this page.
Hope that helps.