Tugboat Error Codes

This table is a reference of various error codes and messages you may encounter, and what they can mean.

Error Code Message Details
404 Not Found If you receive a 404 when using Tugboat, that can mean you are accessing something that has been deleted, or that you aren’t authenticated. Double check the URI, try re-authenticating, or when using the API, double check your Tugboat Access Token.
1000 Permission Denied
1002 No API Key ID Provided
1004 No Project ID Provided
1006 No Repository ID Provided
1008 No Configuration Field Provided
1013 Invalid Configuration
1015 No Preview ID Provided
1017 No Service ID Provided
1020 No ID Provided
1021 Repository is Over Quota This occurs if a quota is present on a repository (uncommon) and has been exceeded. Rebuild any orphaned or stale previews, or delete some previews to free up some disk space.
1022 Project is Over Quota This occurs if your quota has been exceeded. Rebuild any orphaned or stale previews, or delete some previews to free up some disk space. If it persists, consider upgrading to a higher tier.
1025 Image Not Found This occurs if Tugboat is unable to pull the Docker image or tag you’ve specified in your config.yml. Double check your config and Rebuild your preview.
1027 No Message ID Provided When using some Mail Message endpoints of our API, this error will occur if you’ve omitted the Message ID in the request.
1031 Unknown API Key When using some API Keys endpoints of our API, this error will occur if you’ve used an invalid API Key.
1032 Unknown Project This error will occur if you’ve passed an invalid Project ID or a Project ID that you do not have access to in an API request or CLI command. Double check that the ID is correct and that you have access to it with the access token provided.
1033 Unknown Repository This error will occur if you’ve passed an invalid Repository ID or a Repository ID that you do not have access to in an API request or CLI command. Double check that the ID is correct and that you have access to it with the access token provided.
1034 Unknown Mail Message This error will occur if you’ve passed an invalid Mail Message ID or a Mail Message ID that you do not have access to in an API request or CLI command. Double check that the ID is correct and that you have access to it with the access token provided.
1035 Cannot stop preview
1036 Cannot start preview
1037 Cannot suspend preview
1038 Cannot refresh preview
1039 Unknown Preview This error will occur if you’ve passed an invalid Preview ID or a Preview ID that you do not have access to in an API request or CLI command. Double check that the ID is correct and that you have access to it with the access token provided.
1040 Cannot reset preview
1041 Cannot delete preview
1043 Cannot create preview
1044 Unknown Service This error will occur if you’ve passed an invalid Service ID or a Service ID that you do not have access to in an API request or CLI command. Double check that the ID is correct and that you have access to it with the access token provided.
1045 Unknown Agent
1046 Cannot rebuild preview
1047 Repository is not authenticated
1048 Cannot cancel preview
1049 Provider authentication failed
1051 Command not found
1052 Preview not in the same repo as base preview
1053 Insufficient provider access
1054 Failed to create provider webhook
1055 Cannot start Tugboat SHell
1056 Invalid Preview configuration
1058 Unsupported Image
1059 No Parent ID Provided
1060 No Integration Type Provided
1061 Unknown Integration Type
1062 Unknown Integration
1063 Unknown Registry
1064 Command Failed If a command in your config.yml has failed or exited with a non-zero exit code, Tugboat will return Command Failed (Tugboat Error 1064): Exit code (n). The n number inside of the parenthesis will be the exit code from the failed command. Read the logs to determine what the failed command is, and use the Terminal to try the command yourself to see if additional output is available.
1067 Cannot create screenshot
1069 Missing argument
1070 Provider not configured
1071 No Agent Provided
1072 No Job ID Provided
1073 Unknown ref Error 1073 will occur when attempting to build a Preview for a git ref that Tugboat cannot find. Double check your command, and reach out to Tugboat Support if the problem persists.
1074 Repo configuration does not allow building of pull requests from forks
1078 Agent Offline
1079 Unknown Provider
1080 No Ref Provided
1081 Tugboat YAML Config Not Found If you encounter error 1081, it may mean the branch or ref you are building does not have a .tugboat/config.yml file.
1082 Cannot reset service
1083 Invalid ref type
1085 Timeout
1086 Service does not have an exposed port
1087 Invalid screen size
1088 Unknown Screenshot
1089 Screenshot Error
1092 Unknown Visual Diff
1093 Visual Diff Error
1094 Unknown Service Alias
1095 No search string provided
1096 Cannot migrate preview
1097 Preview Mail is Over Quota
1098 There was a problem reading the private key
1101 Invalid event type
1102 No Provider Name Provided
1103 Failed to acquire lock
1104 Timeout waiting for lock
1105 Failed to release lock
1106 Unknown Job
1107 Invalid Agent
1109 Server Offline
1110 Agent still in use
1111 Failed to renew lock
1112 Invalid Job Type
1113 Cannot cancel job
1114 Invalid Job Result
1115 Invalid SSH Key Type
1116 Invalid SSH Key Bit Length
1117 Invalid Anchor Type
1118 Invalid Subnet
1119 Invalid IP Address
1120 Provider API Error
1121 Invalid Expiration Date
1122 Unknown Lighthouse Report
1123 Cannot generate Lighthouse Report
1124 No Lighthouse Report ID provided
1125 Lighthouse support not enabled for this Project
1126 Cannot rebuild Lighthouse Report
1127 No Screenshot ID provided
1128 Invalid waitUntil value
1129 Visual Diffs are not enabled for this Project
1130 No Visual Diff ID provided
1131 No Base Screenshot ID provided
1132 Failed to download service image
1133 Invalid Threshold Value
1134 No Registry ID Provided
1135 No username provided
1136 No password provided
2000 Internal Error While rare, the Internal Error (Tugboat Error 2000) error messages can be caused by any number of reasons. This is because it acts as a sort of default “something unexpected happened” error. If you encounter this error, try your action again. If the problem persists, please contact Tugboat Support.