Hello , is there any updating or the key server is not working ?
Update your artifact so you can see the actual reason why it failed
Mean i describe as having problem to authenticate the server key not the server data or something like that …
I asked on discord but no answer at all …
Newer artifacts no longer say “Could not authenticate server license key” and display the actual error so that would help with determining why you can’t authenticate your license key.
i got the https://runtime.fivem.net/artifacts/fivem/build_server_windows/master/2432-9791666094497d044990af0ea23e940494f179f5/server.zip
and still the error
say “Could not authenticate server license key”
Then it means the license key you’re trying to use is not valid or deactivated, please check
- i use a 2432 artifact
- i did the new key
- using azure microsoft
and results the same problem …
In your server.cfg
this is what it should look like
set sv_licenseKey "abcd1abcd2abcd3abcd4abcd5abcd6abc"
Nope , i used premade server to test out and still the same problem … then later on i use a artifacts the newest and server.cfg “xxxxxxxxx” licence key and still problem
Can you send a screenshot of your folder layout for FiveM server as well as the batch file you are using to launch it.
Make sure your firewall isn’t blocking connecting to connect to verify your license. If you disable FiveM from the internet it will yield that same exact error.
i have it like that 99% things are corrected and step by step done from tutorials etc …
Disable your firewall for a temporary test or setup both incoming and outgoing rules properly for FXServer.exe.
i already open a ports for server like everything is ok but the error still
and when logging onto https://keymaster.fivem.net you see the same key that is in your server.cfg and on the site it says “Active” ?
yes everything is double checked . and still the error
I don’t know where you got that “Start Server here.cmd” from but that’s old/wrong.
Follow https://docs.fivem.net/docs/server-manual/setting-up-a-server/#windows
Also big tip: Do not add any other resources until you have the most basic server running from that guide
It is the typical ESX junk.
i did everything and STILL THE PROBLEM its probably mistake on microsoft servers going try local on my pc and hope will works
Okey , i did my pc aswell and same error