Return of Reckoning

Hello!

I've been playing the game without any issues for months until today, when I crashed during a sc loading screen. I've crashed before with no further problems but this time something must've gonne terribly wrong since I can't connect to the server: the web server icon on the launcher is red and following message shows:

Could not connect to Login server
System.Net.Sockets.SocketException (0x80004005): No connection could be made because the target machine actively refused it 127.0.0.1:8000
at System.Net.Sockets.Socket.Connect(IPAddress[] addresses, Int32 port)
at System.Net.Sockets.Socket.Connect(String host, Int32 port)
at RoRLauncher.Client.Connect()

I've ran the netsh winsock reset catalog / netsh int ipv4 reset reset.log / netsh int ipv6 reset reset.log commands and renewed my ip just in case but so far nothing worked. Looking around the forums I've found a post with a similar issue that mentioned using a VPN, but I have little to no experience setting one up and If that's the only solution I'd like to ask what are the ones you recommend using, even if just for testing.

I appreciate any input you guys might have to help me. Thanks in advance!

As an update, I managed to set up the VPN and it did work. I'm able to connect right now using it.

One question still remains, how the crash had to do with any of it? I've been able to connect with the server without a hitch since last year, why the sudden change in behavior? I doubt that my ISP decided to block it out of the blue. Anyone have a guess?

If there is any restrictions on your internet, that can stop you from accessing the server, i sometimes forget to pay my broadband bill and this happens.

the error indicates localhost. check router & nic dhcp settings
also look in internet properties-connections and what are the Lan -> proxy settings?

Turn out the issue WAS my ISP all along (who would've thought that, right? ). My internet was scheduled to go under maintenance and moments before it went down they blocked the RoR server for some reason. After a couple hours down, it came back up and everything was working fine again.

Just for future reference, the VPN was able to circumvent the issue. So if anyone is having the same problem, that's the way to go.

george needs a new chapter. orwell perhaps we are beyond. as a people we need to stand against