Using Oxide's built in RCON over the built Rust WebRCON

I'm hoping this catches Wulf's eye , I'm trying to make use of the built in Rcon Module with the oxide framework, after doing various searches and digging through the forums, It was determined to be a webrcon based protocol.

I seem to have an issue getting any web rcon client to properly communicate with the Oxide WebRCON Server, it makes a full connection and then dumps the status info to console, however the WebRCON client itself will communicate commands but it seemingly has an issue reading the console of the said rust server.

Any ideas or suggestions? I'm stumped.

 

Yes it's both ran on webrcon, but what i'm running into is oxide rcon doesn't behave exactly as the rust rcon does.

When using tools like Websocket Rcon or RustAdmin they both experience the same thing, the server outputs all that json data, but the rcon client refuses to read the values from the console.

This only occurs when using the oxide version of rcon (I use oxide for more than rust, love your work!)

 

Ah I see, thank you for the information.

Well, the use of Oxide's rcon also stems from another issue. My server ignores the port argument for rcon entirely (provided by commandline in addition to defined in the configuration file, rcon will even say it is binding on this port then bind the default port / interface regardless) with the provided rcon by facepunch. This is what lead me along the lines to using oxide rcon, as from what I was reading it operates the same and allows port changes pretty straightforward by configuration file.

 

+server.port 28016 & +rcon.port 28018 by command line (startup script)

 

I have the same values being set within the config file aswell, would that cause an issue?

Nope no warning or errors until you attempt to bind something else to the same port that webrcon would use default, such as Rust:IO's HTTP server.

 

Oh no oxide rcon is working fine other than that command issue with the console as I mentioned.

The problem is facepunch's rcon seems to ignore +rcon.port argument, when provided in any form, (by startup script, configuration, you name it) it simply does not respect the provided port and binds the default anyways.

I was exploring oxide rcon as a possible work around, but as you said it has that issue with core commands (The answer to my original question)

 

@Wulf Does the oxide rcon use websockets for all oxide games or only rust?

 

Hi,
Solved this with my own implementation of the rcon client to account for Oxide's behavior when compared to facepunch's official, thanks for the help!