IP reset requests

Your licence locks to one server address. What happens when that address changes, how to get it unlocked, and the limits on asking again.

A licence binds to the IP address your server first verifies from, and only ever verifies from that address again. If your server moves, verification is refused until an admin unlocks it. This page covers the refusal, why the lock exists, and how to raise and track a reset.

What it looks like

The resource refuses to start and prints the address it was refused from. It stops after the first attempt rather than retrying, because the address is not going to change on its own.

console

[Raven Anticheat] Error: Server verification failed.
[Raven Anticheat] Error: Reason: Unauthorized IP. Request received from
198.51.100.42. If your server moved, request an IP reset from your dashboard under
IP Reset, or ask an admin in our Discord: https://www.ravenac.net/discord

The line after Reason: is the actual refusal, and it is never generic. Verification checks things in a fixed order, so the first thing that is wrong is the only thing you are told about.

Order	What is refused
1	The request could not be read at all, which means the `licence.key` file is wrong or truncated, or the resource files were edited.
2	No server holds that licence key.
3	The address. This page is about this one.
4	The licence is suspended, which only an admin can lift.
5	The licence has expired, which you renew yourself.
6	The licence is already running another FiveM server at this address, on a different port.

Because the address is checked third, a server on a new address gets this reason even when its licence has also expired or been suspended. The resource version is recorded at this point but never refused on, so being out of date is not one of the reasons here.

If you see a different reason there, this page is not your problem. Troubleshooting covers the others.

Why the lock exists

One licence runs one server. Binding it to an address is what stops a single key being shared across several communities, which is why a reset is reviewed by a person rather than granted automatically. A refusal is the lock working, not a fault.

The refusal message deliberately does not name the address the licence is bound to. That response goes to whoever holds the key, which on a leaked or resold key is not you, and echoing the bound address would hand them the one fact they are missing. The address it was refused from is fine to print: it is the machine they are already sitting on.

Requesting a reset

Open the IP Reset page

The entry only appears if you own a server. Server administrators cannot raise a reset, however many dashboard permissions they hold, because rebinding a licence decides where the product runs.

Pick the server

Choose the server that is locked out. Each one shows the address its licence is currently bound to, which is the quickest way to confirm you are unlocking the right licence.

Only servers with an active licence are listed, along with any whose subscription is inside its three-day renewal grace, which are marked Renewal pending with the date they are covered until. An expired or suspended licence stays bound to its address, but the page offers no reset until the licence is active again, so renew it first, or ask in our Discord if it was suspended, then come back. The picker hiding them is a courtesy; an expired licence is refused by the endpoint itself even if you reach past it.

Say why the address changed

Tap the closest reason and it fills in the box, which you can then keep typing into. At least 10 characters, and at most 800.

Add the new address, if you have it

Optional, and capped at 64 characters. Copy it from the Unauthorized IP line in your console, since it saves the admin looking it up. It is a hint on the card and nothing is ever acted on from it.

Send it and restart

The request goes straight to our admins. Once it is approved your licence unbinds, and it re-binds to whatever address your server verifies from on the next start, so restart the server after you hear back.

The reasons on offer

Button	What it fills in
Changed hosting provider	We changed hosting provider, so the server runs on a new IP address.
Moved to a new machine	The server was rebuilt on a new machine, so its IP address changed.
Host changed our IP	Our host changed the server IP address. We did not move anything ourselves.
Dynamic IP changed	The server is on a dynamic IP address and it changed on its own.
Added a proxy or VPN	We put a proxy in front of the server, so it now connects from a different address.
Moved datacentre	We moved the server to a different datacentre, so it has a new IP address.

The text is inserted into the box rather than submitted as a code, so anyone with a detail worth adding can just keep typing.

One request at a time

State	Can you ask again	Why
Pending	No	The admin has not answered yet, and a second card tells them nothing they do not already have. It just buries the first.
Declined	After 7 days	A denial is a decision. Letting you re-ask immediately turns "no" into "ask again until someone says yes".
Approved	Yes, immediately	The lock is already gone, so the record is cleared outright and a genuine move months later never inherits an old cooldown.

The refusal while one is pending or a denial is still inside its week says which of the two it is, and how many days are left.

Either way the request writes a row to your server's activity log, so there is a durable record of asking even if the Discord card never arrives.

Running two servers on one address

The lock is on the address, so two servers on the same machine both pass it. Raven refuses the second one separately: if a server is already online on that address under this licence, another one starting on a different port is turned away with a message saying so. That is not something a reset fixes. One licence runs one server, and a second server needs a second licence.

An ordinary restart is not caught by this, because a restart drops its WebSocket before it logs in again, so nothing is connected by the time it comes back and any port is fine. That refusal is also the one verification failure the resource keeps retrying, because a server that died without closing its socket can look like a second instance for a short while, and retrying lets that heal itself.

If you are still stuck

Check the console line again against the table at the top of this page. The reason names which check failed.
Confirm the server really did change address. Some hosts rotate outbound addresses without telling you.
Ask in our Discord with your server name and the address in the error.