#RCON refuses to work

107 messages · Page 1 of 1 (latest)

fallen path
#

Did you port forward the Rcon ports?

#

Since you said you only forwarded 16261 and 16262

#

Rcon uses the 27015 port

ruby hornet
ruby hornet
#

forwarded, trying

#

nope

#

doesn't work

#

IP and Port, I do enter the RCON port or the server port?

#

tried both 31.130.156.245:27015 and 31.130.156.245:16261, nothin'

fallen path
#

You should not enter any port actually

#

As far as I understand the tool you are using

ruby hornet
#

huh

#

nope

#

doesn't work without ports

#

if I enter a port it hangs a little before closing

#

without a port it closes instantly

#

although

fallen path
#

Hm, and you have Rcon enabled in the game settings?

ruby hornet
#

yes

fallen path
#

And the port is set to 27015?

ruby hornet
#

yes

#

LOG : General , 1691144038799> 297,716,748> RCON: listening on port 27015

fallen path
#

Try opening both TCP and UDP then

ruby hornet
#

do i need to restart the server after each port opening?

#

restarted just to be sure

#

also, on some server restarts, the discord integration bot keeps renaming to servertest

ruby hornet
fallen path
ruby hornet
#

well it can, just have to go to the discord dev panel

fallen path
# ruby hornet no dice

Likely an issue with the tool you are using or you may be writing the port incorrectly, try a different one?

#

Or read the description and see the options it has

ruby hornet
#

not much room for options

fallen path
#

From the link you sent

ruby hornet
#

not sure how to use those

fallen path
#

I suppose through the command line

#

You open it in the directory, use ./rcon options

ruby hornet
#

what rcon tool do you use?

#

cause even battlemetrics can't connect

fallen path
#

Hm, and you are very certain that you port forwarded the rcon port right?

#

You using Windows or Linux?

ruby hornet
#

DMd you the password, try if you want/can

#

I know the risks

#

31.130.156.245

ruby hornet
ruby hornet
#

oh

#

wow

#

alright

#

now it's 27015

#

still doesn't work

#

let me restart real quick

fallen path
#

It should be opened in your firewall as well

ruby hornet
#

setup a rule in the firewall to let in 27015 traffic

#

let's see

#

no dice

fallen path
#

And you tried both variation in the cli tool?

ruby hornet
#

I don't know any other rcon tools

fallen path
#

I meant the ports

#

16261 and 27015

ruby hornet
#

gimme a minute

fallen path
#

Just gave a test with my own server, the port has to be the Rcon port

#

27015

#

The tool you linked works fine

ruby hornet
#

can you send me a screenshot of the console window?

#

how it's supposed to work

#

(don't forget to hide the psw)

fallen path
#

That is all, it will connect then

ruby hornet
#

connect how?

fallen path
#

You press Enter

ruby hornet
#

yeah but how does that look like

#

cause when I press enter

#

it just closes

fallen path
#

Are you launching the .exe or using the command line?

ruby hornet
#

the exe

fallen path
#

Go through the command line instead as mentioned above

ruby hornet
#

how do i do that

fallen path
#

Open a terminal in the location of the rcon exe

#

Write .\rcon.exe

#

Press enter

ruby hornet
#

cli: auth: rcon: dial tcp 31.130.156.245:27015: connectex: No connection could be made because the target machine actively refused it.

#

now we're getting somewhere

fallen path
#

Yep, seems like something is still blocking / refusing it

#

I can only either blame the ports not being opened, or perhaps any other security measure blocking rcon connections

ruby hornet
#

maybe outbound traffic?

#

added a rule

#

didn't help

fallen path
#

Hm, try changing the password? Just as a test

#

The server itself seems to be fine as far as I can tell, it uses the right port and everything

ruby hornet
#

yeah I've tested the server with multiple people

#

the server itself works perfectly

#

except all the balancing and debugging and mod options I have to do

ruby hornet
#

target machine actively refusing it

#

what does that mean

#

stack overflow states:

If this happens always, it literally means that the machine exists but that it has no services listening on the specified port, or there is a firewall stopping you.

fallen path
#

Yep, the server is listening to the port though as the server message says

#

So the firewall or some sort of router security is blocking it

#

Or it still is not opened right, you sure the port is written correctly this time? In the firewall as well?

ruby hornet
#

i don't know anymore

#

quite honestly