This post is mainly for validation from one of the Oxide devs. I've been having rcon issues with my host using Rusty or any other rcon tool and they insist it's Oxide's end. I've told them I've tested it on other Oxide servers NOT hosted through them and it works fine. Here is the response I've gotten.
I honestly think this is a load of crap, could anyone verify this?
In advanced, thanks.
Fixed RCON "not connected", not working
Discussion in 'Rust Discussion' started by Evano, Sep 6, 2015.
-
Wulf Community Admin
Oxide doesn't control or touch RCON, so not sure what else to say. I have no issues with RCON with Oxide installed either.
-
Thanks again, Wulf. -
Wulf Community Admin
I posted an image connecting here: Rusty - Server RCON administration tool | Page 43 | Oxide.
Also out of curiosity, are you running Rust:IO? Some say they had issues when using it, but I run it 24/7 as well. -
Yeah, I run it with no issues. I clone my server locally same Oxide build / Rust protocol and I have no issues. It's only when those files are located @FPSPlayers that I experience this, which leads to them. And despite this post I've linked them they are still saying I'm wrong.
-
Wulf Community Admin
-
Yay! Last time I checked, I was able to connect to mine though. Let me re-confirm this.
[DOUBLEPOST=1441497017][/DOUBLEPOST]I just did some testing, so It has to be TCAdmin?
-
Wulf Community Admin
Not that I can tell, it may be a hook issue with Oxide, just not sure why. I've managed to get it to work somewhat, but I'm investigating to see what may be causing it. I've been getting mixed results though, so it's proving difficult to figure out.
[DOUBLEPOST=1441500240][/DOUBLEPOST]So a little update... With and without Oxide on my remote server, RCON only successfully connects fully once, then it "connects", but shows "not connected" after that. I'm not sure what's going on, but I'm not aware of any changes related to this with Rust, and Oxide doesn't appear to be affecting it. The results can be so mixed though, that it can be hard to pin down the culprit. -
Another Update,
The tool itself is not reporting back any information from the server such as players, chat, etc.... However, with Oxide installed and even though the green box on the tool says not connected I am still able to send a test chat message to servers. I am able to check the status, kick, ban, and perform many other tasks but again... no information is being reported back to the tool itself. However, in our TCAdmin environment you can see the actions being performed by clicking on our Web Console.
I am not sure if this helps you at all Wulf. I will attempt to contact the developer of Rusty as well to get their input on the matter. Thank you for continuing to look into the issue.
-Chris -
Wulf Community Admin
The general "not connected" issue though after the first connection disappears when you hit "Refresh" on the Rusty client, though I'm not sure why it happens it the first place, but it isn't related to Oxide. -
Okay, tested and working in our environment. Any chance I can get you to commit that to your GitHub as, for us, Oxide is pulled straight from there?
-Chris -
Thank you all for looking into this, I truly appreciate your time.
-
Wulf Community Admin
-
Works for me too. Thanks Wulf
(Rusty, RustAdmin Tool and Rust:IO Console work now) -
Wulf Community Admin
The latest Oxide snapshots have this fixed now by the way. If you see any "Not connected" messages after the initial connect/disconnect, just hit "Refresh" on your RCON client; that's not an issue on our end though. I'll be putting out a release soon.
-
Well, i still have the problem and cant connect no idea what to do !!
-
I havent been able to get rusty to work at all for a week. No other Rcon tools have an issue. I have heard that changing the Rcon port to 0 is a fix but i have not tried to confirm as it requires me to change all my Rcon tools.
Connected green light - no connection
Admin log 03/12/2017 17:32:35 > Connected
Consoole
Connecting to server
Success
No return of commands or console/server player info
Disconnects 30 secs
Clicking View console logs crashes the client