1. Community
  2. Game Support
  3. Rust
Seeing a lot of errors after updatingNot An Issue
Posted 5 years ago
Last updated 5 years ago
#1
Updated this morning to v2.0.4660 Oxide that released an hour ago. Now receiving many red errors. Here are the red lines I receive when booting up server.

could not check for update to compiler.exe
Error: NameResolutionFailure

Server startup complete
SteamServer Connected
Failed to setup companion server registration: System.Net.Http.HttpRequestException: An error occurred while sending the request ---> System.Net.WebException: Error: NameResolutionFailure
at System.Net.HttpWebRequest.EndGetRequestStream (System.IAsyncResult asyncResult) [0x0003a] in <ae22a4e8f83c41d69684ae7f557133d9>:0 7 slprs 0b/s in, 0b/s out
at System.Threading.Tasks.TaskFactory`1[TResult].FromAsyncCoreLogic (System.IAsyncResult iar, System.Func`2[T,TResult] endFunction, System.Action`1[T] endAction, System.Threading.Tasks.Task`1[TResult] promise, System.Boolean requiresSynchronization) [0x0000f] in <437ba245d8404784b9fbab9b439ac908>: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.ConfiguredTaskAwaitable`1+ConfiguredTaskAwaiter[TResult].GetResult () [0x00000] in <437ba245d8404784b9fbab9b439ac908>:0
at System.Net.Http.HttpClientHandler+<SendAsync>d__64.MoveNext () [0x002e7] in <7ebf3529ba0e4558a5fa1bc982aa8605>:0
--- End of inner exception stack trace ---
at System.Net.Http.HttpClientHandler+<SendAsync>d__64.MoveNext () [0x00478] in <7ebf3529ba0e4558a5fa1bc982aa8605>: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.ConfiguredTaskAwaitable`1+ConfiguredTaskAwaiter[TResult].GetResult () [0x00000] in <437ba245d8404784b9fbab9b439ac908>:0
at System.Net.Http.HttpClient+<SendAsyncWorker>d__47.MoveNext () [0x000ca] in <7ebf3529ba0e4558a5fa1bc982aa8605>: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 CompanionServer.Server+<SetupServerRegistration>d__15.MoveNext () [0x0009e] in <0b99253a9cf644a6a361312aebe4f624>:0​
Posted 5 years ago
Last updated 5 years ago
#2
The bottom error are not related to Oxide, that is from the Rust+ companion app support.

The top error means your server can't connect to the site or internet.

It's likely that the solution for both would be to make sure the server is networking properly.
Posted 5 years ago
#3
5e13a8d5b2bc5.jpg Wulf
The bottom error are not related to Oxide, that is from the Rust+ companion app support.

The top error means your server can't connect to the site or internet.

It's likely that the solution for both would be to make sure the server is networking properly.

Network and internet is running smoothly. Checked my firewall and port forwarding settings in my router. No changes have occured, how do I get rid of these Rust+ companion app support red errors?

Posted 5 years ago
Last updated 5 years ago
#4
I'm not really familiar with the Rust+ companion app, just going based on what the errors say.

For the compiler check, that means your server can't or couldn't connect to your site to check for an update; so either a network issue there (from the server, not your machine itself) else the connection was blocked somehow.

Being as they are both happening though, it would still imply a network issue for both as they both indicate networking.
Posted 5 years ago
#5
Well I run my own server from home. Network wise all the firewall settings, port settings, port forwarding has not changed. I'm able to get onto the internet fine on all devices within my network. So I am not sure all of the sudden after this June 6th update (whether it's the patch from the game, or oxide) Kind of confused.
Posted 5 years ago
#6
Nothing changed with Oxide this update, zero changes on our end. All I can suggest is to check your network settings and make the server is not blocked in any way, else try restarting it.
Locked automatically