CD46 / AC #95 HB-timeout on a custom MTA client; disabling AC #95 causes permanent Network Trouble

[VladislavK203]

I am using a local MTA server and a custom client compiled from the open-source mtasa-blue repository.

The client connects successfully and works normally for several minutes. After that, the server disconnects the client with:

Disconnected [CD46]
AC #95 HB-timeout

The server itself continues running and does not crash.

With the default Anti-Cheat configuration, Network Trouble does not appear. It occurred only during a separate test when Anti-Cheat #95 was manually disabled in mtaserver.conf:

95

After restoring the default configuration:

Network Trouble no longer appeared, but the CD46 / AC #95 HB-timeout disconnect continued to occur.

Expected result: the custom client should maintain a stable connection to the local server.

Actual result: after several minutes, the server disconnects the client because of AC #95 HB-timeout.

Please help me solve this problem.

Steps to reproduce

Start the local MTA server.
Launch the custom client compiled from mtasa-blue.
Connect to 127.0.0.1:22003.
Remain connected for several minutes.
The server disconnects the client with CD46 / AC #95 HB-timeout

Version

Client: MTA:SA v1.7-custom Windows 64-bit Server: Multi Theft Auto v1.7-custom Operating system: Windows 10 64-bit Server AC information: Allowed client files: None Disabled AC: None Enabled SD: None

Additional context

Troubleshooting already performed:

• Changed the main server port, including the default port 22003 and other values.
• Changed the HTTP port, including the default port 22005.
• Tested connections through 127.0.0.1, localhost, and the computer's local IPv4 address.
• Completely disabled Windows Defender and antivirus protection.
• Enabled antivirus protection again and added the MTA:SA and GTA San Andreas folders to the exclusion list.
• Tested with VPN enabled and disabled.
• Restarted the client, GTA San Andreas, the server, and the computer.
• Tested the server with some custom resources disabled.
• The server continues running when the client is disconnected.
• With AC Experimental/win static link #95 enabled, the client receives CD46 / AC #95 HB-timeout.
• With AC Experimental/win static link #95 disabled, the client becomes permanently stuck on Network Trouble.

The issue may be related to the custom-compiled client, network components, or compatibility with the current Anti-Cheat system?

Relevant log output

CLIENT CONSOLE: [2026-06-16 17:09:34] Reconnecting to 127.0.0.1:22003... [2026-06-16 17:09:35] Connected! [MTA:SA Server 1.7, Windows] [2026-06-16 17:09:39] Server AC info: [Allowed client files: None] [Disabled AC: None] [Enabled SD: None] SERVER CONSOLE: [2026-06-16 17:14:38] KICK: The client was kicked from the game by AC #95 HB-timeout. CLIENT STARTUP LOG: [2026-06-16 17:09:25] Windows Defender enabled and healthy. [2026-06-16 17:09:27] Loading network. [2026-06-16 17:09:27] Network loaded. [2026-06-16 17:09:29] Network initialized. [2026-06-16 17:09:34] Connecting to 127.0.0.1:22003.

Security Policy

• I have read and understood the Security Policy and this issue is not security related.

[AlfredoAnonym]

I have the exact same problem, just disable the anti-cheat 95 if you are on the local server that's the solution right now. It's somewhere in MTA server conf file. They don't care anyways, and you should use Nightly imo because it didn't do such things in 1.7 nightly for some odd reason (maybe AI code?) MTA is dying and less and less players play it, due to GTA VI coming up later this year, and these problems. I got info couple of weeks ago that MTA developers do not care about this problem and said to "fix it by yourself" but I don't know it's 100% accurate, they blame the hardware of ours which is just not true, but idk about that, someone on Discord asked that and they just... don't care.

By the way I disabled the anti-cheat 95 only, and yeah I had that network trouble for about 30-40 seconds, and then it went back to normal... And sometimes... IT DOESN'T EVEN HAPPEN AT ALL without anti-cheat. Or problem just decides to not appear sometimes when anti-cheat is ON. It's a very strange problem, you can fix it if you just restart the server (if you run it through MTA Server.exe) or restart the game I don't exactly remember.

[VladislavK203]

Thank you for the reply.

My situation is a little different.

If I disable AC #95 in mtaserver.conf, the AC #95 kick disappears, but after about 2-3 minutes I get "Network Trouble". Synchronization completely stops and the problem never goes away, even if I wait for a long time. Reconnecting does not help and I have to restart the client or the server.

If I enable AC #95 again, the Network Trouble issue disappears, but after a few minutes I get kicked with:

AC #95 HB-timeout

So I am stuck in a loop:

AC #95 enabled → kicked with AC #95 HB-timeout.
AC #95 disabled → permanent Network Trouble.
I already tried changing ports, IP addresses, disabling and enabling antivirus software, and testing through 127.0.0.1, localhost, and the local IPv4 address. The result is always the same.

Did you also have a case where disabling AC #95 caused Network Trouble that never recovered at all

[AlfredoAnonym]

I never had a case that Network Trouble was stuck or never recovered. It just randomly went away, maybe try to reconnect? It's especially painful in the map editor, I'm doing something and then that happens and I need to wait...

[VladislavK203]

@AlfredoAnonym

Thank you for the reply.

In my case it behaves differently.

When I disable AC #95, I get "Network Trouble" after about 2-3 minutes. The issue never disappears, even if I wait for a long time. Synchronization completely stops.

If I try to reconnect, I cannot join normally anymore because I immediately get kicked with "AC #95 HB-timeout".

The only way to play again is:

1. Close the client.
2. Stop the local server.
3. Start the server again.
4. Launch the client and reconnect.

After that everything works again for a few minutes, then the same problem repeats.

By the way, are you using the official MTA client or a custom client compiled from source code (mtasa-blue)?

[AlfredoAnonym]

Official one. Maybe as I said try Nightly 1.7? I didn't had those issues. Btw heres what I had, had way more different issues: #4922

[VibingCreator]

Restarting computer fixes the HB-timeout for me.

[Lpsd]

You don't need to restart the entire machine, just the server. Anyway, we're going to loosen/disable this check in 1.7 so this issue will be irrelevant soon.