This page lists the messages Promptor 2.1.0 shows when something goes wrong, what causes each one and how to fix it. Search the page (Ctrl+F or Cmd+F) for a few words of the message you see. Since 2.1.0 the chat and the admin can be shown in seven languages, so on a non-English site the wording is translated; the English text below is the original.
Messages visitors see in the chat
Setup and AI provider
| Message | Cause | Fix |
|---|
| "Please set up your OpenAI API key or start a free trial in the plugin settings." | Free edition: no API key is saved and no free trial has been started. | Add a key in Settings › AI Behavior, or start the trial. See Get and add an OpenAI API key. |
| "API configuration needed. Please contact the site administrator to set up the OpenAI API key." | No API key is saved (Pro, or a site without the trial). | Add a key in Settings › AI Behavior. |
| "Please enter your OpenAI API key to continue using Promptor." | The free trial has ended (used up, expired or revoked) and no key is saved. | Add your own OpenAI API key. |
| "Your free trial queries have been used up…" / "Your free trial has expired…" / "Your trial access has been revoked…" / "Your trial access is no longer available…" | The trial reached its 25 answers or its end date, or was revoked. | Add your own OpenAI API key. |
| "AI service error: … Please try again or contact support if this persists." | The AI provider refused the request, for example an invalid key or no credit left. | Click Verify Key in Settings › AI Behavior and check billing on your OpenAI account. |
| "Connection issue. Please check your internet connection and try again." | Your server could not reach the AI provider, or it took too long (45 seconds, 60 seconds when streaming). | Try again. If it persists, ask your host whether outgoing connections to api.openai.com are blocked or slow. |
| "Connection issue. Please try again." | During the free trial, the trial service could not be reached. | Try again later, or add your own key. |
| "Unable to process your query. Please check your connection and try again." | Promptor could not create the search embedding for the question. | Same as above; also verify your API key. |
| "AI service returned an unexpected response." | The provider or trial service returned something that was not valid data. | Try again. If it keeps happening, contact support (see the end of this page). |
| "Sorry, I could not put that answer together. Please rephrase your question or try again." | The answer could not be read, usually because it was cut off. | Raise Maximum Tokens in Settings › AI Behavior. See Models, temperature and response length. |
| "📚 The Knowledge Base is currently empty…" | The knowledge base used by this chat has no indexed content. | Add content and sync. See Sync, re-index and clear a knowledge base. |
| "Please type your question above and press Send to get started!" | The question was empty. | The visitor types a question. |
A polite refusal such as "I can only help with questions about …" is not an error. Since 2.1.0 the assistant declines questions that have nothing to do with your business (general knowledge, code, homework). See Answers are wrong or miss your content.
Limits
| Message | Cause | Fix |
|---|
| "Monthly limit reached (100 queries). Upgrade to Pro for unlimited queries and advanced features!" | The free edition has used its 100 AI answers for this calendar month. | Wait: the allowance resets automatically after the last day of the month (your site's time zone). Or upgrade to Pro. The lead form keeps working in the meantime. See Free vs Pro. |
| "Our AI assistant is temporarily unavailable due to high usage. Please try again later or contact us directly." | A daily or monthly token limit was reached and When Limit Reached is set to Pause AI chat. | Raise the limit or choose Fallback to GPT-3.5-turbo in Settings › AI Usage. See Control AI costs with usage limits. |
| "Too many requests. Please wait … seconds and try again." | The visitor sent more than 20 messages in a minute or 200 in an hour. | Wait the time shown. This protects you from abuse and runaway costs. |
| "Too many attempts. Please try again later." | More than 20 form submissions from the same IP address in 10 minutes. | Wait 10 minutes. |
In the admin, AI Conversations shows "Monthly Query Limit: x / 100 used" on the free edition.
Page and security
| Message | Cause | Fix |
|---|
| "Security verification failed. Please refresh the page and try again." | The lead form or Add to Cart security token was rejected, usually because a cached page holds an expired token. | Refresh the page. If visitors see it often, see Caching plugins. |
| "Security validation failed. Please refresh the page." | The chat's security tokens are missing from the page when it loads. | Clear caches; exclude Promptor's inline settings from JavaScript optimization. See Caching plugins. |
| "Configuration error. Please contact administrator." | The chat's settings did not load in the page, often because JavaScript optimization removed or delayed them. | Exclude Promptor's scripts from delay and combine. See Caching plugins. |
| "Chat could not be loaded. (Context Error)" | The chat's knowledge base data is missing from the page. | Clear caches; check the shortcode's context. See The chat doesn't appear or looks wrong. |
| "Failed to initialize chat. Please refresh the page." | A JavaScript error stopped the chat from starting, often a conflict with another script. | Check the browser console. See The chat doesn't answer or shows an error. |
| "Network error. Please check your connection." / "Request timed out. Please try again." | The browser got no answer from your server. | Try again; if it persists, check your server and security plugins. |
| Message | Cause | Fix |
|---|
| "Please fill in your name and email." / "Name and email are required fields." | The visitor left the name or email empty. | The visitor fills in both. |
| "Please enter a valid email address." / "Please provide a valid email address." | The email address is not valid. | The visitor corrects it. |
| "Please enter a valid phone number (7 to 15 digits; +, spaces, brackets and dashes are allowed)." | The phone number has too few or too many digits. Since 2.1.0 the form checks this before sending. | The visitor corrects it. The phone field is optional. |
| "Please provide a valid phone number (7–30 …)" | The server rejected the phone number. | The visitor corrects it. |
| "Name is too long…" / "Notes are too long…" | Name over 100 characters, or notes over 5,000 characters. | The visitor shortens it. |
| "Your message is too long. Please shorten it and try again." | A chat message is longer than 5,000 characters. | The visitor shortens it. |
| "Could not save your submission. Please try again later." | The lead could not be saved in the database. | Check Diagnostics (Pro) or your server's error log. |
Human handoff
| Message | Cause | Fix |
|---|
| "No contact channels are available right now. Please leave your details below and we will get back to you." | Handoff is on, but no channel is enabled in Settings › Handoff & Channels. | Add at least one channel (WhatsApp, email or phone in Free). See Hand visitors over to a human. |
| "Our team is currently away. We are back …" or your own away message | Pro: the visitor asked outside your operating hours. | Not an error. Adjust Operating Hours or the Away message if needed. |
Shop (Pro, WooCommerce)
| Message | Cause | Fix |
|---|
| "This product cannot be purchased." | The product is not purchasable, out of stock or not published. | Check the product in WooCommerce. |
| "WooCommerce is not active." | WooCommerce was deactivated. | Activate WooCommerce. |
| "Your coupon code: …" instead of "Coupon applied to your cart." | The coupon chip could not apply the code, so the chat shows it and copies it to the clipboard. Common causes: the code in Settings › WooCommerce Assistant does not match a WooCommerce coupon, or WooCommerce rejected it (expired, usage limit, minimum spend). | Check the coupon in WooCommerce and the code in Settings › WooCommerce Assistant. See Order help and coupons. |
Messages you see in the admin
API key and AI
| Message | Where | Cause | Fix |
|---|
| "Error: Invalid API Key. Please check your key and try again." | Verify Key | OpenAI rejected the key. | Create a new key on the OpenAI platform and paste it. |
| "API Key cannot be empty." | Verify Key | The key field is empty. | Paste your key first. |
| "Connection Error: …" | Verify Key | Your server could not reach OpenAI. | Ask your host to allow outgoing HTTPS to api.openai.com. |
| "The API key format looks unusual. Your previous key has been kept." | Saving Settings › AI Behavior | The pasted key does not look like an OpenAI key (it should start with sk-). | Copy the key again, without spaces. |
| "Trial activation failed (HTTP …): …" | Setup wizard | The trial service could not be reached or refused activation. | Try again later, or add your own key. |
| "No indexed content found. Please sync some content first." | Generate with AI | The knowledge base has nothing indexed. | Sync first, then generate. |
| "OpenAI API key not configured." | Generate with AI | No API key is saved. | Add an API key. |
Knowledge bases and content
| Message | Where | Cause | Fix |
|---|
| "You are using Promptor Lite. You can select a maximum of 35 content items (pages, posts, files or Q&A entries) per knowledge base. Upgrade to Pro for unlimited content." | Saving content, adding a Q&A entry or an unanswered question | The free edition's knowledge base already holds 35 items. | Deselect items you need less, or upgrade. See Choose content and set content roles. |
| "OpenAI API Key is not set in Settings > API Settings." | Syncing, re-indexing, saving a Q&A entry | No API key is saved. The key lives in Settings › AI Behavior. | Add your key in Settings › AI Behavior. |
| "WooCommerce product indexing is a Pro feature." | Syncing | Products need Pro. | Remove them or upgrade. |
| "PDF indexing is a Pro feature. TXT and Markdown files work in the free edition." (or "Word indexing…") | Syncing files | PDF and DOCX files need Pro. | Use TXT or Markdown files, or upgrade. See Add TXT, Markdown, PDF and DOCX files. |
| "This file type is not supported. Upload PDF, TXT, Markdown or DOCX files." | Syncing files | The attachment is another file type. | Convert it to one of the supported types. |
| "PDF Parser library is not installed; only the title and description can be indexed." | Syncing a PDF (Pro) | The PDF text extraction library is not available on your site. | The PDF's title, caption and description are still indexed. If answers need the PDF's text, copy the key parts into a page, a TXT or Markdown file, or a Q&A entry. |
| "The PDF could not be parsed." / "The DOCX file could not be opened." / "The DOCX file has no readable body." | Syncing files (Pro) | The file is damaged, encrypted, scanned (image only) or empty. | Save it again as a text-based file and re-upload. |
| "The PHP Zip extension is required to read DOCX files." | Syncing a DOCX (Pro) | Your server's PHP lacks ZipArchive. | Ask your host to enable the PHP Zip extension. |
| "The question cannot be empty." / "The answer cannot be empty." | Q&A tab | A field of the Q&A entry is empty. | Fill in both. See Add Q&A entries. |
| "Knowledge base name cannot be empty." / "Knowledge base with this name already exists." | Creating a knowledge base | The key is empty or taken. | Choose another short, lowercase name. |
| "Cannot delete the default knowledge base." | Deleting a knowledge base | The default knowledge base is permanent. | Clear its index instead. |
Crawler (Pro)
| Message | Cause | Fix |
|---|
| "Only the current site domain is allowed for crawling." | The sitemap URL is on another domain. | Use your own site's sitemap. |
| "Sitemap URL is required." | The field is empty. | Enter your sitemap URL. |
| "Could not fetch sitemap…" / "The provided URL does not contain valid XML…" | The sitemap URL is wrong or not reachable. | Open the URL in your browser to check it. See Index your site with the website crawler. |
| "No URLs found in the sitemap after applying filters…" | The sitemap is empty, or your crawler filter settings exclude every URL. | Check the sitemap and loosen the filters. |
| "Scheduled crawling is turned off." | You clicked Run now while the schedule is set to off. | Choose an interval and save first. |
| "A crawl is already in progress." | A scheduled crawl is still working through its batches. | Wait for it to finish; Last run updates when it does. |
| "Website Crawler is a Pro feature. Please upgrade your license." | You are on the free edition. | See Free vs Pro. |
Notifications, digest and webhooks (Pro)
| Message | Cause | Fix |
|---|
| "Slack notifications are disabled or Webhook URL is invalid." | Slack is off or the URL does not start with https://hooks.slack.com/services/. | See Email and Slack notifications. |
| "The digest could not be sent. …" | WordPress could not send the test digest email; the reason from your mail setup follows. | Check your SMTP plugin or host's mail settings. See The weekly digest email. |
| "Webhook URL is required." / "Invalid webhook URL format. Only HTTP and HTTPS protocols are allowed." | The Webhook URL is empty or not a web address. | Enter a full https:// URL. |
| "Warning: Using HTTP instead of HTTPS is not recommended for security reasons." | The URL uses http://. | Use https:// if your endpoint supports it. |
| "This feature is only available in Promptor Pro." | Opening a Pro screen such as Diagnostics without an active Pro license. | Activate your license. See Upgrade, activate your license and update. |
Messages in your AI client (Pro MCP server)
These appear in Claude, ChatGPT, Cursor or another MCP client connected to your site. See Connect Claude, ChatGPT or Cursor with the MCP server.
| Message | Cause | Fix |
|---|
| "Authentication required. Use a WordPress Application Password with HTTP Basic auth." | The client sent no credentials, or a wrong user name or Application Password. Some hosts and security plugins also strip the Authorization header. | Create a new Application Password and update the client's configuration. If it still fails, ask your host whether the Authorization header reaches WordPress. |
| "You do not have permission to use the Promptor MCP server." | The Application Password belongs to a user who is not an administrator. | Use an administrator's Application Password. |
| "This application password is not on the MCP allowlist." | Settings › MCP Server has an allowlist and this password's name is not on it. | Add the name to the allowlist, or use a listed password. |
| "The Promptor MCP server is disabled. Enable it under Promptor → Settings → MCP Server." | The server is switched off (the default). | Turn it on in Settings › MCP Server. |
| "The Promptor MCP server is a Pro feature." | The site runs the free edition. | See Free vs Pro. |
| "Rate limit exceeded: at most 60 calls per minute per user." | The client called more than 60 tools in a minute. | Wait a minute. |
| "Unknown tool: …" | The tool name is wrong, or the tool is switched off in Settings › MCP Server. | Turn the tool on, then reconnect the client so it reloads the tool list. |
| "API Key is not set." | Knowledge search needs an OpenAI API key for the search embedding. | Add your key in Settings › AI Behavior. |
| "Unknown knowledge base: …" | The client asked for a knowledge base key that does not exist. | Ask the client to list knowledge bases first. |
For developers: HTTP status codes
Failed chat requests return an HTTP status you can see in the browser's network tab:
| Status | Meaning |
|---|
| 400 | Invalid or empty input |
| 403 | Security token failed, or a trial error |
| 429 | Visitor rate limit, the free edition's monthly allowance, or a usage limit pause |
| 500 | Configuration or save error |
| 502 | The AI provider failed or could not be reached |
See AJAX endpoints, REST routes and data storage.
Still stuck?
Include the exact message, your Promptor, WordPress and PHP versions, and your caching plugin. Never send your API key.