Troubleshoot the Connector

The request is incomplete or did not come from the Connector: information is missing or invalid, or the application name exceeds 80 characters or contains control characters. The page is titled The connection can't be started and does not redirect anywhere. Restart the connection in the application.

Neither a Space nor the option for future Spaces is checked, and Connect is disabled. The sentence appears below the buttons. Check at least one Space or the option. A Space is a shared workspace in the app.

The consent page has expired or has already been submitted; the message is It has expired or has already been used. Restart the connection in your app. This can also happen after signing out, changing accounts or a change in Space membership. No connection was created. Start connecting again in the application and confirm within 10 minutes.

The return from TEISENDA could not be completed; any existing connection stays unchanged.

• After more than 10 minutes: Start connecting again in the application.
• After changing browsers or losing the cookie: Start again, stay in the same browser profile and allow cookies for mcp.teisenda.com.
• After a late or repeated return: Check whether the application is already connected, and start again if it is not.
• For a mismatched application name or return host: Start again and contact support if it happens again.
• If the TEISENDA app is unreachable: Try again in a few minutes.

Your account is scheduled for deletion, and such an account cannot connect anything. The page may show the same message as for an incorrect password (Incorrect email or password.). First restore the account using the link in the email sent when deletion was scheduled. Restart the connection in the application.

The email address or password is incorrect; the message does not say which. Check both fields.

There have been more sign-in attempts than allowed. The message gives the minutes until the waiting period ends; if no number is given, it is 15. Wait that long, then sign in again. If the 10-minute sign-in period has elapsed, restart the connection in the application.

Sign-in failed for another reason. Try again.

The second-factor code is incorrect or expired. Enter the code your authenticator app currently shows.

There have been too many incorrect codes. The message gives the minutes until the waiting period ends; if no number is given, it is 10. Wait that long, then enter a current code. If sign-in has expired by then, restart the connection in the application.

The Connector only allows sign-in to return to Claude and ChatGPT's fixed addresses or to your own computer, as required by Claude Code. It rejects any other application. Use Claude, Claude Code or ChatGPT.

The application's authentication is no longer valid and cannot be renewed. This includes “The connection no longer exists.” and “The refresh token has already been used.” Connect the application again and choose its Spaces on the consent page.

The call reached the app, but the connection has ended in TEISENDA or the account is scheduled for deletion. The Connector may continue forwarding such calls for up to one minute before removing authentication. The solution depends on the cause:

• The connection has ended: reconnect in the application; an ended connection cannot be reopened. TEISENDA has no button for this; a connection can only be started in the application.
• The account is scheduled for deletion: first restore it using the link in the email sent when deletion was scheduled. This does not end the connection, but the Connector deletes the application's authentication once it learns that the account is inactive. You must then reconnect in the application in this case too.

The call has authentication without a user or connection. Reconnect in the application.

The app does not know the call's account, for example because it was permanently deleted while the Connector still held its authentication. Reconnect in the application with an existing account.

The call does not name a Space, or the argument space does not contain ten digits; the app does not distinguish these cases. Tell the application which Space you mean; whoami lists the connection's Spaces.

The Space was never checked, you later deselected it, you are no longer a member, or the Space ID is incorrect; the app does not say which reason applies.

Check the Space ID with whoami and add the Space to the connection, as explained in Manage connections. If you are no longer a member, you first need a new invitation to the Space.

The Connector treats the Space as locked for one of three reasons, which the message does not distinguish:

• The Space is not confirmed yet: use the link in the confirmation email.
• The Space is scheduled for deletion: only the member with the Owner role who deleted it can undo deletion while the deadline is running, using the link in the email they received when deleting it. TEISENDA cannot resend the link (Delete a Space).
• TEISENDA locked the Space: contact support; you cannot remove this lock as a user.

After a lock ends, the Connector may still treat the Space as locked for up to one minute. See No tool works in a locked Space.

No unlocked Space in the connection has this tool's product. Every Space has Hosting, so this message means the connection covers no Spaces or only locked ones. Add a Space to the connection, as explained in Manage connections.

Your role in this Space does not allow the tool. With Read-only, you can only call the five tools that require viewing permission (Your role in the Space determines which tools you can call). Ask a member with the Owner or Administrator role for User or higher.

This tool does not exist: the Connector rejects names that do not match the form <Produkt>_<Name> or exceed 64 characters, and the app rejects names it does not know. Have the application read the tool list again. According to OpenAI's guide, in ChatGPT this is “Refresh” on the connection; the German interface calls it “Tools aktualisieren” (Update or remove the Connector in ChatGPT).

An argument is missing or has the wrong form; the sentence names it. Check the tool's parameters and their limits. Have the application repeat the call with the corrected argument.

The tool aborted with an unexpected error; it is unclear whether anything has already changed. First check the current state, for example with hosting_project_status, then try again.

This sentence has two possible causes:

