Help

Troubleshooting

Fixes for the things people run into — install warnings, being blocked by a firewall (429/403), certificates, missing variables, and updates.

Installing

Windows says “Windows protected your PC”. The app is new and not yet code-signed, so SmartScreen doesn't recognise it. Choose More info → Run anyway. This goes away as more people install it and once the app is signed.

macOS says the app can't be opened. The Mac version is a preview and not yet signed by Apple. Right-click the app → Open, then Open again. You only need to do this once.

Linux AppImage doesn't start. Make it executable — chmod +x APITestCenter-*.AppImage — and run it. Some distributions need libfuse2 for AppImages; the .deb doesn't.

atc is not recognised after installing the app. Open a new terminal — a terminal that was already open keeps the old PATH. On macOS, link it once (see Command line and CI). The portable Windows app, the AppImage and the Microsoft Store version don't add atc; use npx apitestcenter.

atc --version shows an older version. Another copy comes first in your PATH — usually an npm install -g apitestcenter from before. Update it with npm install -g apitestcenter@latest, or remove it with npm uninstall -g apitestcenter to use the app's. In a project, npx apitestcenter uses the project's own copy: npm install -D apitestcenter@latest there.

My company network blocks the website download. Ask IT to allow github.com downloads, or install from the Microsoft Store when it's listed. The Store keeps its copy up to date.

Blocked: 429 or 403

The report says Blocked by a rate limit or firewall, or most requests failed with 429 Too Many Requests or 403 Forbidden.

Something in front of the API — a CDN (Cloudflare, Akamai, CloudFront), an API gateway, or a firewall — decided the traffic looked like an attack and started refusing it. Often it keeps refusing for a while after the load drops, which the report calls a lockout.

What to do:

  1. Don't repeat it against a public site or someone else's API. It can get your address blocked for longer.
  2. Test a staging server without the limit, or ask the API's owner to allow your computer's address for the test.
  3. Lower the load. Use Requests per second with a modest rate instead of many simulated users with no think time. The report shows the rate at which refusals started — stay below it.
  4. If the API is yours: the 429 limit is a finding. It tells you what your gateway allows per caller.

Failures and errors

{{name}} is not defined. The request uses a variable that has no value. Pick an environment that defines it, add it, or check for a typo. In a collection run, the message also says which earlier request should have saved it.

401 Unauthorized. The token is missing or expired. Use Run first to sign in automatically, or update the token in your environment.

**Certificate errors (self-signed, unable to get local issuer certificate). The desktop app already trusts every certificate your computer trusts — including a company proxy's (Zscaler and similar) and your company's own roots. If a server's certificate comes from a CA your computer doesn't know, add that CA under Manage certificates → Trusted certificate authorities (see Client certificates and trusted CAs). New requests skip the certificate check (Settings → Skip TLS certificate check**), so this shows only on a request where it is off — such as one saved before 0.10.0. Turn it on for a test server; for production, fix the certificate or add its CA instead.

NODE_TLS_REJECT_UNAUTHORIZED=0 on your computer. Some setups turn certificate checks off machine-wide for a proxy. The desktop app ignores it — it checks against the certificates your computer trusts instead — and logs that it did. The command line still honours it.

Timeouts or “no answer”. The API didn't answer in time (default 60 seconds, in Settings → Timeout), the address is wrong, or a VPN or firewall is in the way. Try Send first: if a single request fails, a performance test will too.

The performance test didn't start because the first request failed. Before loading, the app sends the request once; if that doesn't answer with a 2xx status, it stops so you don't send thousands of failing requests. The Response tab says Performance test not started and shows that answer. Fix the request and run again — or, if that status is what you expect (a 404 you're testing on purpose, say), press Run anyway. On the command line, --no-check skips this check.

The app

“Engine offline” or “k6 missing” at the left of the status bar. The app's engine runs in the background; restart the app. If k6 is missing, reinstall — it ships inside the app.

atc ui shows “APITestCenter was stopped”. The atc ui in that terminal was stopped (Ctrl+C or the terminal was closed). Close the tab, and run atc ui again to carry on — everything you saved is in your data folder.

Updates

About (the version, at the right of the status bar) shows the update status, with Check for updates. The app also checks by itself about 15 seconds after it starts and every 6 hours — see Update check.

About saysWhat it means
Checks for a new version shortly after opening and every 6 hours.No check has finished yet.
Checking for a new version…A check is running.
You have the latest version.Nothing to do.
Version x.y.z is available.Press See what's in x.y.z…: what it brings, then Download and install (or, for portable Windows, macOS and .deb, Open the download page).
Downloading version x.y.z… n%It's downloading; Checking the download… at 100% while it's verified. You can keep working.
Version x.y.z is downloaded.Press Restart to update… → Restart now, or it updates the next time the app quits.
— an important updateThe new version fixes something you shouldn't wait for; its dialog says why. Install it soon.
The download didn't finish.Press Try again in the update's dialog, or download from the website.
Couldn't reach GitHub, where updates come from.Offline, or a company firewall or proxy blocks github.com. Press Open the download page and get it from the website instead.
The update check failed.Try again later, or download from the website.
This copy comes from the Microsoft Store, which keeps it up to date.The Store updates it; there is no check button.
Update checks are turned off on this computer (ATC_NO_UPDATE).The ATC_NO_UPDATE=1 environment variable is set. Remove it to turn checks back on.
Updates are checked by the desktop app. This copy runs in a browser.You're in npx apitestcenter ui. npx fetches the command line from npm.

Your requests and history stay as they are when you update.

Your files

Where are my files? How do I start fresh? See Privacy and your data. About → Open folder opens it. Close the app before moving or deleting files.

Still stuck? Write to support@apitestcenter.com with what you tried and, if you can, the exported JSON report.

Something unclear or missing? Write to support@apitestcenter.com — the guide improves with every question.