Troubleshooting
Fixes for the problems people meet most: paused features, key errors, caching, email, lockouts and updates.
"Ironhelm Suite has paused" or "is not running yet"
The site has no working API key. Open Settings, API key and updates: the message there says why (no key yet, removed from the account, subscription ended, key belongs to another site, or our server unreachable for 30 days). Connect a key from your account and everything resumes.
"This API key is connected to another site"
Each key belongs to one site. Disconnect it on that site, or create a new key for this one. Development copies (localhost, .local, .test, staging. subdomains) share their site's key; a copy on any other address needs its own key.
A page shows old content
Clear the cache from the top bar or run wp ironhelm cache flush. If the page still shows old content, your host or Cloudflare may cache it too; connect Cloudflare under Performance, CDN and Cloudflare so it clears automatically.
Something stopped working after a speed change
Switch off the last thing you turned on under Scripts and styles: each optimisation has its own switch. The asset manager shows exactly which files a page loads.
Emails do not arrive
Use Toolkit, Email delivery with a real email service, send a test, and run the DNS check: it tells you exactly which SPF, DKIM or DMARC record is missing.
Locked out
Use the unlock link on the login page, wp ironhelm unlock, or wp ironhelm 2fa-reset <user>. As a last resort, add define( 'IRONHELM_RECOVERY', true ); to wp-config.php to pause the security features until you remove it.
An update was refused
Ironhelm refuses an update whose signature does not match our release key. That protects you from a damaged or altered file. Try again later; if it keeps failing, download the release from your account and open a ticket.
Still stuck?
Customers: open a ticket from your account, with the site and a screenshot. Everyone else: contact us.