[Bug] App url (for CFX authentification, joining server from browser) not working

[PichotM]

Summary

Anything that relies on the CFX protocol handler does not work.

For example, clicking “Open in FiveM Enhanced” to confirm the linking of my CFX account, or clicking a server connection URL such as connecting from the browser produces no response in the game.

As a result, I am unable to link my CFX account or join a server from the browser.

Issue type

Client

Repro rate

Always

Server build version

0

OS

Windows 11 Pro 25H2

CPU

AMD Ryzen 9 7950x

GPU

No response

RAM

No response

Storage type

SSD NVMe

Connection type

Ethernet

ISP and bandwidth

No response

DxDiag

No response

Network graph

No response

Platform

None

OS version / distribution

No response

CPU

No response

RAM

No response

Using txAdmin?

None

Hosting provider

None

Machine type

None

/perf endpoint output

No response

DDoS protection

No response

ulimit -n value (Linux only)

No response

Docker Compose file (Docker only)

No response

Steps to Reproduce

1. Try to link my account when joining
2. Opening a cfx.re join url from the browser

Expected Behavior

Handshake from the game for all url stuff

Actual Behavior

Nothing happens, like if the app is not listening/not receiving anything (infinite "waiting")

Evidence

No response

Additional Context

No response

[wolfram-cfx]

Thanks we are looking into this.

[MohamadHezi]

I confirmed it's not the OS protocol handler, HKEY_CLASSES_ROOT\fivem\shell\open\command was missing after a clean install (even with admin reinstall), so I manually added it pointing to FiveM.exe "%1". Didn't fix it. still hangs on "Awaiting sign in confirmation."

The launcher log shows this right after the Discord auth step:

[error] Discord auth validation response:
[error] Received unknown message type: loadWarning
[error] Failed to open CfxDataProvider file: path - assets/undefined

Looks like something fails inside the client's own auth/UI flow after the handoff, not the protocol registration itself.

Windows 11 Pro 25H2.

[n0minal]

A friend of mine is having the same issue, I can confirm this bug.

[MohamadHezi]

same here

[dmvape]

Confirming this issue on Windows 11 Pro 25H2 with the current FiveM for GTAV Enhanced client as of July 28, 2026.

Symptom

After selecting Link account → Sign in with Cfx, the browser authorization completes, but the Enhanced client remains indefinitely on:

Awaiting sign-in confirmation

Diagnostics performed

The fivem:// protocol was initially not registered. Running a FiveM URL displayed:

Get an app to open this 'fivem' link

I manually registered the protocol under:

HKEY_CURRENT_USER\Software\Classes\fivem\shell\open\command

Pointing to:

"C:\Users\xtrem\AppData\Local\FiveM for GTAV Enhanced\FiveM.exe" "%1"

Windows then recognized fivem:// links, but the launcher still did not process them.

I also bypassed the Windows protocol registration and invoked the executable directly:

& 'C:\Users\xtrem\AppData\Local\FiveM for GTAV Enhanced\FiveM.exe' 'fivem://connect/127.0.0.1:30120'

The loading cursor appeared briefly, but no launcher window opened and the command returned immediately. The real browser accept-auth callback behaves the same way.

Relevant launcher log

The newest reproduction produced:

Product validation completed for "cfxlauncher" on branch "main": 3/3 files are valid and up to date.
Discord auth validation response:
Received unknown message type: loadWarning
Failed to open CfxDataProvider file: path - favicon.ico
Failed to open CfxDataProvider file: path - assets/undefined
Failed to open CfxDataProvider file: path - assets/undefined

The assets/undefined error also repeats continuously during longer sessions. I do not see a successful accept-auth receipt or token-exchange entry afterward.

I use a custom GTA V Enhanced location:

D:\Games\GTA5\Grand Theft Auto V Enhanced

The corresponding config.toml is now loading correctly. The initial missing-config error disappeared after creating it, but the account-link problem remained unchanged. Launcher product validation also reports all three launcher files as valid.

