BobuxBOT

Luarmor time error? Check your clock

TIME_ERROR means the timestamp in the request did not line up with the server. Set the clock to automatic, restart, and test before touching the key.

TIME_ERROR means the client's clock did not line up with the server's when the request was signed. Set the clock to automatic, restart the device and run the loader again. That fixes the common case before you touch the key or the executor.

What the code says

Code Documentation message Documentation meaning
TIME_ERROR Client time is invalid Request took too long to complete or os.time() is broken

The code has two named causes and they point at different places. The first is a request that took too long between signing and arrival. The second is a client clock that returns the wrong value. Both end in the same rejection because the service checks a timestamp. It belongs to the client layer, as set out in Luarmor error codes.

Why a licence check reads the clock

A signed request has to prove it was made recently. Otherwise a captured request could be replayed later. The external API documentation shows the flow: the client fetches server time from a sync endpoint, keeps the 32-bit value, and uses it in the request signature and in the clienttime header.

The server can then reject a request whose time is far from its own, or one that spent too long in transit. The exact tolerance is not published. Set the clock to automatic and the size of that tolerance stops mattering.

In the Lua path the documentation names os.time(), so the local clock is read there. In the external path the value starts as server time, and a long delay between the sync request and the key check produces the same code. Both explanations fit the same sentence.

The three clocks involved

Clock Where it comes from What can go wrong
System clock The operating system Wrong date, wrong minutes, manual setting
os.time() What Lua returns for the system clock Hooked or fixed by the client
Server clock The service Rarely wrong, and not yours to fix

Your time zone is not one of them. os.time() returns a Unix timestamp, which is counted in UTC. Changing the time zone changes the display, not the number. A clock set to the wrong minute, day or year changes the number and produces the error.

Fix the clock in four steps

  1. Turn on automatic date and time.
  2. Turn on automatic time zone. The zone does not change the timestamp, but it leaves one fewer setting to get wrong.
  3. Restart the device, then compare the minutes with a time site.
  4. Run the loader unchanged and read the result.

On Windows the setting is under Time and language. On macOS and iOS it is under Date and time. On Android it is under System, then Date and time. If the device cannot reach a time server, set the time manually, reconnect, and switch automatic back on.

A device that has been asleep for days can wake with a stale clock. A virtual machine restored from a snapshot can wake with the clock of the snapshot. Both look like a broken clock to the service.

When the clock is right and the error stays

The next suspect is the client. If the executor hooks os.time() or returns a fixed value, the system clock can be perfect and the request still carries the wrong number. Try another client with the same loader and key. If the code disappears, the first client is the cause. A client that alters the request can also produce Luarmor security error, so note which code you get on each client.

A proxy or a slow link can also produce the error by delaying the request between signing and arrival. Try another network. A device with a dead CMOS battery loses time whenever it is unplugged, which explains an error that appears only after the machine has been off.

If every user sees TIME_ERROR at the same time, the service side is the common piece. That is unusual, because the code is normally about the client, but it is testable: compare with other users before changing your machine.

What does not cause TIME_ERROR

A different time zone, daylight saving, a slow PC, or a long queue before the loader starts do not cause it. The timestamp is read when the request is built, not when you launched the game. A device that is slow but correct still sends a correct value.

A new key does not fix it either. The key is one of the signed values, and a different key with the same wrong timestamp fails the same check. Read the code and fix the clock before you spend anything.

FAQ

Does my time zone cause TIME_ERROR?

No. The service compares Unix timestamps, which are independent of the zone, so a device set to another zone still sends the correct number. Change the zone if you like. With automatic time on, neither the time nor the zone can be set wrong.

How exact does my clock need to be?

The tolerance is not published, so no number of seconds is worth aiming at. Automatic time removes the error without guessing the window. If you set the clock by hand, compare the minutes with a time site after a restart, because a small drift can return after the machine sleeps.

Can a virtual machine cause TIME_ERROR?

Yes. A VM restored from a snapshot can resume with the clock of the moment the snapshot was taken. Resync the guest clock, then retry. If the VM also hides or changes the hardware fingerprint, the executor check can fail first, so read the code before assuming the clock is the only problem.

Can a VPN cause TIME_ERROR?

Only indirectly. A VPN can add latency, and a request that takes too long between signing and arrival fails the timing check. A fast VPN usually does not. Test with it off to remove one variable, then compare. A VPN is more likely to affect an ad session than a signed licence request.

Can TIME_ERROR happen on mobile?

Yes. Phones and tablets can drift when they are offline, and a manual clock setting can be wrong after a factory reset or a long period without a network. Set date and time to automatic, restart the device, and run the loader again before changing the client. The mobile article covers the platform differences.

Will a new key fix TIME_ERROR?

No. The error is about the timestamp the request carries. A new key signed with the same wrong time produces the same rejection. Fix the clock or the client, then use the key you already have. If the key also has a problem, the next code will tell you.

Is TIME_ERROR a sign of an outage?

Usually not. UNKNOWN_ERROR is the code the documentation associates with an outage or an API restart. TIME_ERROR names the client clock or a slow request. If several users see it at once, compare with them and with the status discussion.

Does restarting the game fix it?

It can, because the client reads the clock again when it rebuilds the request. A restart does not correct the system clock, so the error can return after the next sleep or reboot. Set automatic time as well, otherwise you are fixing the symptom for one session.

Search Roblox games

Popular now Pick a result to open its page
↑↓ navigate ↩ open esc close