1. Can anyone assist? Had issues updating my Rust server today (hosting it off windows 10, and yes, I know, it would be better off linux and that is in the works) luckily it was a newer server that did not have much going for it. After a few hours of trying to get the server to update to no avail, it would tell me I was already fully updated but then kick me upon trying to connect saying that client protocol was 2062 and server protocol was 2057, I decided to completely delete the server and set up a completely new one. After setting up this new server, I was able to connect and walk around in game. Once I went to install Oxide however, the 2062/2057 error immediately came back. I'm wondering if there is something going on here in the background, some kind of n00b mistake that I'm making, but it appears to me that trying to install the most recent oxide is causing connectivity issues to my server?
     
  2. Wulf

    Wulf Community Admin

    What error exactly? Rust telling you that your client is outdated is not a crash, that means your server is outdated. If you are seeing that only after installing Oxide, then you are installing an older Oxide build. Oxide itself has no protocol handling, that's all Rust; so you'd only get that by using older Rust DLLs.
     
  3. ...Strange, I went to go back and recreate the issue and screenshot everything however it is not persisting...I did drag n drop the oxide rust dedicated data folder I downloaded today into the (server)folder a second time just to be sure it was the latest, (same version as a few hours ago) but now I'm able to connect. Must have been some rando n00b issue I was blind to. Sorry to waste your time Wulf, I appreciate the response greatly and can't express enough how much I love running oxide on the servers.
     
  4. Wulf

    Wulf Community Admin

    No problem, glad you got it worked out.