Caido

In-app Issues ​

Proxying Doesn't Work ​

If you are unable to proxy traffic, tamper rules may be the cause.

Disable any Match & Replace rules, network configuration settings, and ensure your proxy settings are configured correctly.

Match & Replace Rule Not Working ​

If a Match & Replace rule is not working or is not being applied, the formatting may be incorrect.

Ensure you are viewing and working with the raw representation of data.

No Responses to Automate Requests ​

If Automate requests are not receiving responses, unexpected input/output errors may be the cause.

Select the Settings tab of the Automate interface and set the value of Max retries to 1+.

Can't Preview Responses ​

This error may occur when Caido is running as root.

text
Rendering error: LaunchIo(Custom { kind: UnexpectedEof, error: "unexpected end of stream" }, BrowserStderr("[0101/110718.156035:ERROR:zygote_host_impl_linux.cc(90)] Running as root without --no-sandbox is not supported. See https://crbug.com/638180.\n"))

If you encounter this error message after attempting to preview a response, do not run Caido as the root user or launch Caido without the --no-renderer-sandbox command-line option.

Looping Requests ​

If a steady stream of requests are being sent to api.caido.io and/or gstatic.com, network configuration settings may be the cause.

Disable your VPN and check your browser, upstream, SOCKS, and invisible proxy settings.

Unable to Access Individual/Team Tier Subscription Features ​

This error may occur when the cached state of your account has not been updated.

If you are unable access premium subscription features, refresh your account state by reauthenticating to your Caido instance.

"You don't have the required permissions for this action." ​

This error may occur when you have exceeded the installation limits of workflows, plugins, or filters for your account type.

If you encounter this error message after attempting to install an extension, remove extensions that are unused or less important to your current work, and then retry the installation.

The GraphQL Playground Doesn't Work ​

This error may occur when unauthenticated requests are being sent to the GraphQL server.

If you are unable to make GraphQL API calls, access the GraphQL Playground in your browser by navigating to http://127.0.0.1:8080/graphql, click on the Headers tab, and add an Authorization header.

json
{
  "Authorization": "Bearer ACCESS_TOKEN_HERE"
}

To acquire your token, open the browser's DevTools interface, select the Application tab, and copy the value of the accessToken in the CAIDO_AUTHENTICATION object within local storage.

A Section of the User Interface is Missing ​

If you are unable to view a section of the user-interface, it may have been minimized.

Ensure the section pane wasn't resized inadvertently.

Shell Node Timeouts ​

This error may occur when workflows include a shell node.

text
"Error in $shell node: Failed to execute shell: Timeout"

By default, the initialization script sources from bashrc or zshrc, which may contain slow operations or hanging commands. Clear the init script field in the shell node configuration, or replace it with a minimal script that doesn't source shell configuration files.