IP reset

An IP reset clears the IP your license is locked to, so the next connection can bind a new one. An AstroShield admin reviews every request.

When you need one#

You need an IP reset when the console banner says IP RESET REQUIRED, or when you see Auth failed: IP Locked. Typical reasons:

you moved the server to a new host or machine,
your hosting provider changed the server's IP,
your outbound IP rotated.

Request a reset#

You must be the owner of the server. Admins who only have other permissions cannot request a reset.

Open the request form

Either open IP Reset Requests in the dashboard sidebar, or open your server, go to FiveM resource, Manage resource and choose IP Unlock Request. The second way also shows the IP that is currently saved.

Choose the server and explain why

Select the server and write a short reason, up to 1000 characters. Mention what changed and when, for example the hosting provider and the date of the move. A clear reason gets handled faster.

Submit

Click Submit Request. AstroShield staff are notified automatically. Your request is also written to the server's audit log.

Wait for the review

An admin approves or denies the request. Approving it clears the saved IP. The dashboard does not email you, so check by restarting AstroShield.

Limits#

Only the owner of the server can request a reset.
You can send 3 requests per 7 days. Every request counts, including denied ones, and the limit is per user, not per server. When you hit it the dashboard says Too many requests this week.
The reason is required.

Plan ahead, because a request has to be reviewed by a person.

Restart AstroShield after approval#

After a refusal the resource does not retry on its own. Once your request is approved:

Restart the resource in the server console of the server that should own the license:
Output
```
restart AstroShield
```
Watch the banner. It should show License active (or Lifetime license). The IP it just connected from is now saved as the license's IP.

If this is your only server, the dashboard may open the Setup Wizard instead of the overview until the server has connected again. That is expected, because the license has no IP bound yet.

Moving to a new host#

Follow this order so the right machine ends up bound:

Set up the new server and copy over the AstroShield folder, including the .key file. Do not start AstroShield on it yet.
Submit the IP reset request and wait for it to be approved.
Stop AstroShield on the old server. A license allows only one live connection, so the new server would be refused while the old one is connected. If the old server restarts AstroShield before the new one connects, it binds its old IP again.
Start AstroShield on the new server. It connects and binds the new IP.

Submit the request when you are ready to switch, so there is little time between approval and step 3.

Troubleshooting#

What you see	What to do
`Auth failed: IP Locked`	Your server connected from a different IP than the saved one. Request a reset.
Request approved but still `IP Locked`	Run `restart AstroShield`. The resource does not retry after a refusal.
`Auth failed: Already Connected`	The old server is still connected with the same key. Stop it, then restart AstroShield on the new one.
`Too many requests this week.`	You used all 3 requests. Wait for the 7-day window to pass, or ask on Discord if it is urgent.
`No permission` or `Owner rights required to unlock the IP.`	Only the owner of the server can request a reset. Ask the owner to submit it.
The request was denied	Ask on Discord why. Fix what staff point out and submit a new request.

Avoid the next reset

The IP that counts is your server's outbound address. If it keeps changing, move the server to a host with a fixed IP. See IP lock.