Actively refused error

natenaterollerskate

Member
JFF Supporter
Getting an error in the RAT console:

2019-03-01 07:08:29 ----------------------------------
Current Time: 3/1/2019 7:08:29 AM
Thrown by: Void .ctor(System.String, Int32)
Method: VB$StateMachine_28_connect.LogException
Message: No connection could be made because the target machine actively refused it 127.0.0.1:8082
Stack Trace:
at System.Net.Sockets.TcpClient..ctor(String hostname, Int32 port)
at RAT.telnet.VB$StateMachine_28_connect.MoveNext()
----------------------------------

This apparently is causing my server not to show up on even Local network. I've made sure that my Remote settings reflect my local settings, all ports are setup for 8082. I've tried changing all to 8081, didn't seem to work.

Everything shows green, Bad Company, Alloc's Files, Telnet, Local Server. Everything is green. Steam console says everything loaded fine as well.
 

natenaterollerskate

Member
JFF Supporter
  • Tried reinstalling RAT
  • Tried both 8081 and 8082
  • Tried creating a new Firewall rule for Port 8081
  • Tried restarting server
  • Tried turning off Firewall
  • Tried pointing 26900 Port directly to Windows machine IP using Router login
 

natenaterollerskate

Member
JFF Supporter
Ok, FINALLY figured it out for anyone who cares.

All ports need to be 8082 (If you are using Alloc's mods). Which RAT requires, so, needs to be port 8082 (at least this is what fixed all this for me.

SO, the Remote POrt needs to be 8082 as well as the Connections tab for the Telnet and Control panel settings. At least if you're hosting RAT on the same system that your Dedicated server is on, which mine was.
 

Trekkan

JFF Administrator
Staff member
I can honestly say, I have no idea how that would work. ;) But glad it does for you. ;)

The Telnet port needs to be its own port, control panel port, doesn't actually matter at all (and in fact, you should disable it unless you plan on using the built in control panel). The webmap port is 8082, that's the only thing allocs.

So by default, Telnet port should be 8081 and enabled, and on the remote tab, it should match the telnet settings.
 

RB614

New Member
Hey guys, I recently upgraded server machines and went to setup my server and RAT again.
I saved my backups from the previous version of RAT.
After I installed everything but the Mods, everything seemed to be fine.
Then I went out looking for the Allucs and BCManager mods.
After adding both mods to the server directory, I could no longer get RAT to connect via telnet.
I was getting the same error, target refusing connection 127.0.0.1:xxxx
After a lot of blood, sweat, and tears I managed to find the problem.
It seems there is a conflict with the BCManager mod.
After removing the BCManager from the mods directory and restarting the server and RAT, I was able to get a green light for Telnet again.

So if anyone else has done a recent install and added both mods recommended, try removing BCManager.

JFF, is BCManager not compatible with the most recent 7d2d Dedicated Server (Win10 via Steam) or the RAT?
 

Trekkan

JFF Administrator
Staff member
Hey guys, I recently upgraded server machines and went to setup my server and RAT again.
I saved my backups from the previous version of RAT.
After I installed everything but the Mods, everything seemed to be fine.
Then I went out looking for the Allucs and BCManager mods.
After adding both mods to the server directory, I could no longer get RAT to connect via telnet.
I was getting the same error, target refusing connection 127.0.0.1:xxxx
After a lot of blood, sweat, and tears I managed to find the problem.
It seems there is a conflict with the BCManager mod.
After removing the BCManager from the mods directory and restarting the server and RAT, I was able to get a green light for Telnet again.

So if anyone else has done a recent install and added both mods recommended, try removing BCManager.

JFF, is BCManager not compatible with the most recent 7d2d Dedicated Server (Win10 via Steam) or the RAT?
As far as I know, the latest BCM should be fine, but I haven't tested the most recent version myself. BCM however is required for RAT to function correctly. So, if the most recent version is giving you problems, try downgrading to the prior version and see if that works for you. Please let me know on anything you might find out!
 

RB614

New Member
As far as I know, the latest BCM should be fine, but I haven't tested the most recent version myself. BCM however is required for RAT to function correctly. So, if the most recent version is giving you problems, try downgrading to the prior version and see if that works for you. Please let me know on anything you might find out!
I am going to give that a try right now.
Thanks Trekkan.
 
Top