I hope you can get a response from an element regarding this issue. Sorry I wasn’t able to help more.
Dude, you wrote a badass fucking tutorial on how to get it setup to begin with. Such a well written tutorial, in fact, that someone like me, who had zero experience with FiveM server management felt immediately comfortable diving in and had it setup and running in 5-10 minutes. This is beyond your control, and you still spent time trying to help figure it out. Sit down, be humble, you did good man. A damn fine job!
2 Likes
Hm - is netstat supposed to show UDP binds? It seems the UDP bind doesn’t show up at all in there, which of course wouldn’t be related to TCP issues (perhaps due to proot? unsure, this normally doesn’t cause issues) but is possibly related.
1 Like
Ok, so to make this thread, I basically copied over all the stuff I already wrote in the thread I reference at the beginning. I accidently cut off the UDP portion. It’s been updated. Sorry, and thanks for any help you give!
1 Like
This wasn’t fixed by updating to 290-04e034829f75169f11ee33abf67281ecd74728e3
It’s still the same issue.
Something I’m noticing here is the default route for TCP is ipv4 while the default route for udp is ipv6…
Edit: I disabled ipv6 entirely as I don’t utilize it.
That might be bad. ENet supports IPv4 through an IPv6 compatibility mapping ([::ffff:1.2.3.4], v4mapping), and does not use raw IPv4 at all, so you’ll need to have the IPv6 stack enabled.
I did it as a troubleshooting step. It hasn’t worked either way. I’ll re-enable it, but the issue is still there either way. Server appears fine but doesn’t respond to queries. I’m honestly pretty frustrated at this point. It’s been days and I feel like there’s a solution in reach, but I need help getting it.
I can see the ACCEPT packet count increasing when using iptables -L -v -n | grep 30120 while trying to send packets to the server port using Putty and FiveM direct connect searches, so I KNOW the server is receiving packets.
In a new revelation I saw, if only for a brief moment, the “My New FXServer!” with a connect button, before FiveM jumped back to http://imgur.com/p4QLZN2
Something is up with the server. I’ve completely wiped out the directories and re-done it step-by-step 3 times now. Again, any help is greatly appreciated.
Tried renice-ing the server process to -1 to make sure it takes priority for processing, still nada.
After using Ctrl+C to kill the server, I see a lot of pids from proot, is this normal?
proot info: pid 6746: terminated with signal 2
proot info: pid 6754: terminated with signal 2
proot info: pid 6758: terminated with signal 2
proot info: pid 6760: terminated with signal 2
proot info: pid 6757: terminated with signal 2
proot info: pid 6756: terminated with signal 2
proot info: pid 6755: terminated with signal 2
proot info: pid 6753: terminated with signal 2
proot info: pid 6752: terminated with signal 2
proot info: pid 6751: terminated with signal 2
proot info: pid 6750: terminated with signal 2
proot info: pid 6749: terminated with signal 2
proot info: pid 6748: terminated with signal 2
proot info: pid 6747: terminated with signal 2
proot info: pid 6744: terminated with signal 2
proot info: pid 6745: terminated with signal 2
proot info: pid 6742: terminated with signal 2
proot info: pid 6743: terminated with signal 2
proot info: pid 6739: terminated with signal 2
proot info: pid 6741: terminated with signal 2
proot info: pid 6737: terminated with signal 2
proot info: pid 6738: terminated with signal 2
proot info: pid 6735: terminated with signal 2
proot info: pid 6736: terminated with signal 2
proot info: pid 6732: terminated with signal 2
proot info: pid 6734: terminated with signal 2
proot info: pid 6730: terminated with signal 2
proot info: pid 6740: terminated with signal 2
proot info: pid 6733: terminated with signal 2
proot info: pid 6731: terminated with signal 2
proot info: pid 6728: terminated with signal 2
proot info: pid 6729: terminated with signal 2
proot info: pid 6726: terminated with signal 2
proot info: pid 6727: terminated with signal 2
proot info: pid 6725: terminated with signal 2
proot info: pid 6724: terminated with signal 2
proot info: pid 6723: terminated with signal 2
proot info: pid 6722: terminated with signal 2
proot info: pid 6721: terminated with signal 2
proot info: pid 6720: terminated with signal 2
proot info: pid 6719: terminated with signal 2
proot info: pid 6718: terminated with signal 2
proot info: pid 6717: terminated with signal 2
proot info: pid 6716: terminated with signal 2
proot info: pid 6715: terminated with signal 2
It does this every time.
No, I don’t, but I’m about to host it from a VM from the same server to see if a clean linux installation fixes the issue.
Worked on the clean install, running inside a VM with a bridged VNIC, that’s hosted by the machine it won’t work on… smh
It’d be nice if we could still look into this and see why. I dont want to have to “guess” at how many resources I should dedicate to my VM when I could just run it off the main server… This could probably help a few people in the future…
I’m all ears.
If it makes you feel any better I run my server on 2gigs of ram and I don’t think it’s ever gone above like 200mb of resources for FiveM.
Each player is like 10-15mb and I don’t think it scales linear due to most of the work being offloaded to the client (It’s all peer to peer except for the server scripts)
So you never found out what caused it? Having the exact same problem on my VPS. It’s a standard Ubuntu 16.04 installation. Running multiple other game servers and websites but this is the only game server that does not work. Starting it works fine without any errors but I am unable to query it in any way on the 30120 port. Even with UFW and IPtables completely off. I’m at a loss here what it could be.
Is there any way the docker ethernet adapter could be causing any issue? And I also have ipv6 completely disabled because I only have an ipv4 address.
Enable ipv6 because it uses a loopback for the UDP protocal, otherwise no, I never figured it out unfortunately.
1 Like
Enabled ipv6 now and even got ipv6 addresses from my provider. Added it to my eth0 adapter. But still no connection.
Tried a FiveM server in a docker container and it works perfectly fine. The docker image didnt feel too stable so I would love to just run it natively instead of in docker.
Got any tips to check if that loopback to the UDP is actually functional on my system?
Hi,
Got the exactly same problem here, trying for about 10 hours. I’ve enabled IPv6 on my dedicated server, nothing. I’ve tried on such virtual machines with Ubuntu 16.04 and Debian 9 clean install, and same problem. After I’ve tried on Windows and everything work. The dedicated server is on Ubuntu 16.04 too with many others games servers. Maybe the linux version is broken or I forgot something? Thanks.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.