Could not bind on 0.0.0.0:30120

FiveM Server Development Server Discussion
,
1

When i’m launching server, the server start normally but could not bind on 30120 port.
I checked if port 30120 is already linked to another program or server, but it’s not.
I do not know what to do to fix this and I can not join my server because of this.
I would be very grateful if you could help me !

2

There’s not much else to tell you. There’s something running on that port.

3

How can i fix it?

4

Chage port or stop whats on it…

5

1. Windows (PowerShell or CMD)

A. Check what’s running on port 30120

netstat -ano | findstr :30120

B. Check 40120

netstat -ano | findstr :40120

This gives you a line like:

TCP    0.0.0.0:30120    0.0.0.0:0    LISTENING    1234

The last number = PID (process ID).

C. Kill it

taskkill /PID 1234 /F

2. Even if no app is on the port, Windows can still reserve it because of firewall rules.

Fix:

  • Open Windows Defender Firewall → Allow an app
  • Remove FXServer.exe
  • Add it again manually
  • Restart the server

OR from terminal:

netsh advfirewall firewall delete rule name="FiveM FXServer"

Then re-create the rule.

3. Windows sometimes marks a port as “reserved” after a crash or update.

Run PowerShell as admin:

netsh int ipv4 show excludedportrange protocol=tcp

If you see 30120 inside a blocked range, that’s the problem.

Fix:

  • Reboot (this clears ephemeral ranges)
    OR
  • Change your server port temporarily to test:

In server.cfg:

endpoint_add_tcp "0.0.0.0:30125"
endpoint_add_udp "0.0.0.0:30125"

If it works, the old port was reserved.

4. Another FXServer instance is running — just not where you looked

Lots of users forget to check Services, not just Processes.

Open Task Manager → Details tab
Look for:

FXServer.exe
cmd.exe
conhost.exe (that belongs to FXServer)

End all of them.

Boom. Whatever was locking your FiveM ports is now gone.