This appears to show two related problems:

1. The Enhanced installer did not register the fivem:// protocol.
2. Even after manually registering it—or passing the URL directly to FiveM.exe—the Enhanced launcher does not process the URL and fails inside its UI/message handling.

I have the complete launcher log ZIP available if it would help with debugging.

[dmvape]

Additional browser test

I repeated the authorization using Microsoft Edge. Edge correctly recognized the registered fivem:// protocol and displayed:

This site is trying to open FiveM for GTAV Enhanced.

After clicking Open, nothing happened and the client remained on Awaiting sign-in confirmation.

This confirms that Windows and Edge can resolve the protocol association. The failure occurs after the URL is handed off to the FiveM for GTAV Enhanced executable, rather than being specific to my original browser.

[Biboque]

Same for my friend on Firefox

[Nobelium-cfx]

Hi, while there are probably some issues with url protocol and account linking that we are investigating - note that fivem:// is for gen8, for enhanced we use cfx://

[dmvape]

Update: retested using the correct cfx:// protocol

Thank you for clarifying that fivem:// is for Gen8/Legacy and that GTA V Enhanced uses cfx://.

I retested using the correct Enhanced protocol.

Protocol registration

The cfx:// protocol is already registered correctly in Windows:

HKEY_CLASSES_ROOT\cfx
    (Default)       REG_SZ    FiveM-for-GTAV-Enhanced
    URL Protocol    REG_SZ

HKEY_CLASSES_ROOT\cfx\shell\open\command
    (Default)       REG_SZ    "C:\Users\xtrem\AppData\Local\FiveM for GTAV Enhanced\FiveM.exe" "%1"

This was confirmed using:

reg query "HKCR\cfx" /s

Direct protocol test

With FiveM for GTA V Enhanced completely closed, I ran:

Start-Process 'cfx://connect/127.0.0.1:30120'

PowerShell returned without an error, but no FiveM Enhanced window opened and there was no visible response from the client.

Account-linking result

I also repeated the normal account-linking process:

1. Opened FiveM for GTA V Enhanced.
2. Selected Link account.
3. Selected Sign in with Cfx.
4. Signed into the Cfx Forum account.
5. Opened the authorization page.

The authorization page now displays:

429 error

Before the 429 appeared, clicking Authorize attempted to redirect to accept-auth, but the Enhanced client remained indefinitely on:

Awaiting sign-in confirmation

The 429 may be a temporary rate limit caused by the repeated troubleshooting attempts, so I have stopped retrying until the limit resets. However, the original problem existed before the 429 appeared.

Current conclusion

The correct cfx:// protocol registration exists and points to the correct Enhanced executable. Windows recognizes the protocol, but the Enhanced client does not visibly respond when the URL is handed to it.

This suggests the failure occurs after the protocol URL reaches FiveM.exe, during the Enhanced client’s URL or authentication-callback processing.

My earlier mention of a missing fivem:// registration was based on the Legacy/Gen8 protocol and should be disregarded for GTA V Enhanced.

[RH-Adv1c3]

I tried this today and managed to get a successful link between mij client and Cfx account.
I have tried this on server build 106. Not sure when it released but just updated it and it works on my end.
Hope it works for you as well!

[PichotM]

Works for me now

[Nobelium-cfx]

I see that using cfx:// already solved the issue for some people. In todays patch we also fixed a few problems:

• Auth link not working on some browsers
• Protocol only working once per launcher run (e.g. after using the protocol for auth - protocol will not work for connecting to the server until launcher is restarted)

Now everything should work fine. If it still doesn't and you have tried to register fivem:// protocol manually - there is a chance you messed something up and you need to clean up the registers.

Feel free to reopen if issues remain

[Gogsi]

A fix for this bug has been implemented and is available in the August 4 patch. Please try again and let us know if the issue persists. Thanks for your help!