You paste your key into the loader, it thinks for a second, and then it stops. Sometimes the message is request failed, contact support. Sometimes the loader says it cannot connect to the server, or that a connection issue stopped sign in. The same product can show either wording. The key is not called invalid or expired; the loader simply refuses to go any further and points you at support. It happens on brand new keys and on keys that signed in fine the day before.
Why this happens
Our documentation does not list either of these two messages, so we will not guess at a mechanism. What is observable is this: the loader reaches the key field and then fails to complete sign in. In support records these cases usually end with someone on our side checking the key or the account, which is what the message is asking you to do. Customers in those records had often already confirmed the right loader from the official guide, pasted the key cleanly, turned off their antivirus and tried a VPN, and the sign in still failed. Support has also confirmed a run of these connection failures as a known issue on our side. If you want to know what is behind your own case, ask support for specifics rather than reading a cause into the wording.
How to fix it
Steps 1 to 3 are the checks support asks for first. Steps 4 to 6 are documented for other loader errors rather than for this one, but they are quick to rule out before you open a ticket.
- Confirm you are using the loader for the product and game you actually bought, and that you downloaded it from that product's official guide. Only use loaders linked from an official guide.
- Paste the key into the loader's license-key field with no extra spaces or characters.
- If this is an NFA game account rather than a cheat, use the Account Loader from the NFA accounts guide. The license key is the login, so there is no separate email and password.
- Turn on automatic date, time and time zone in Windows, select Sync now, then restart the loader. If you have only just paid, wait five minutes before trying again.
- Check your Windows version against the supported version in the product description. If a recent Windows update stopped a loader that worked before, roll that update back through Windows Recovery, and back up your files first.
- Download a fresh copy of the loader from its guide, install the current Microsoft Visual C++ redistributables, then restart Windows.
- Support often asks whether you have tried a different network or a VPN. Worth ruling out, though a VPN can help with network privacy without guaranteeing access.
- If security software flagged or blocked the loader, send support the detection name and a screenshot. Do not disable Windows security features as a workaround.
- If the key has been used on another computer, or you have changed PC or used a supported spoofer, ask live chat for a human and request an HWID reset.
- Check the status board before spending longer on your own setup. Connection failures at sign in have been confirmed as known issues on our side before.
- If it still fails, contact support with the product name, the game, the exact error wording or a screenshot, the steps you have already completed, and your website username and license key.
Which products this applies to
The records behind this page are mostly Frost and Frost LITE for BO6, BO7 and Warzone, Frost LITE for Arc Raiders, and Inferno for Siege X. The same key-entry checks apply to Armani and to the Account Loader used for NFA accounts. If your product is not named here, ask support for specifics rather than assuming the same cause. Check the status board for your product before you troubleshoot further.
If the loader still will not sign you in after these steps, open live support with your product, game, error wording and key, and ask for a human. We can compensate unused time in most error-related cases.
