License Key on CentOS 7 Server

Currently setting up a FiveM server on CentOS 7, I set up the License key for the VPS’s IP, but when I enter it I get this error:

An error occurred while checking server license key.
An error occurred while checking server license key.Received signal 6
[end of stack trace]

I tried re-entering the license key in keymaster.fivem.net but it gave me the same error

Could you please upload a screenshot or pastebin of the whole console output when launching your server.

Getting this message usually refers to you incorrectly launching the server or perhaps you have blocked all outgoing connections (through iptables)

https://hastebin.com/agabesaguq.coffeescript

And your Config file?

# only change these if you're using a server with multiple network interfaces
endpoint_add_tcp "0.0.0.0:30120"
endpoint_add_udp "0.0.0.0:30120"

start mapmanager
start chat
start spawnmanager
start sessionmanager
start fivem
start hardcap
start ■■■■■■■
start scoreboard
start playernames

# allow client mods such as Lamda Menu?
sv_scriptHookAllowed 1

# change this
#rcon_password yay

# a comma-separated list of tags for your server
# for example: sets tags "drifting, cars, racing" or sets tags "roleplay, military, tanks"
sets tags "default"

sv_hostname "OriginGaming.Net"

# nested configs!
#exec server_internal.cfg

# loading a server icon (96x96 PNG file)
#load_server_icon myLogo.png

# convars for use from script
set temp_convar "hey world!"

# Uncomment to DISABLE your server coming up in the server list
#sv_master1 ""

# want to only allow players authenticated with a third-party provider like Steam (don't forget, Social Club is a third party provider too!)?
#sv_authMaxVariance 1
#sv_authMinTrust 5

# add system admins
add_ace group.admin command allow # allow all commands
add_ace group.admin command.quit deny # but don't allow quit
add_principal identifier.steam:110000112345678 group.admin # add the admin to the group

# remove the # to hide player endpoints in external log output
#sv_endpointprivacy true

# server slots limit (must be between 1 and 32)
sv_maxclients 32

# license key for server (https://keymaster.fivem.net)
sv_licenseKey dont know if im allowed to publicly post this, just to be safe :p

I’m guessing a host firewall issue. What firewall are you using, CentOS’s firewalld or iptables? Or something else? If firewalld, could you show the output of firewall-cmd --list-all-zones ? If iptables, how about iptables -L ?

When I type firewall-cmd --list-all-zones i get this:
https://hastebin.com/tohehimedu.coffeescript

When i type iptables -L i get this:
https://hastebin.com/omasuteraz.hs

When setting up the remote desktop access i had to do a few commands with the firewall with a port a tcp, would i have to do the same with the fivem port, I made a support ticket about port-forwarding and they said:

Yes of course, all ports are opened on our network by default. Please let us know if you have any other questions.

I did
firewall-cmd --zone=public --add-port=30120/tcp --permanent and
firewall-cmd --zone=public --add-port=30120/udp --permanent

to see if that would fix it, it didn’t

endpoint_add_tcp “0.0.0.0:30120”
endpoint_add_udp "0.0.0.0:30120

Add your servers IP in the 0.0.0.0

do not change the endpoints it will help nothing and the info above it explains what its for.

1 Like

Ok, when i setup my server on my PC i didn’t need to change that

EDIT: Didn’t work

It’s problem in FiveM server.
All versions >=577 has been broken. Use 576 or older builds, it’s worked fine on CentOS.

Ok I will try, why would they upload them if they’re fucked?

They are meant for testing

Might know the issue, the support people said

Our CentOS and Fedora templates provide FirewallD, all others use iptables.
Please let me know if there is anything I can do to help.

So anyone know a way around firewallD?

@BombermaG Thanks it worked, you’re a life saver!

they’re not ‘fucked’, working fine on our systems as well as many others.

if you’re having issues, please provide a consistent repro.

builds older than 585 are not recommended for use and will be blocked in the near future

Ok, weird, well that worked for me, I guess i’ll use it until you guys block it

thanks, now if there’s an actual issue we’ll never know nor will it be fixed!

1 Like

How can I make a repo for this issue