Multiple errors

[Tobbsey]

What is the issue you’re having?

RedM Crash and Port Conflict Issue Report

Issue Summary:

RedM is experiencing frequent launch failures due to port conflicts, showing libuv error EADDRINUSE in logs, and crashes with:

307. Failure connecting to the Rockstar Games Launcher! (ExitCode = 307)

After numerous unsuccessful attempts and trying nearly every documented workaround, it only connects randomly — seemingly when a specific port isn’t blocked or reused. This issue appears to stem from how RedM and Rockstar’s ROSService manage socket bindings during startup.

System Info:

RedM Version: Latest (as of July 15, 2025)

Red Dead Redemption 2: Legit Steam install

Operating System: Windows 10 (Build 19045.6093)

CPU: Intel Core i9

GPU: NVIDIA RTX (GeForce overlay confirmed disabled)

Firewall/AV: No restrictions; ports are not manually blocked

Overlay Software: Disabled/closed (Discord, NVIDIA, etc.)

Launcher: Rockstar Games Launcher (found and running correctly)

What have you tried already to fix the issue?

Steps Already Taken (All Unsuccessful for Permanent Fix):

Verified integrity of RDR2 files via Steam and Rockstar Launcher.

Deleted and rebuilt RedM and Rockstar cache folders.

Disabled all overlays (NVIDIA, Steam, Discord).

Confirmed no background applications interfere with ports (OBS, VPNs, etc.).

Attempted launching RedM from Canary, Beta, and Normal channels.

Clean boot attempts and admin rights ensured.

Tried assigning static ports to ROSService and server sv/cl entries.

Confirmed port conflicts using TCPView and netstat — random ephemeral port range usage by RedM_GTAProcess.exe every launch.

RockStar Launcher handshake confirmed successful in some logs — but still fails on many attempts.

Crash dump reference: si-2620ca17b0e9469bba8948c0bbab0dd4

Observed Behavior:

On most launches, RedM fails with port binding errors:

[    ROSService] UV loop: default/ Listening on socket failed - libuv error EADDRINUSE.

Repeated relaunches show different port ranges (e.g., 49000–53000).

Once in a while (randomly), it successfully connects, confirming the install and entitlement are valid.

ROSService does not respect port overrides set via command-line flags or configuration edits.

What server did you get this issue on?

thefrontierroleplay

Windows version

Windows 10 64-bits (10.0, build 19045)

System specifications

Asus b750-F
BIOS date: 05/15/25
Processor: Intel Core i9-14900 ~2.0GhZ
Motherboard: Asus Rog Strix B-760-F Wifi
RAM: 65536 Mb RAM
DX-12
Windows 10 64 bits.

Antivirus software

Windows Defender

Additional comments

Conclusion:

This appears to be a race condition or improper socket cleanup between RedM, ROSLauncher, and ROSService. Ports appear to remain locked or unreleased, causing crashes until Windows arbitrarily clears them. The lack of consistent port binding or override support prevents users from making it stable.

Request:

Please confirm if this is a known issue and whether:

RedM's ROSService can have a manually fixed port assigned, and if so, how?

There is a workaround to enforce a clean socket bind or port reuse delay?

A patch is planned to resolve persistent EADDRINUSE conflicts?

We’re happy to provide full logs and repeatable test scenarios.

[system]

Hello, this is a friendly reminder because this is your first time creating a topic (or it has been a while since your last topic) in this category.

Please note that most of the support is provided by the Cfx.re community on a voluntary basis. We ask you to be patient; there is no guarantee we have a solution to your problem(s). To avoid unnecessary/duplicate topics, please browse the forums before creating a topic.

To improve your chances of your issue(s) being solved, please provide as much information as possible about the issue(s) you are having. Also —whenever possible— please use the template given to you when creating a topic.

Thanks for keeping these forums tidy!