Xonotic Forums
Rcon via HLSW Problem - Printable Version

+- Xonotic Forums (https://forums.xonotic.org)
+-- Forum: Support (https://forums.xonotic.org/forumdisplay.php?fid=3)
+--- Forum: Xonotic - Server Administration (https://forums.xonotic.org/forumdisplay.php?fid=16)
+--- Thread: Rcon via HLSW Problem (/showthread.php?tid=871)



Rcon via HLSW Problem - Highlander - 08-25-2010

Hi ,
I´m trying 2 connect 2 my Nexuiz server via HLSW + Rcon and it doesnt work.
HLSW is sending the password but doesn´t get anything back from the server.

I set up the rcon_password in the server config is there anything else i need 2 do 2 get this working ?

InGame Rcon via console is working.


( i also have a few other Server´s like CSS , Urban Terror they all work via HLSW )


RE: Rcon via HLSW Problem - Mr. Bougo - 08-25-2010

Nexuiz and Xonotic use a secure version of the rcon protocol. You can disable this (and thus get regular rcon) by setting the rcon_secure cvar to 0 in your server configuration.


RE: Rcon via HLSW Problem - Highlander - 08-25-2010

(08-25-2010, 08:11 AM)Mr. Bougo Wrote: Nexuiz and Xonotic use a secure version of the rcon protocol. You can disable this (and thus get regular rcon) by setting the rcon_secure cvar to 0 in your server configuration.

Well thank´s for the quick replay but that doesn´t work :
the Putty console tell´s me now " server denied rcon access to "myIPadress" "
i checked the config even renamed the Bots 2 check if the config is taking any effekt on the server, that did work.

the server.log say´s this :
====== Log started (Wed Aug 25 14:24:51 2010) ======
^7Game type successfully switched to dm
^7Server using port 26000
^7Server listening on address 88.198.183.160:26000
^7LHNET_OpenSocket_Connectionless: socket returned error: Address family not supported by protocol
^7Server failed to open socket on address [0:0:0:0:0:0:0:0]:26000
^7LHNET_OpenSocket_Connectionless: socket returned error: Address family not supported by protocol
^7Server failed to open socket on address [0:0:0:0:0:0:0:0]:26001

^^does that have anything 2 do with the Problem ???

at least the server does get an request on rcon when i set rcon_secure 0 but still doesn´t let me in ... :-(


RE: Rcon via HLSW Problem - Mr. Bougo - 08-25-2010

Do you have a firewall blocking port 26000 on the srrver host?


RE: Rcon via HLSW Problem - Highlander - 08-25-2010

(08-25-2010, 12:26 PM)Mr. Bougo Wrote: Do you have a firewall blocking port 26000 on the srrver host?

i don´t think so .. I can connect 2 the server just fine . . wouldn´t that also be a problem when the firewall would block that port ?

(i meant Playing on the server works just fine)


RE: Rcon via HLSW Problem - divVerent - 08-25-2010

The error messages are just about IPv6 connectivity, which is fine. IPv4 was initialized successfully, as per

^7Server listening on address 88.198.183.160:26000


RE: Rcon via HLSW Problem - Mr. Bougo - 08-25-2010

Ah...
Highlander, make sure that rcon_secure is set to 0 on your server then, and also make sure that rcon_password matches the input password. I don't really see why it wouldn't work, rcon_secure 0 makes the server use the standard rcon protocol. Sad


RE: Rcon via HLSW Problem - kidx - 10-15-2012

I get this on my server when ever I try to acess rcon in hlsw, Any ideas sorry for posting on an old post just makes more sense to post here correct.

denied rcon access to 76.10.135.89:7130
server denied rcon access to 76.10.135.89:7130
server denied rcon access to 76.10.135.89:7130
server denied rcon access to 76.10.135.89:7130


RE: Rcon via HLSW Problem - Mr. Bougo - 10-16-2012

Read the thread, address the questions I asked to Highlander.


RE: Rcon via HLSW Problem - kidx - 10-16-2012

(10-16-2012, 12:41 AM)Mr. Bougo Wrote: Read the thread, address the questions I asked to Highlander.

Its been addressed I unblocked that port so go figure.


RE: Rcon via HLSW Problem - PinkRobot - 10-19-2012

This post was intentionally left blank.


RE: Rcon via HLSW Problem - kidx - 10-20-2012

(10-19-2012, 03:39 AM)PinkRobot Wrote: This post was intentionally left blank.

Figures lmao.