Errors when running Rust Server and trying to connect with RustAdmin (a tool for running rust server_

I have another topic running on this issue here: http://oxidemod.org/threads/rustadmin-rcon-tool.5682/page-88#post-221630

When trying to connect with rust admin, I get this in the server console is this:

7/3/2016 1:16:56 PM|Fatal|<>c__DisplayClass6.b__5|WebSocketSharp.WebSocketException: An exception has occurred while reading an HTTP request/response. ---> System.IO.EndOfStreamException: The header cannot be read from the data source./200]
at WebSocketSharp.HttpBase+<>c__DisplayClass1.b__0 (Int32 i) [0x00000] in :0
at WebSocketSharp.Ext.EqualsWith (Int32 value, Char c, System.Action1 action) [0x00000] in <filename unknown>:0 at WebSocketSharp.HttpBase.readHeaders (System.IO.Stream stream, Int32 maxLength) [0x00000] in <filename unknown>:0 at WebSocketSharp.HttpBase.Read[HttpRequest] (System.IO.Stream stream, System.Func2 parser, Int32 millisecondsTimeout) [0x00000] in :0
--- End of inner exception stack trace ---
at WebSocketSharp.HttpBase.Read[HttpRequest](System.IO.Stream stream, System.Func`2 parser, Int32 millisecondsTimeout) [0x00000] in :0
at WebSocketSharp.HttpRequest.Read (System.IO.Stream stream, Int32 millisecondsTimeout) [0x00000] in :0
at WebSocketSharp.Net.WebSockets.TcpListenerWebSocketContext..ctor (System.Net.Sockets.TcpClient tcpClient, System.String protocol, Boolean secure, WebSocketSharp.Net.ServerSslConfiguration sslConfig, WebSocketSharp.Logger logger) [0x00000] in :0
at WebSocketSharp.Ext.GetWebSocketContext (System.Net.Sockets.TcpClient tcpClient, System.String protocol, Boolean secure, WebSocketSharp.Net.ServerSslConfiguration sslConfig, WebSocketSharp.Logger logger) [0x00000] in :0
at WebSocketSharp.Server.WebSocketServer+<>c__DisplayClass6.b__5 (System.Object state) [0x00000] in :0

Start with WebSocketSharp.Server.WebSocketServer and the HttpBase.readHeaders stack frames shown in the report. Reproduce the connection attempt from RustAdmin and compare the request handling with the external discussion linked in the issue. Done means identifying the cause of the EndOfStreamException and confirming that the affected connection no longer produces the fatal server error.