Cfx.re deprecates Nucleus reverse proxy for *.users.cfx.re by March 31, 2026

Cfx.re posted to its official community forum that "On March 31, 2026, the current \.users.cfx.re reverse proxy will be fully deprecated, meaning you will no longer be able to access your server http endpoints via this reverse proxy service." The message, published by the team behind FiveM and RedM, warned that the reverse-proxy endpoints many servers depend on will stop routing traffic after that date.

The forum announcement singled out server-side HTTP handling as a primary concern, stating "One critical aspect that needs more attention regarding this deprecation is the impact on `SetHttpHandler`." The post added that "Many modern resources rely on SetHttpHandler to expose HTTP endpoints directly from the server runtime. These are frequently accessed via the `.users.cfx.re` proxy using `GetConvar("web_baseUrl", "")`." Cfx.re then cautioned that "Removing this doesn’t just affect join links; it breaks essential functionality that many servers might not even realize is dependent on this proxy until it’s gone:" and explicitly listed "Media Systems: In-game image/video uploads and previews." The announcement snippet shows an ellipsis after that item, indicating the post contained additional examples not present in the provided excerpt.

As mitigation, Cfx.re pointed operators toward external tooling, writing "There are also plenty of free third-party resources available to build your own reverse proxy if desired." The post framed the change as part of platform maintenance: "As our platforms evolve, some features may no longer meet current performance or maintenance needs. When this occurs, we deprecate them to focus on more reliable and scalable alternatives." Cfx.re asked for operator feedback and provided direct channels: "We encourage you to let us know if this planned change might have an effect on your FiveM or RedM server. Please leave a comment below, or send a message on our Discord server." The announcement included two image attachments labeled "Nucleus Reverse Proxy" at 1920×1080, 85.3 KB.

Forum users immediately raised implementation questions and reported mixed reactions. One user asked, "I have a Discord bot that looks at the players.json, is it going to still work if I am using 127.0.0.1 in the bot code? For context, the bot is hosted on the same server as our FiveM project." Another user estimated the scale, writing "The proxy is actually used by a major number of servers (possibly +10k) for various purposes." A developer described their own dependency candidly: "I’m currently using some custom endpoints via the `SetHttpHandler` native, so this would have an effect on me, however, it’s really not a big deal. I’ll simply find/create an alternative. Better to move forward than to be stuck in legacy land." Shorter community reactions included "Thank you Sir Gogsi :saluting_face:", "Green Light for me :+1:t2:", "Good ig :mascot:", "Go ahead.", and "Very random." The thread also contained the post-level admission that "Honestly we’re not sure how many people have been using it/if removing it might mess up anyone’s server, so we want to get feedback before we say a proper goodbye to Nucleus."

With the deprecation date fixed at March 31, 2026, servers using `SetHttpHandler` and GetConvar("web_baseUrl", "") must plan replacements for reverse-proxy routing and media endpoints to avoid interruptions to in-game uploads and previews. Cfx.re pointed operators to third-party reverse-proxy resources and asked them to report impact via the forum or the project Discord as they prepare for the cutoff.