Rust+ Update causing crash due to missing port mapping

[alanman87]

Describe the issue you are having Answer: Server crashes

What was you doing before it happened Answer: Running the container

Screenshots N/A

What are you running on (please complete the following information):

• OS: Unraid
• Browser Chrome
• Hardware: AMD 3900x 64GB DDR4

Additional information Rust+ is enabled by default with the update. This requires TCP port 28083 to be mapped in the container. See error below

6/4/2020 10:41:00 PM|Fatal|WebSocket.<startReceiving>b__170_2|System.ObjectDisposedException: Cannot access a disposed object.
Object name: 'MobileAuthenticatedStream'.
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <437ba245d8404784b9fbab9b439ac908>:0
at Mono.Net.Security.MobileAuthenticatedStream+<StartOperation>d__58.MoveNext () [0x001bf] in <ae22a4e8f83c41d69684ae7f557133d9>:0
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <437ba245d8404784b9fbab9b439ac908>:0
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0003e] in <437ba245d8404784b9fbab9b439ac908>:0
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x00028] in <437ba245d8404784b9fbab9b439ac908>:0
at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x00008] in <437ba245d8404784b9fbab9b439ac908>:0
at System.Runtime.CompilerServices.TaskAwaiter`1[TResult].GetResult () [0x00000] in <437ba245d8404784b9fbab9b439ac908>:0
at System.Threading.Tasks.TaskToApm.End[TResult] (System.IAsyncResult asyncResult) [0x0002e] in <437ba245d8404784b9fbab9b439ac908>:0
at Mono.Net.Security.MobileAuthenticatedStream.EndRead (System.IAsyncResult asyncResult) [0x00000] in <ae22a4e8f83c41d69684ae7f557133d9>:0
at System.Net.Security.SslStream.EndRead (System.IAsyncResult asyncResult) [0x00006] in <ae22a4e8f83c41d69684ae7f557133d9>:0
at WebSocketSharp.Ext+<>c__DisplayClass54_0.<ReadBytesAsync>b__0 (System.IAsyncResult ar) [0x00002] in <7126fb4f5c5b40029458a4f975f98d13>:0

[labalicious]

Any luck with this? Would love to have Rust Companion on my Unraid docker container as well.

[Sgtsmi1es]

@alanman87 can we just map the port to the container for now in unraid until @mdarkness1988 updates the docker?

[alanman87]

@alanman87 can we just map the port to the container for now in unraid until @mdarkness1988 updates the docker?

I tried this and had no luck. I abandoned this container because it has clearly been abandoned. I ended up running a VM and found it to be more stable anyway.

[Sgtsmi1es]

thats too bad, this was a good docker, thanks for the reply @alanman87

[mdarkness1988]

Hi. Sorry guys been busy with other stuff too. Tell me the issue and will try resolve it

On Mon, 10 Aug 2020, 18:15 Sgtsmi1es, notifications@github.com wrote:

thats too bad, this was a good docker, thanks for the reply @alanman87 https://github.com/alanman87

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/mdarkness1988/Rust-Server/issues/27#issuecomment-671480178, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKDVBYFX4K6SATKSEQYX4FLSAATKPANCNFSM4NTHMMKA .

[labalicious]

Hi. Sorry guys been busy with other stuff too. Tell me the issue and will try resolve it … On Mon, 10 Aug 2020, 18:15 Sgtsmi1es, @.***> wrote: thats too bad, this was a good docker, thanks for the reply @alanman87 https://github.com/alanman87 — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#27 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKDVBYFX4K6SATKSEQYX4FLSAATKPANCNFSM4NTHMMKA .

I think what needs to happen is that a port is designated and open in the container for Rust+ Companion app to work. https://wiki.facepunch.com/rust/rust-companion-server

Making it work For most people, the only requirement for the companion server to work is to make the app.port TCP port accessible over the internet. Port forward, open it, add firewall rules for it.

The default port is the game port + 67, or the RCon port + 67, whichever is the larger number. If you haven't changed any ports that means it will be 28082. This port must be 10000 or greater for Rust+ to connect to it.

If you have a more complicated networking setup where you need to specify which NIC to listen on then you'll need to set the app.listenip convar to its IP address. You can check the connection settings the server is currently using with the app.info command. If the IP address that the app connects to is incorrect, you can set it app.publicip to the value you need.

If you get errors about companion server registration or push notifications aren't working then make sure your server can access companion-rust.facepunch.com over the internet.

[Sgtsmi1es]

@mdarkness1988 thanks for touching base, we all really appreciate the work you do, hands down the best docker for unraid servers I have found. If there is any way I can help or test let me know.

[mdarkness1988]

So can you tell me what is needed axactly as in ports needs a different range etc.

I am back to work with this now. Only thing is I can't test this docker anymore just edit it.

[Sgtsmi1es]

I'll happily test it, here is the whitepaper on what port to use: https://wiki.facepunch.com/rust/rust-companion-server here is a post from folks who have setup their own servers: "The wiki states default port should be 28082, which is +67 above the default game port (if you left it at default - 28015), but it really should be +67 above the RCON port (28016, also default) since it's the higher port number. So, if you didn't change the default ports and which to use the Rust+ app with your self-hosted server, make sure you're using TCP 28083

If you're still unsure, just open F1 console in game and type app.info and that's the IP:port the app is listening on and that's what should be forwarded through your firewall/router."