Disconnected: EAC: unconnected, been almost a month of not being able to log into servers.

[T-i-m-]

I can't for the life of me figure out what the problem is. I tried:

- launching from Steam (I always do)
- reïnstalling the game, multiple times, on different hard drives
- uninstalling/reïnstalling EAC through the EasyAntiCheat_Setup.exe
- deleting all EAC files and verifying integrity of game cache
- try stable, dev, dev debug, none of them work
- some servers I can log into, my guess is because EAC is disabled.
- ipconfig flushdns
- restarting Steam
- launch as administrator
- EAC forums (stopped replying after couple back-and-forth's)

I just want to play this game again, but something isn't letting me.
(some extra info: windows 8.1, usually play on London Dev, connecting to server fails upon spawn, I see the Rust island, and then the message pops up. Nothing happens in console.)

[cokeflu]

alooot of ppl are having problems like this atm.. the last update broke the game for me too, everytime i interact with another player or an item in my inventory the game crashes now

[T-i-m-]

[QUOTE=cokeflu;47237881]alooot of ppl are having problems like this atm.. the last update broke the game for me too, everytime i interact with another player or an item in my inventory the game crashes now[/QUOTE]

What are problems similar to this? This has been around for about 4 weeks. It isn't a crash, it's the server booting the player right after log-in.

[espen795]

Have you tried joining a server without EAC enabled?
I also had people not able to join my server so i disabled it.

[T-i-m-]

[QUOTE=espen795;47242208]Have you tried joining a server without EAC enabled?
I also had people not able to join my server so i disabled it.[/QUOTE]

See point 6 :)
"- some servers I can log into, my guess is because EAC is disabled."

[eac knubbe]

Hi,

EAC uses port 443 TCP to connect to the server. This port is open by default in ~all networks, as its used for HTTPS connections, but some ISPs might do network shaping and kill connections to the port.

Which ISP are you using? Could you add me in Steam for debugging further the issue? (steamcommunity.com/profiles/76561197999579793) We would very much like to find out what in the traffic is triggering the ISP/firewall to kill the connection.

[T-i-m-]

[QUOTE=eac knubbe;47243511]Hi,

EAC uses port 443 TCP to connect to the server. This port is open by default in ~all networks, as its used for HTTPS connections, but some ISPs might do network shaping and kill connections to the port.

Which ISP are you using? Could you add me in Steam for debugging further the issue? (steamcommunity.com/profiles/76561197999579793) We would very much like to find out what in the traffic is triggering the ISP/firewall to kill the connection.[/QUOTE]

Added you. My ISP is CAIW Internet, I'm in the Netherlands.

[T-i-m-]

Contacted CAIW, they say the port isn't blocked.
Manually opened the port on my router.
Turned off the firewall on the router.

Problem persists.

I added you on Steam (steam name = slartibartfast)

[KONKER2015]

[url]http://easyanticheat.userboard.net/t31791-really-need-help#108347[/url]

[T-i-m-]

[QUOTE=KONKER2015;47256521][url]http://easyanticheat.userboard.net/t31791-really-need-help#108347[/url][/QUOTE]

You have a similar problem? I'll keep checking your post as well for updates.

[I]Small tip, try using a bit more punctuation. The initial post is almost illegible due to lack of periods and commas. [/I]

[KONKER2015]

Yep no response.

[eac knubbe]

Hi,

Sorry about the late response here.

After debugging on several clients, it seems that using the Websockets protocol triggers client-side to kill the connection. This could be caused by local network or firewall software, but as SSL seems to be working in all cases, we will be implementing SSL support asap now.

All tested clients encountering this issue had Ad-Aware installed, and uninstalling it solved the issue. If you are using Ad-Aware, try temporarily disabling it as a temporary work-around while we are working on this. Hopefully we will have very shortly good news for you.

[Yona]

I use server.secure false on my server, is better!
(I find hacks with server.secure true then for what I wan't this?)

server.secure false = all people can play
(the people with eac banned can share the game with a new steam account...)

[T-i-m-]

[QUOTE=eac knubbe;47282869]Hi,

Sorry about the late response here.

After debugging on several clients, it seems that using the Websockets protocol triggers client-side to kill the connection. This could be caused by local network or firewall software, but as SSL seems to be working in all cases, we will be implementing SSL support asap now.

All tested clients encountering this issue had Ad-Aware installed, and uninstalling it solved the issue. If you are using Ad-Aware, try temporarily disabling it as a temporary work-around while we are working on this. Hopefully we will have very shortly good news for you.[/QUOTE]

Can confirm, disableing Ad-Aware allows me to join servers again.

[KONKER2015]

knubbe ad love if you tested my client :)

[eac knubbe]

@KONKER2015, could you add me in Steam for debugging it? Thanks! [url]http://steamcommunity.com/profiles/76561197999579793[/url]

[Mlotek]

[QUOTE=T-i-m-;47283699]Can confirm, disableing Ad-Aware allows me to join servers again.[/QUOTE]

Did this and it disconnects when loading the topology map for some reason.

Still getting "Disconnected: EAC: unconnected".

[klondike]

I have also started having this problem today. Followed all advice. I dont use Ad-aware. nothingx changed. Was working fine this morning..

I think EAC must have changed something today for it to affect me.

[cinderstar]

Sometimes windowed mode helps.

[Pyrosion]

[QUOTE=T-i-m-;47283699]Can confirm, disableing Ad-Aware allows me to join servers again.[/QUOTE]

Doesn't work for me

[lordrushx1]

Would verifying Rust files in steam do it? It worked for me