Server Not Sending Heartbeat or Listing in Server List

[Dominic1337]

System Info - VPS - vpsdime - Windows Server 2019

Server Console (no heartbeat and this has been up for hours)

server.cfg - sv_master is commented out

Whats listening when fxserver is running

Made rules allowing inbound and outbound for
TCP-UDP for port 30110-30120, 80 ,443

Made rule allowing FXserver.exe

Additional Info

• I checked port 30120 while server was running and it shows as open
• I checked port 30110 while server was running and it shows as closed
• I checked port 80 while server was running and it shows as closed
• I checked port 443 while server was running and it shows as closed
• Fresh install of FiveM server, default and updated artifact, only base resources running
• keymaster page is showing a heartbeat being sent AND shows my server name
• I am able to direct connect via F8 however server does not list on server list

24 hours and my server is still not sending any heartbeats or being listed on servers list? Does anyone have any idea why and can you please help, thank you

[keem_developments]

I found a similar topic which has a solution, it might offer some insight for you.

I cant send HEARTBEAT

I tried sending the heartbeat which is what I usually do on a restart of the server, I havent done it on this server before cause I’ve been in development mode of the server and we are getting close to launch. so I sent the heartbeat command and usually it say something underneath but it doesnt (see screenshot above), checked ports they work so I sent the heartbeat and still nothing its not showing up, so I think it might have something to do with the command or the way the server is set up… A…

[Dominic1337]

Seems to me that the solution of that thread is that the VPS provider is unusable with FiveM. Can anyone confirm that vpsdime has issues with FiveM, I seen it recommended here before.

[Dominic1337]

I tried configuring the same server on zap hosting vps and I am also having issues on there. I believe it may be something I am doing wrong, not the host.

[TheIndra]

Instead of editing your whole topic to “was something on my end” instead share the solution and mark it as solved so it can help others in the future.

[Dominic1337]

The issue is something I was placing in the server.cfg for the vanilla FXServer install. I havent narrowed it down but if you use the txAdmin server.cfg as a template instead and change that around it seemed to work for me. Not the cleanest answer but it may help someone one day.

Everything I did above in my OP was correct except the server.cfg