• The Connector did not receive a usable response from the app; whoami then returns the last known connection state and says it is outdated. Try again a few minutes later.
• A tool call took longer than two minutes; the Connector stopped waiting and the result was lost. The work may still have completed, and any changes remain. Check the current state, for example with hosting_project_status or hosting_list_deploys, rather than repeating the call blindly.

The application's request exceeds 8 MB, and TEISENDA rejects it. Send less per call; for a whole website, use hosting_create_upload.

Too many requests arrived in a short time, and TEISENDA rejects them. The values are listed under These limits apply to each call. Try again a moment later.

The app returned a result the Connector could not read. Try again. If it keeps happening, contact support.

The Space has used its plan's publications; Free allows three in total. TEISENDA rejects hosting_put_files, hosting_create_upload and hosting_deploy without a version number; there was no upload and no version was created. Republishing a previously published version does not count and remains possible with hosting_rollback or with hosting_deploy and its number. The Max plan allows more publications; see Plans.

The application called hosting_deploy with the number of a ready version, one that has never been published, and the Space has used its plan's publications. The version remains ready but is not published. The solution is the same as above.

The Space's plan does not allow another project; hosting_create_project created nothing. Delete a project. The Max plan allows more projects; see Plans.

A Space can have as many custom domains as its plan allows projects; hosting_add_domain changed nothing. Remove a domain. The Max plan allows more projects and therefore more custom domains; see Plans.

The Space's storage is full; TEISENDA already accounts for what another completed version would free and rejects hosting_put_files, hosting_create_upload and hosting_deploy before anything is uploaded. Delete versions or backups in TEISENDA (Versions). The Max plan provides more storage; see Plans. The upload address from hosting_create_upload gives under max_bytes the largest archive that still fits.

The completed version exceeds the plan's per-version size limit. Its actual size is only known after the hosting node extracts it, so TEISENDA only discards it at completion, in hosting_deploy or hosting_deploy_status. Older versions remain unchanged. Make the website smaller; Max has no separate per-version plan limit.

The completed version contains more files than the plan allows per version; TEISENDA discarded it, and older versions remain unchanged. Reduce the file count. Max has no separate per-version plan limit.

With the completed version, the Space would exceed its plan's storage limit; TEISENDA discarded it, and older versions remain unchanged. Delete versions or backups in TEISENDA. Max provides more storage; see Plans.

The argument project is missing or is not a project number. hosting_list_projects shows the numbers.

There is no project with this number in the named Space. Check the number with hosting_list_projects and check whether it is the Space you intended.

A project name is missing or empty in hosting_create_project or hosting_rename_project. Give a name with 1 to 80 characters.

A project name exceeds 80 characters. Give a name with 1 to 80 characters.

A project name contains control characters. Give a name without control characters.

The project has no version with the number from the argument deploy, for example because it was deleted when newer versions were completed. hosting_list_deploys shows the project's versions. In the app, mark a completed version you want to retain as a backup.

This is not a rejection: hosting_rollback or hosting_deploy received the number of the version that is already published. The tool says so and changes nothing. To go back, give another version.

The project has no draft from which to delete files or publish. First write files with hosting_put_files.

The project has no version at all yet; the message comes from hosting_deploy_status without a number. First write files with hosting_put_files.

The application called hosting_rollback for a version that has never been published. Publishing it would count as a publication towards the plan limit. Use hosting_deploy with this version's number.

The application called hosting_deploy with the number of an incomplete version; for the websites available today, that is the draft. With a number, the tool only publishes and does not complete anything. For the draft, have the application call hosting_deploy without a number. The hosting node completes a version uploaded in the app interface itself; hosting_deploy_status shows when.

The version is complete and cannot be changed anymore. Check the state with hosting_deploy_status. hosting_put_files creates a new draft if the project has none.

The version has no index.html in its root folder, so it cannot be completed or published. A new draft starts empty and does not take files from the published version. Add an index.html in the root folder and publish again.

The hosting node will not create another version because it already holds 20 versions of this project. It counts every version in every state, including versions deleted in TEISENDA but not yet removed from the node.

If you recently deleted versions, wait a few minutes and try again; the app retries pending deletions about every five minutes. Otherwise, delete an older version in the app (Versions). No Connector tool deletes a specific individual version.

A file path violates the path rules. hosting_put_files then writes nothing; hosting_delete_files may already have deleted the files listed before it. Correct the path and, after deleting, use hosting_list_files to check what remains.

The contents of a file with the encoding base64 are not valid Base64. Send the file again with valid contents.

A call to hosting_put_files contains more than 3 MB of files. Split the files across several calls or upload an archive with hosting_create_upload.

The file exceeds 200 KB, and hosting_read_file cannot read it. A file of this size cannot be read through the Connector.

An individual file exceeds 25 MB. Make the file smaller.

The whole version exceeds 300 MB. Make the website smaller.

