[Server] Net permission check spam for loopback (localhost/::1) #245
Closed
0xMxh
started this conversation in
[BUG] FiveM for GTAV Enhanced
Replies: 3 comments 1 reply
|
I have the same problem. |
0 replies
|
Thanks, we are looking into this. |
0 replies
|
A fix for this bug has been implemented and is available in Hotfix 7 (b104). Please try again and let us know if the issue persists. Thanks for your help! |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Summary
A Node.js server resource that opens outbound connections to loopback (
127.0.0.1/localhost/::1) repeatedly logs sandbox network permission checks even though the connection is allowed. There is no documented server.cfg permission (unlikeadd_filesystem_permission/add_unsafe_worker_permission/add_unsafe_child_process_permission) to whitelist loopback or silence these messages.Issue type
Server
Repro rate
Always
Server build version
FXServer-early-access b96 win32
OS
No response
CPU
No response
GPU
No response
RAM
No response
Storage type
None
Connection type
None
ISP and bandwidth
No response
DxDiag
No response
Network graph
No response
Platform
Windows
OS version / distribution
Windows 11
CPU
No response
RAM
No response
Using txAdmin?
None
Hosting provider
Self-hosted
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
127.0.0.1:3999) and, on start, doeshttp.getto127.0.0.1/localhost/::1.Expected Behavior
Outbound Node connections to loopback (
127.0.0.1/localhost/::1) should either:add_filesystem_permission/add_unsafe_worker_permission/add_unsafe_child_process_permission), orActual Behavior
The connection succeeds, but the console repeatedly prints messages like:
There is no documented way to whitelist loopback egress or suppress these messages. The public Sandbox docs only cover filesystem, ConVar, unsafe worker, and unsafe child process permissions, nothing for Node network egress.
Evidence
Server console excerpt:
Crash ID / Perfetto / PCAP: N/A (not a crash, script perf, or packet-loss issue)
Additional Context
fxmanifest.lua:server.js:All reactions