The version contains more than 5,000 files. Reduce the file count.

The version has no file at this path; the message comes from hosting_read_file. hosting_list_files shows the paths.

The offset passed to hosting_list_files is beyond the end of the list. Start again at offset 0 or continue with next_offset from the previous response.

The offset passed to hosting_read_file is beyond the end of the file. Start again at offset 0 or continue with next_offset from the previous response.

The project is offline, so the hosting node does not provide an upload address. The same message applies to every project in a Space TEISENDA paused after a subscription ended, even if the project itself is not switched offline. Bring the project online again with hosting_set_offline. For paused Spaces, see Hosting limits.

This is not a rejection: hosting_delete_project deleted the project in TEISENDA, but the hosting node has not confirmed deletion; the data contains removed_at_node with the value false. The website may still respond briefly. You do not need to do anything: the app retries deletion on the node about every five minutes.

The hosting node is not responding. Try again later.

The hosting node rejected the request without its own error sentence. After an unusable archive or an upload that arrived too late, have the application call hosting_create_upload again: the version stays open and you receive a new address. Otherwise check the state with hosting_project_status; if it keeps happening, contact support.

The project has not yet been transferred to the hosting node and cannot accept files. Query hosting_project_status and try again once the node has the settings.

This is not a rejection: the change is saved in TEISENDA, but the hosting node does not have it yet. The reason follows the sentence, and the data contains node_has_settings with the value false. The app transfers the state later automatically; check with hosting_project_status.

The hostname is invalid: it must be at most 253 characters, cannot be an IP address and must not include https:// or a path. The app converts it to lowercase itself. Give the bare hostname, for example www.example.com.

The hostname is in a zone no project may use: teisenda.com or teisendapages.com. Use a custom domain.

The hostname is in the zone used for TEISENDA addresses assigned by TEISENDA itself: teisendahosting.com. Use a custom domain.

The domain already points to a project: this one, another project in this or another Space, or a project known to the hosting node. A hostname can belong to only one project across all Spaces. First remove it from the other project with hosting_remove_domain or use another hostname.

The project already has 19 custom domains. The hosting node holds at most 20 hostnames per project, including the automatically assigned TEISENDA address. Remove a domain first.

The domain does not belong to this project. hosting_project_status lists the project's domains.

The application tried to use hosting_set_primary_domain to make a domain primary before it was active. Complete DNS setup and have the application call hosting_check_domain until the domain is active.

This is not a rejection: hosting_check_domain found that the domain's DNS is not correct yet. The sentence is followed by one line per problem and Set either the CNAME record or the A record, plus the TXT record as proof of ownership. The lines are listed in the next section. Set the DNS records at your DNS provider and have the application call hosting_check_domain again.

The list from hosting_set_redirects was not saved. Each invalid rule gets a line “Rule …: …” with the reason. Check source, destination, wildcards and status as well as loops and the 200-rule limit. Correct the listed rules and resend the complete list.

The domain name does not point anywhere: the hosting node finds neither an A nor an AAAA record. Set the CNAME or A record given in the result.

The domain has an AAAA record but no A record. Set the A record to the value given in the result, or use the CNAME record instead.

Alongside the A record pointing to the hosting node, the domain has another pointing elsewhere. Remove the other A record at your DNS provider.

The domain has A records, but none is the hosting node's address: it points to another server. Replace the existing CNAME or A record with the one given in the result.

The domain has an AAAA record that is not the hosting node's IPv6 address; the certificate authority prefers IPv6 and fails with such a record. Remove this AAAA record, or set it to the value in the result if one is given.

A CAA record for the domain or a parent name permits certificates only from certificate authorities other than Let’s Encrypt, which the hosting node uses. Change or remove the CAA record at your DNS provider so it allows letsencrypt.org.

Proof of ownership is missing: the domain does not have a CNAME pointing to an address of the same project under teisendahosting.com, and the TXT record _teisenda-hosting.<Domain> does not contain the expected value. Set the TXT record with the name and value given in the result.

The DNS servers queried by the hosting node did not respond for the domain, so DNS could not be checked. Check with your DNS provider whether the domain resolves and have the application call hosting_check_domain again.

The hosting node queries two public DNS servers. One already sees the records as correct, while the other does not; this line then appears alone. Wait a few minutes and have the application call hosting_check_domain again.

An attempt to activate the domain found DNS incorrect at that moment, so the hosting node did not request a certificate. Correct DNS and have the application call hosting_check_domain again.

Certificate issuance failed, for any reason; the domain then has the state failed, and the tools' state and certificate data contain this untranslated value. Check DNS records, especially any CAA record, and have the application call hosting_check_domain again; the tool starts a new attempt once DNS is correct. If it keeps happening, contact support.

The hosting node reports something the app has no specific sentence for, such as a node restart interrupting certificate issuance. Have the application call hosting_check_domain again.