error-insights

{ "twilioErrorCode":[ { "id": 1, "code": 400, "message": "Bad Request", "log_level": "ERROR", "secondary_message": null, "log_type": "APPLICATION", "docs": "## ERROR - 400\r\n\r\n### Bad Request\r\n\r\n Failed to complete request due to a bad request\r\n\r\n#### Possible Causes\r\n* The resource to be modified has moved into a state that is no longer valid.\r\n* Input on the request did not pass validation.\r\n\r\n#### Possible Solutions\r\n* Retry the request after confirming the request is valid.\r\n* Verify if the resource to be modified exists and is in a valid state.", "causes": "* The resource to be modified has moved into a state that is no longer valid.\r\n* Input on the request did not pass validation.", "solutions": "* Retry the request after confirming the request is valid.\r\n* Verify if the resource to be modified exists and is in a valid state.", "description": "Failed to complete request due to a bad request", "product": null, "date_created": "2020-09-14T21:49:18Z", "last_updated": "2025-02-07T18:55:03.917622Z" }, { "id": 2, "code": 403, "message": "Forbidden", "log_level": "ERROR", "secondary_message": null, "log_type": "APPLICATION", "docs": "## ERROR - 403\r\n\r\n### Forbidden\r\n\r\n The request is not authorized\r\n\r\n#### Possible Causes\r\nIncorrect credentials\r\n\r\n#### Possible Solutions\r\nVerify credentials", "causes": "Incorrect credentials", "solutions": "Verify credentials", "description": "The request is not authorized", "product": null, "date_created": "2023-05-02T17:53:30Z", "last_updated": "2023-05-02T18:03:44.513592Z" }, { "id": 3, "code": 404, "message": "Not Found", "log_level": "ERROR", "secondary_message": null, "log_type": "APPLICATION", "docs": "## ERROR - 404\r\n\r\n### Not Found\r\n\r\n Failed to find a match for the request\r\n\r\n#### Possible Causes\r\n* The specified resource is no longer available.\r\n\r\n\r\n#### Possible Solutions\r\n* Check that the specified resource still exists.\r\n", "causes": "* The specified resource is no longer available.\r\n", "solutions": "* Check that the specified resource still exists.\r\n", "description": "Failed to find a match for the request", "product": null, "date_created": "2020-09-14T21:50:07Z", "last_updated": "2020-09-14T21:50:07Z" }, { "id": 4, "code": 410, "message": "Unknown Error Code", "log_level": "ERROR", "secondary_message": null, "log_type": "APPLICATION", "docs": "## ERROR - 410\r\n\r\n### Unknown Error Code\r\n\r\n Access to this resource is no longer available and should not be retried.\r\n\r\n\r\n#### Possible Causes\r\n* The resource has reached a terminal state and is no longer available.\r\n\r\n\r\n#### Possible Solutions\r\n* Do not retry the request since the condition is likely permanent.\r\n", "causes": "* The resource has reached a terminal state and is no longer available.\r\n", "solutions": "* Do not retry the request since the condition is likely permanent.\r\n", "description": "Access to this resource is no longer available and should not be retried.\r\n", "product": null, "date_created": "2020-09-14T21:50:57Z", "last_updated": "2020-09-14T21:51:24Z" }, { "id": 5, "code": 503, "message": "Internal Error", "log_level": "ERROR", "secondary_message": null, "log_type": "TWILIO", "docs": "## ERROR - 503\r\n\r\n### Internal Error\r\n\r\n An internal error has occurred while processing the request.\r\n\r\n\r\n#### Possible Causes\r\n* The server is currently unable to handle the request.\r\n\r\n\r\n#### Possible Solutions\r\n* Retry the request at a later time.", "causes": "* The server is currently unable to handle the request.\r\n", "solutions": "* Retry the request at a later time.", "description": " An internal error has occurred while processing the request.\r\n", "product": null, "date_created": "2020-09-14T21:55:34Z", "last_updated": "2020-09-14T21:55:34Z" }, { "id": 6, "code": 10001, "message": "Account is not active", "log_level": "ERROR", "secondary_message": "This account has been disabled and may not be used until it is reactived.", "log_type": "TWILIO", "docs": "## ERROR - 10001\r\n\r\n### Account is not active\r\n\r\nThis account has been disabled and may not be used until it is reactived. This account has been disabled and may not be used until it is reactivated.\r\n\r\n#### Possible Causes\r\n* Lack of funds\r\n* Violation of the Terms of Service or Acceptable Use Policy\r\n\r\n#### Possible Solutions\r\n* Check your account balance. Refill funds if necessary.\t\r\n* Please reach out to Twilio Support through the [Console](https://console.twilio.com) or [Help Center](https://support.twilio.com).", "causes": "* Lack of funds\r\n* Violation of the Terms of Service or Acceptable Use Policy", "solutions": "* Check your account balance. Refill funds if necessary.\t\r\n* Please reach out to Twilio Support through the [Console](https://console.twilio.com) or [Help Center](https://support.twilio.com).", "description": "This account has been disabled and may not be used until it is reactivated.", "product": null, "date_created": "2016-03-31T17:13:21Z", "last_updated": "2023-11-01T04:47:50.904317Z" }, { "id": 7, "code": 10002, "message": "Trial accounts do not support the feature you tried to use", "log_level": "ERROR", "secondary_message": "Your account is currently in trial mode and therefore does not have access to the premium feature you attempted to use.", "log_type": "APPLICATION", "docs": "## ERROR - 10002\r\n\r\n### Trial accounts do not support the feature you tried to use\r\n\r\nYour account is currently in trial mode and therefore does not have access to the premium feature you attempted to use. Premium features are limited to full accounts, so you must upgrade your account if you wish to use them.\r\n\r\nFor guidance on updating your account, please see [How to Work with your Free Twilio Trial Account](/docs/usage/tutorials/how-to-use-your-free-trial-account#how-to-upgrade-your-account). \r\n\r\n\r\n#### Possible Causes\r\nYou attempted to use a premium feature with a trial account.\r\n\r\n#### Possible Solutions\r\nUpgrade to a full account and try the feature again.", "causes": "You attempted to use a premium feature with a trial account.", "solutions": "Upgrade to a full account and try the feature again.", "description": "Premium features are limited to full accounts, so you must upgrade your account if you wish to use them.\r\n\r\nFor guidance on updating your account, please see [How to Work with your Free Twilio Trial Account](/docs/usage/tutorials/how-to-use-your-free-trial-account#how-to-upgrade-your-account). \r\n", "product": "Phone Numbers", "date_created": "2016-03-31T17:13:22Z", "last_updated": "2024-03-11T18:04:37.073973Z" }, { "id": 8, "code": 10003, "message": "Incoming call rejected due to inactive account", "log_level": "ERROR", "secondary_message": "An incoming call was made to your application, but was not answered because your account was not active at the time.", "log_type": "APPLICATION", "docs": "## ERROR - 10003\r\n\r\n### Incoming call rejected due to inactive account\r\n\r\nAn incoming call was made to your application, but was not answered because your account was not active at the time. \r\n\r\n#### Possible Causes\r\n* Lack of funds\r\n* Violation of the Terms of Service or Acceptable Use Policy\r\n\r\n#### Possible Solutions\r\n* Check your account balance. Refill funds if necessary.\t\r\n* Contact Twilio <a href=\"/help/contact\">customer support</a> to inquire further.", "causes": "* Lack of funds\r\n* Violation of the Terms of Service or Acceptable Use Policy", "solutions": "* Check your account balance. Refill funds if necessary.\t\r\n* Contact Twilio <a href=\"/help/contact\">customer support</a> to inquire further.", "description": null, "product": null, "date_created": "2016-03-31T17:13:22Z", "last_updated": "2023-07-31T21:26:30.972239Z" }, { "id": 9, "code": 10004, "message": "Call concurrency limit exceeded", "log_level": "ERROR", "secondary_message": null, "log_type": "TWILIO", "docs": "## ERROR - 10004\r\n\r\n### Call concurrency limit exceeded\r\n\r\n ## Error - 10004\r\n\r\n### Call concurrency limit exceeded\r\n\r\nThe call was rejected because you reached the maximum limit of concurrent calls available for your account.\r\n\r\n#### Possible Causes\r\nTrial accounts and newly upgraded accounts without an approved Primary Customer Profile have limited concurrent calls.\r\n\r\n#### Possible Solutions\r\n[Upgrade your account](https://www.twilio.com/docs/usage/tutorials/how-to-use-your-free-trial-account-namer#how-to-upgrade-your-account) and [create a Primary Business Profile](https://www.twilio.com/docs/trust-hub/trusthub-rest-api/console-create-a-primary-customer-profile) to remove concurrent call limitations.", "causes": "Trial accounts and newly upgraded accounts without an approved Primary Customer Profile have limited concurrent calls.", "solutions": "[Upgrade your account](https://www.twilio.com/docs/usage/tutorials/how-to-use-your-free-trial-account-namer#how-to-upgrade-your-account) and [create a Primary Business Profile](https://www.twilio.com/docs/trust-hub/trusthub-rest-api/console-create-a-primary-customer-profile) to remove concurrent call limitations.", "description": "## Error - 10004\r\n\r\n### Call concurrency limit exceeded\r\n\r\nThe call was rejected because you reached the maximum limit of concurrent calls available for your account.", "product": null, "date_created": "2018-10-05T04:05:45Z", "last_updated": "2024-03-27T20:52:20.445749Z" }, { "id": 10, "code": 10005, "message": "Voice calling has been disabled for this account", "log_level": "ERROR", "secondary_message": null, "log_type": "APPLICATION", "docs": "## ERROR - 10005\r\n\r\n### Voice calling has been disabled for this account\r\n\r\n Voice calling has been disabled for this account. \r\n\r\n#### Possible Causes\r\nYour account may have been flagged for review.\r\n\r\n#### Possible Solutions\r\nPlease reach out to Support for assistance. ", "causes": "Your account may have been flagged for review.", "solutions": "Please reach out to Support for assistance. ", "description": "Voice calling has been disabled for this account. ", "product": "Programmable Voice", "date_created": "2023-09-05T16:31:53Z", "last_updated": "2023-09-05T16:40:45.727161Z" }, { "id": 11, "code": 11100, "message": "Invalid URL format", "log_level": "ERROR", "secondary_message": "The format of the provided URL is invalid.", "log_type": "APPLICATION", "docs": "## ERROR - 11100\r\n\r\n### Invalid URL format\r\n\r\n The format of the provided URL is invalid.\r\n\r\n\r\n#### Possible Causes\r\n* Bad URL for phone number configuration\r\n* Bad URL passed to outgoing call REST request\r\n* Bad URL in Play or Redirect Verb Body\r\n* Bad URL provided for a verb's action attribute\r\n* No URL provided in Record verb action attribute when modifying a live call\r\n* Unsupported characters in auth portion of URL\r\n\r\n#### Possible Solutions\r\n* Make sure you submit a fully qualified URL including: protocol (http:// or https://), hostname, file path, properly url-encoded query parameters.\r\n* Twilio must be able to reach this URL over the public Internet.", "causes": "* Bad URL for phone number configuration\r\n* Bad URL passed to outgoing call REST request\r\n* Bad URL in Play or Redirect Verb Body\r\n* Bad URL provided for a verb's action attribute\r\n* No URL provided in Record verb action attribute when modifying a live call\r\n* Unsupported characters in auth portion of URL", "solutions": "* Make sure you submit a fully qualified URL including: protocol (http:// or https://), hostname, file path, properly url-encoded query parameters.\r\n* Twilio must be able to reach this URL over the public Internet.", "description": "The format of the provided URL is invalid.\r\n", "product": "Programmable Messaging", "date_created": "2016-03-31T17:13:23Z", "last_updated": "2024-12-18T14:58:52.871136Z" }, { "id": 12, "code": 11200, "message": "HTTP retrieval failure", "log_level": "ERROR", "secondary_message": "Twilio’s servers were unable to fetch a non-error response from the designated URL.", "log_type": "APPLICATION", "docs": "## ERROR - 11200\r\n\r\n### HTTP retrieval failure\r\n\r\nTwilio’s servers were unable to fetch a non-error response from the designated URL. We try to provide specific webhook errors whenever possible, however in this instance we are unable to identify the exact cause of the webhook delivery/response issue. To prevent 11200 errors, ensure that your webhook receiving infrastructure can quickly respond to inbound Twilio requests with a 2xx status code.\r\n\r\n#### Possible Causes\r\n* Web server returned a 4xx or 5xx HTTP response to Twilio\r\n* Network disruptions between Twilio and your web server; these can be within your or Twilio’s infrastructure or wider disruptions to the internet at large.\r\n* Firewalls (network or application level) between Twilio and your infrastructure\r\n* Misconfigured Web Server\r\n* No Content-Type header attached to response\r\n* Content-Type doesn't match actual content, e.g. an MP3 file that is being served with Content-Type: audio/x-wav, instead of Content-Type: audio/mpeg\r\n\r\n\r\n#### Possible Solutions\r\n* Double check that your TwiML URL does not return a 4xx or 5xx error\r\n* Make certain that the URL does not perform a 302 redirect to an invalid URL\r\n* Confirm the URL requested is not protected by HTTP Auth\r\n* Make sure your web server allows HTTP POST requests to static resources (if the URL refers to .xml or .html files)\r\n* Verify your web server is up and responsive\r\n* Check to see that the URL host is not a private or local IP address\r\n* Verify the ping times and packet loss between your web server and api.twilio.com\r\n* Review firewall rules; modern web application firewalls can trigger on only a small subset of inbound connections leading to inconsistent behavior.\r\n* Check logs at the very edge of your infrastructure to verify if TCP connection attempts are arriving at your edge. If you have confirmed these requests are not reaching your infrastructure, please reach out to [support](https://www.twilio.com/console/support/tickets/create).\r\n* Use more robust options for webhook receipt. For inbound messages and calls be sure to provide a fallback URL (ideally on separate infrastructure). Transition integrations to [Event Streams](https://www.twilio.com/docs/events) which has various event sink types including webhooks with built in retries.\r\n* Review your use of any [webhook connection overrides](https://www.twilio.com/docs/usage/webhooks/webhooks-connection-overrides). In general the defaults provide the best results, start by reconfiguring your webhook URL without any fragment overrides and see if the problem persists.\r\n* If synchronously processing a webhook requires significant time, we recommend that you simply acknowledge the event by quickly responding with an empty 202 (Accepted) and then processing the message on your own timeline. Replies to inbound message events can be done at any time by making a call to the REST API.\r\n", "causes": "* Web server returned a 4xx or 5xx HTTP response to Twilio\r\n* Network disruptions between Twilio and your web server; these can be within your or Twilio’s infrastructure or wider disruptions to the internet at large.\r\n* Firewalls (network or application level) between Twilio and your infrastructure\r\n* Misconfigured Web Server\r\n* No Content-Type header attached to response\r\n* Content-Type doesn't match actual content, e.g. an MP3 file that is being served with Content-Type: audio/x-wav, instead of Content-Type: audio/mpeg\r\n", "solutions": "* Double check that your TwiML URL does not return a 4xx or 5xx error\r\n* Make certain that the URL does not perform a 302 redirect to an invalid URL\r\n* Confirm the URL requested is not protected by HTTP Auth\r\n* Make sure your web server allows HTTP POST requests to static resources (if the URL refers to .xml or .html files)\r\n* Verify your web server is up and responsive\r\n* Check to see that the URL host is not a private or local IP address\r\n* Verify the ping times and packet loss between your web server and api.twilio.com\r\n* Review firewall rules; modern web application firewalls can trigger on only a small subset of inbound connections leading to inconsistent behavior.\r\n* Check logs at the very edge of your infrastructure to verify if TCP connection attempts are arriving at your edge. If you have confirmed these requests are not reaching your infrastructure, please reach out to [support](https://www.twilio.com/console/support/tickets/create).\r\n* Use more robust options for webhook receipt. For inbound messages and calls be sure to provide a fallback URL (ideally on separate infrastructure). Transition integrations to [Event Streams](https://www.twilio.com/docs/events) which has various event sink types including webhooks with built in retries.\r\n* Review your use of any [webhook connection overrides](https://www.twilio.com/docs/usage/webhooks/webhooks-connection-overrides). In general the defaults provide the best results, start by reconfiguring your webhook URL without any fragment overrides and see if the problem persists.\r\n* If synchronously processing a webhook requires significant time, we recommend that you simply acknowledge the event by quickly responding with an empty 202 (Accepted) and then processing the message on your own timeline. Replies to inbound message events can be done at any time by making a call to the REST API.\r\n", "description": "We try to provide specific webhook errors whenever possible, however in this instance we are unable to identify the exact cause of the webhook delivery/response issue. To prevent 11200 errors, ensure that your webhook receiving infrastructure can quickly respond to inbound Twilio requests with a 2xx status code.", "product": null, "date_created": "2016-03-31T17:13:23Z", "last_updated": "2023-08-23T07:59:41.134484Z" }, { "id": 13, "code": 11201, "message": "TCP connection timed out", "log_level": "ERROR", "secondary_message": "Twilio cannot establish a TCP connection to your web server. The two attempts to connect to your web server were timed out. Each connection attempt has a 5 second timeout.", "log_type": null, "docs": "## Error - 11201\r\n### TCP connection timed out\r\nTwilio cannot establish a TCP connection to your web server. The two attempts to connect to your web server were timed out. Each connection attempt has a 5 second timeout.\r\n\r\n#### Possible Causes\r\n* firewall in your network blocking incoming TCP traffic\r\n* network outage between Twilio and your web server\r\n* invalid host part in the HTTP URL pointing to non-existing host or private IP address\r\n\r\n#### Possible Solutions\r\n* verify firewall configuration in your network or on the web server\r\n* verify network connectivity to your web server\r\n* verify the HTTP URL provided is accessible to the public Internet", "causes": null, "solutions": null, "description": null, "product": null, "date_created": "2018-07-26T20:08:21Z", "last_updated": "2020-08-04T10:00:12.946Z" }, { "id": 14, "code": 11202, "message": "TCP connection refused", "log_level": "ERROR", "secondary_message": "Twilio cannot establish a TCP connection to your web server. Your web server rejected our two connection attempts.", "log_type": null, "docs": "## Error - 11202\r\n### TCP connection refused\r\nTwilio cannot establish a TCP connection to your web server. Your web server rejected our two connection attempts.\r\n\r\n#### Possible Causes\r\n* invalid port number in the HTTP URL\r\n* your web server process is down so no process is listening on the port\r\n* your web server is in a degraded state and is not accepting new connections (e.g., overloaded)\r\n\r\n#### Possible Solutions\r\n* verify the HTTP URL provided has the correct host and port number of your web server\r\n* verify your web server is running and listening on the correct port\r\n* verify your web server is properly provisioned to handle all requests", "causes": null, "solutions": null, "description": null, "product": null, "date_created": "2018-07-26T20:08:56Z", "last_updated": "2020-08-04T10:00:12.927Z" }, { "id": 15, "code": 11203, "message": "HTTP communication total time out triggered", "log_level": "ERROR", "secondary_message": "All attempts to communicate with your web server were timed out.", "log_type": null, "docs": "## Error - 11203\r\n\r\n### HTTP communication total time out triggered\r\nAll attempts to communicate with your web server were timed out. You set the total timeout using the tt parameter in the URL fragment identifier.\r\n\r\n#### Possible Solutions\r\n* Adjust the 'tt' (total timeout) parameter in the fragment part of the URL, the one after '#'.", "causes": null, "solutions": null, "description": null, "product": null, "date_created": "2019-01-31T00:28:56Z", "last_updated": "2020-08-04T10:00:10.848Z" }, { "id": 16, "code": 11205, "message": "HTTP connection failure", "log_level": "ERROR", "secondary_message": "There was a network failure attempting to connect to this URL", "log_type": "APPLICATION", "docs": "## ERROR - 11205\r\n\r\n### HTTP connection failure\r\n\r\nThere was a network failure attempting to connect to this URL ### HTTP connection failure\r\n\r\nThere was a network failure attempting to connect to this URL. Twilio will try for 10 seconds to establish a TCP connection to your URL (two 5-second attempts). Twilio will wait for a total of 15 seconds to receive an HTTP response. This includes the TCP connection time, so if it took six seconds to establish a TCP connection, your server would have 9 seconds to deliver an HTTP response. If either of those timers expire, we fail the request, fire a notification, and try your fallback URL, if one is specified.\r\n\r\n#### Possible Causes\r\n* Network outages between Twilio and your web server.\r\n* URLs that reference private IP addresses or localhost.\r\n* Twilio’s TCP timeout is 10 seconds. If you see an error in Request Inspector after more than 10000 milliseconds, Twilio could locate your server, but could not establish a TCP connection with it. \r\n* Twilio’s HTTP timeout is 15 seconds. If you see an error in Request Inspector returned after more than 15000 milliseconds, Twilio was able to establish a TCP connection with your server, but the HTTP response from the server failed.\r\n\r\n#### Possible Solutions\r\n* Verify the URL provided is accessible to the public internet.\t\r\n* Verify network connectivity to your web server.\r\n* Check your TCP logs to verify inbound connection attempts are successful.\r\n* Check HTTP server logs to verify a response was generated and returned within the timeout.\r\n* Check your edge element logs to verify responses are making it out of your infrastructure.", "causes": "* Network outages between Twilio and your web server.\r\n* URLs that reference private IP addresses or localhost.\r\n* Twilio’s TCP timeout is 10 seconds. If you see an error in Request Inspector after more than 10000 milliseconds, Twilio could locate your server, but could not establish a TCP connection with it. \r\n* Twilio’s HTTP timeout is 15 seconds. If you see an error in Request Inspector returned after more than 15000 milliseconds, Twilio was able to establish a TCP connection with your server, but the HTTP response from the server failed.", "solutions": "* Verify the URL provided is accessible to the public internet.\t\r\n* Verify network connectivity to your web server.\r\n* Check your TCP logs to verify inbound connection attempts are successful.\r\n* Check HTTP server logs to verify a response was generated and returned within the timeout.\r\n* Check your edge element logs to verify responses are making it out of your infrastructure.", "description": "### HTTP connection failure\r\n\r\nThere was a network failure attempting to connect to this URL. Twilio will try for 10 seconds to establish a TCP connection to your URL (two 5-second attempts). Twilio will wait for a total of 15 seconds to receive an HTTP response. This includes the TCP connection time, so if it took six seconds to establish a TCP connection, your server would have 9 seconds to deliver an HTTP response. If either of those timers expire, we fail the request, fire a notification, and try your fallback URL, if one is specified.", "product": null, "date_created": "2016-03-31T17:13:23Z", "last_updated": "2021-03-19T13:44:11.373Z" }, { "id": 17, "code": 11206, "message": "HTTP protocol violation", "log_level": "ERROR", "secondary_message": "There was an error speaking HTTP to the target URL.", "log_type": "APPLICATION", "docs": "## ERROR - 11206\r\n\r\n### HTTP protocol violation\r\n\r\n There was an error speaking HTTP to the target URL.\r\n\r\n\r\n#### Possible Causes\r\n* Server misconfiguration\r\n* Network disruption\r\n* Making HTTP connections to an HTTPS port\r\n* There is an invalid symbol in the TwiML Cookie\r\n\r\n#### Possible Solutions\r\n* Verify your web server is serving valid HTTP for the URL\t\r\n* Verify the network connection to your server is stable\t\r\n* Verify the URL is not directing you to an SSL port\r\n* Remove the following characters from the TwiML Cookies: ‘\\t’, ‘\\r’, ‘\\n’, ‘\\v’, ‘\\f’\r\n* TwiML cookies cannot have an empty name\r\n", "causes": "* Server misconfiguration\r\n* Network disruption\r\n* Making HTTP connections to an HTTPS port\r\n* There is an invalid symbol in the TwiML Cookie", "solutions": "* Verify your web server is serving valid HTTP for the URL\t\r\n* Verify the network connection to your server is stable\t\r\n* Verify the URL is not directing you to an SSL port\r\n* Remove the following characters from the TwiML Cookies: ‘\\t’, ‘\\r’, ‘\\n’, ‘\\v’, ‘\\f’\r\n* TwiML cookies cannot have an empty name\r\n", "description": "There was an error speaking HTTP to the target URL.\r\n", "product": "Programmable Messaging", "date_created": "2016-03-31T17:13:24Z", "last_updated": "2024-09-09T12:15:18.952199Z" }, { "id": 18, "code": 11210, "message": "HTTP bad host name", "log_level": "ERROR", "secondary_message": null, "log_type": "APPLICATION", "docs": "## ERROR - 11210\r\n\r\n### HTTP bad host name\r\n\r\n The DNS entry for the URL’s host cannot be resolved.\r\n\r\n\r\n#### Possible Causes\r\n* URL references a locally defined hostname (check your `/etc/hosts`)\r\n* URL references an undefined hostname\r\n\r\n#### Possible Solutions\r\n* Verify the hostname of the URL has a valid DNS record the can be resolved by the public", "causes": "* URL references a locally defined hostname (check your `/etc/hosts`)\r\n* URL references an undefined hostname", "solutions": "* Verify the hostname of the URL has a valid DNS record the can be resolved by the public", "description": "The DNS entry for the URL’s host cannot be resolved.\r\n", "product": null, "date_created": "2016-03-31T17:13:24Z", "last_updated": "2021-03-15T09:50:26.671Z" }, { "id": 19, "code": 11215, "message": "HTTP too many redirects", "log_level": "ERROR", "secondary_message": "this request has been redirected too many times and may be in a loop.", "log_type": null, "docs": "## Error - 11215 \n\n### HTTP too many redirects\n\nthis request has been redirected too many times and may be in a loop.\n\n#### Possible Causes \n* Twilio received too many HTTP redirect messages in a row for this request.\n\n\n#### Possible Solutions\n* Make certain your code is not stuck in an infinite loop.\n\n", "causes": null, "solutions": null, "description": null, "product": null, "date_created": "2016-03-31T17:13:25Z", "last_updated": "2020-08-04T10:00:29.462Z" }, { "id": 20, "code": 11216, "message": "HTTP invalid redirect", "log_level": "ERROR", "secondary_message": "The response from your server contained an invalid redirect.", "log_type": "APPLICATION", "docs": "## ERROR - 11216\r\n\r\n### HTTP invalid redirect\r\n\r\nThe response from your server contained an invalid redirect. Twilio sent a webhook to your server and your server responded with a 3xx status code that was not a valid redirect.\r\n\r\n#### Possible Causes\r\n* Your server responded with an non-redirect HTTP status code in the 3xx series. Twilio will only follow redirects for status codes 301, 302, 303, and 307.\r\n* Your server did not include a location header in the redirect response\r\n\r\n#### Possible Solutions\r\n* Update your webhook configuration specifying the final URL you would like to be called, removing the need for redirects.\r\n* Ensure you are using a standard redirect HTTP status code (301, 302, 303, or 307)\r\n* Ensure that you are including a valid url in the location header of your response.", "causes": "* Your server responded with an non-redirect HTTP status code in the 3xx series. Twilio will only follow redirects for status codes 301, 302, 303, and 307.\r\n* Your server did not include a location header in the redirect response", "solutions": "* Update your webhook configuration specifying the final URL you would like to be called, removing the need for redirects.\r\n* Ensure you are using a standard redirect HTTP status code (301, 302, 303, or 307)\r\n* Ensure that you are including a valid url in the location header of your response.", "description": "Twilio sent a webhook to your server and your server responded with a 3xx status code that was not a valid redirect.", "product": null, "date_created": "2023-10-04T07:53:56Z", "last_updated": "2023-10-04T12:43:07.463366Z" }, { "id": 21, "code": 11217, "message": "HTTP error response code", "log_level": "ERROR", "secondary_message": "Your server responded to the webhook request with an error response (4xx or 5xx)", "log_type": "APPLICATION", "docs": "## ERROR - 11217\r\n\r\n### HTTP error response code\r\n\r\nYour server responded to the webhook request with an error response (4xx or 5xx) Twilio sent a webhook to your server and your server responded with a 4xx or 5xx status code.\r\n\r\n#### Possible Causes\r\n* There was an error in your server (500).\r\n* There was a problem between your proxy and your server (502, 503, 504).\r\n* The URL specified in your webhook configuration is incorrect (404, 410).\r\n* Your server is attempting to rate limit Twilio's webhook requests (429). Twilio's webhooks do not support rate limiting.\r\n* Your webhook configuration does not have appropriate permissions to call the configured URL (403).\r\n\r\n#### Possible Solutions\r\n* Review the configured webhook URL to ensure that it is correct.\r\n* Look for and fix errors in your server logs.\r\n* Ensure that you can get 2xx status codes by calling your webhook URL.\r\n* Review your proxy and authentication configurations.\r\n* For rate limiting issues, consider shifting to Event Streams HTTP Sink which [support rate limiting](https://www.twilio.com/docs/events/faq/problems-on-delivery#what-does-throttle-sink-means-for-eventstreams).", "causes": "* There was an error in your server (500).\r\n* There was a problem between your proxy and your server (502, 503, 504).\r\n* The URL specified in your webhook configuration is incorrect (404, 410).\r\n* Your server is attempting to rate limit Twilio's webhook requests (429). Twilio's webhooks do not support rate limiting.\r\n* Your webhook configuration does not have appropriate permissions to call the configured URL (403).", "solutions": "* Review the configured webhook URL to ensure that it is correct.\r\n* Look for and fix errors in your server logs.\r\n* Ensure that you can get 2xx status codes by calling your webhook URL.\r\n* Review your proxy and authentication configurations.\r\n* For rate limiting issues, consider shifting to Event Streams HTTP Sink which [support rate limiting](https://www.twilio.com/docs/events/faq/problems-on-delivery#what-does-throttle-sink-means-for-eventstreams).", "description": "Twilio sent a webhook to your server and your server responded with a 4xx or 5xx status code.", "product": null, "date_created": "2023-10-04T07:56:09Z", "last_updated": "2023-10-04T12:43:28.992151Z" }, { "id": 22, "code": 11220, "message": "SSL/TLS Handshake Error", "log_level": "ERROR", "secondary_message": "During SSL/TLS negotiation, Twilio experienced a connection reset.", "log_type": "APPLICATION", "docs": "## ERROR - 11220\r\n\r\n### SSL/TLS Handshake Error\r\n\r\nDuring SSL/TLS negotiation, Twilio experienced a connection reset. \r\n\r\n#### Possible Causes\r\n* Incompatible cipher suites in use by the client and the server. This would require the client to use (or enable) a cipher suite that is supported by the server.\r\n\r\n#### Possible Solutions\r\n* Verify cipher suites in-use are up to date. Twilio-supported ciphers can be found [here](https://support.twilio.com/hc/en-us/articles/360007724794-Notice-Twilio-REST-API-s-TLS-and-Cipher-Suite-Security-Changes-for-June-2019)\r\n* Use compatible version of TLS, Twilio supports TLS 1.2.", "causes": "* Incompatible cipher suites in use by the client and the server. This would require the client to use (or enable) a cipher suite that is supported by the server.", "solutions": "* Verify cipher suites in-use are up to date. Twilio-supported ciphers can be found [here](https://support.twilio.com/hc/en-us/articles/360007724794-Notice-Twilio-REST-API-s-TLS-and-Cipher-Suite-Security-Changes-for-June-2019)\r\n* Use compatible version of TLS, Twilio supports TLS 1.2.", "description": null, "product": null, "date_created": "2016-03-31T17:13:25Z", "last_updated": "2023-01-25T20:31:40.785868Z" }, { "id": 23, "code": 11235, "message": "Certificate Invalid - Domain Mismatch", "log_level": "ERROR", "secondary_message": "Twilio tried to validate your SSL certificate but your certificate has a domain name that does not match the domain we requested.", "log_type": null, "docs": "## Error - 11235\n\n### Certificate Invalid - Domain Mismatch\n\nTwilio tried to validate your SSL certificate but your certificate has a domain name that does not match the domain we requested.\n\n#### Possible Causes\n* Your Certificate Name or Certificate Alternate Name on your SSL certificate does not match the domain Twilio requested.\n\n\n#### Possible Solutions\n* Obtain a SSL certificate with a Certificate Name or Certificate Alternate Name that matches this domain.\n", "causes": null, "solutions": null, "description": null, "product": null, "date_created": "2016-03-31T17:13:25Z", "last_updated": "2020-08-04T10:00:29.428Z" }, { "id": 24, "code": 11236, "message": "Certificate Invalid - Certificate Expired", "log_level": "ERROR", "secondary_message": "Twilio tried to validate your SSL certificate but your certificate has expired.", "log_type": null, "docs": "## Error - 11236\n\n### Certificate Invalid - Certificate Expired\n\nTwilio tried to validate your SSL certificate but your certificate has expired.\n\n#### Possible Causes\n* Your SSL certificate has expired.\n\n#### Possible Solutions\n* Renew your SSL certificate.\n", "causes": null, "solutions": null, "description": null, "product": null, "date_created": "2016-03-31T17:13:25Z", "last_updated": "2020-08-04T10:00:29.41Z" }, { "id": 25, "code": 11237, "message": "Certificate Invalid - Could not find path to certificate", "log_level": "ERROR", "secondary_message": "Twilio tried to validate your SSL certificate but was unable to find it in our certificate store.", "log_type": null, "docs": "## Error - 11237\r\n\r\n### Certificate Invalid - Could not find path to certificate\r\n\r\nTwilio tried to validate your SSL certificate but was unable to find it in our certificate store.\r\n\r\n#### Possible Causes\r\n* You are using a self signed certificate.\r\n* The certificate authority you are using is not on our list of approved certificate authorities.\r\n* Your certificate chain is incomplete and requires an additional download.\r\n\r\n#### Possible Solutions\r\n* Do not use a self signed certificate.\r\n* Concatenate your certificate chain so that no additional download is required.\r\n* Twilio uses CAs that are approved by Mozilla, you can find the full list [here](https://ccadb-public.secure.force.com/mozilla/IncludedCACertificateReport).\r\n* For testing purposes you can [disable SSL Certificate Validation in Console](https://www.twilio.com/console/project/settings).\r\n", "causes": null, "solutions": null, "description": null, "product": null, "date_created": "2016-03-31T17:13:26Z", "last_updated": "2020-08-04T10:00:29.391Z" }, { "id": 26, "code": 11240, "message": "HTTP connection edge location is invalid", "log_level": "ERROR", "secondary_message": null, "log_type": "APPLICATION", "docs": "## ERROR - 11240\r\n\r\n### HTTP connection edge location is invalid\r\n\r\n There was an error connecting to the URL due to an invalid edge location parameter.\r\n\r\n#### Possible Causes\r\n* The edge location(s) specified in the 'e' parameter of your connection settings are not valid\r\n\r\n#### Possible Solutions\r\n* Correct the 'e' parameter in the fragment part of the URL, the one after '#'.", "causes": "* The edge location(s) specified in the 'e' parameter of your connection settings are not valid", "solutions": "* Correct the 'e' parameter in the fragment part of the URL, the one after '#'.", "description": "There was an error connecting to the URL due to an invalid edge location parameter.", "product": null, "date_created": "2019-02-04T18:34:22Z", "last_updated": "2020-08-04T10:00:10.796Z" }, { "id": 27, "code": 11241, "message": "HTTP connection edge location is not supported", "log_level": "ERROR", "secondary_message": null, "log_type": "APPLICATION", "docs": "## ERROR - 11241\r\n\r\n### HTTP connection edge location is not supported\r\n\r\n There was an error connecting to the URL due to an unsupported edge location parameter.\r\n\r\n#### Possible Causes\r\n* The edge location(s) specified in the 'e' parameter of your connection settings are not currently supported by Twilio.\r\n\r\n#### Possible Solutions\r\n* Correct the 'e' parameter in the fragment part of the URL, the one after '#'.", "causes": "* The edge location(s) specified in the 'e' parameter of your connection settings are not currently supported by Twilio.", "solutions": "* Correct the 'e' parameter in the fragment part of the URL, the one after '#'.", "description": "There was an error connecting to the URL due to an unsupported edge location parameter.", "product": null, "date_created": "2019-02-04T18:35:12Z", "last_updated": "2020-08-04T10:00:10.779Z" }, { "id": 28, "code": 11242, "message": "HTTP connection over Twilio Interconnect is not allowed", "log_level": "ERROR", "secondary_message": "Your account has not been enabled for HTTP connections over Twilio Interconnect.", "log_type": null, "docs": "## Error - 11242\r\n\r\n### HTTP connection over Twilio Interconnect is not allowed\r\n\r\nYour account has not been enabled for HTTP connections over Twilio Interconnect.\r\n\r\n#### Possible Solutions\r\n* Correct the 'r' (region) parameter in the fragment part of the URL, the one after '#'. Remove those with the '-ix' suffix.\r\n* Contact Twilio <a href=\"/help/contact\">customer support</a> to inquire further.\r\n", "causes": null, "solutions": null, "description": null, "product": null, "date_created": "2019-02-04T18:37:33Z", "last_updated": "2020-08-04T10:00:10.762Z" }, { "id": 29, "code": 11243, "message": "HTTP retry policy is invalid", "log_level": "ERROR", "secondary_message": "One or more retry policies specified in the ‘rp’ parameter of your connection settings are invalid.", "log_type": null, "docs": "## Error - 11243\r\n\r\n### HTTP retry policy is invalid\r\nOne or more retry policies specified in the ‘rp’ parameter of your connection settings are invalid.\r\n\r\n#### Possible Solutions\r\n* Correct the 'rp' (retry policy) parameter in the fragment part of the URL, the one after '#'.", "causes": null, "solutions": null, "description": null, "product": null, "date_created": "2019-01-31T00:29:58Z", "last_updated": "2020-08-04T10:00:10.831Z" }, { "id": 30, "code": 11251, "message": "Fatal protocol violation", "log_level": "ERROR", "secondary_message": "There was an HTTP protocol violation speaking to the target URL.", "log_type": null, "docs": null, "causes": null, "solutions": null, "description": null, "product": null, "date_created": "2016-03-31T17:13:26Z", "last_updated": "2020-08-04T10:00:29.373Z" }, { "id": 31, "code": 11300, "message": "Invalid template URL", "log_level": "ERROR", "secondary_message": "The provided URL template has an invalid format. Please check to see if you have unclosed brackets.", "log_type": null, "docs": "## Error - 11300 \n\n### Invalid template URL\n\nThe provided URL template has an invalid format. Please check to see if you have unclosed brackets.\n\n\n\n\n\n", "causes": null, "solutions": null, "description": null, "product": null, "date_created": "2016-03-31T17:13:26Z", "last_updated": "2020-08-04T10:00:29.26Z" }, { "id": 32, "code": 11310, "message": "Invalid template token", "log_level": "ERROR", "secondary_message": "The provided URL template references a nonexistent token.", "log_type": null, "docs": "## Error - 11310 \n\n### Invalid template token\n\nThe provided URL template references a nonexistent token.\n\n\n\n\n\n", "causes": null, "solutions": null, "description": null, "product": null, "date_created": "2016-03-31T17:13:27Z", "last_updated": "2020-08-04T10:00:29.24Z" }, { "id": 33, "code": 11320, "message": "Invalid template unclosed brackets", "log_level": "ERROR", "secondary_message": "The provided URL template has an invalid format. Please check to see if you have unclosed brackets.", "log_type": null, "docs": "## Error - 11320 \n\n### Invalid template unclosed brackets\n\nThe provided URL template has an invalid format. Please check to see if you have unclosed brackets.\n\n\n\n\n\n", "causes": null, "solutions": null, "description": null, "product": null, "date_created": "2016-03-31T17:13:27Z", "last_updated": "2020-08-04T10:00:29.221Z" }, { "id": 34, "code": 11321, "message": "Misconfigured webhook", "log_level": "WARNING", "secondary_message": null, "log_type": "APPLICATION", "docs": "## WARNING - 11321\r\n\r\n### Misconfigured webhook\r\n\r\n You received a message to one of your Twilio numbers, but we could not send a request to your web application using your provided webhook URL because its format is invalid.\r\n\r\n\r\n#### Possible Causes\r\nMisconfigured URL for phone number \r\n\r\n#### Possible Solutions\r\n* Verify the URL in the Twilio Console to ensure it is correct and accessible\r\n* Make sure you submit a fully qualified URL including: protocol (http:// or https://), hostname, file path, and properly url-encoded query parameters. \r\n* Twilio must be able to reach this URL over the public Internet.\r\n", "causes": "Misconfigured URL for phone number ", "solutions": "* Verify the URL in the Twilio Console to ensure it is correct and accessible\r\n* Make sure you submit a fully qualified URL including: protocol (http:// or https://), hostname, file path, and properly url-encoded query parameters. \r\n* Twilio must be able to reach this URL over the public Internet.\r\n", "description": "You received a message to one of your Twilio numbers, but we could not send a request to your web application using your provided webhook URL because its format is invalid.\r\n", "product": "Programmable Messaging", "date_created": "2025-01-06T08:25:32Z", "last_updated": "2025-01-06T08:25:32Z" }, { "id": 35, "code": 11322, "message": "Invalid webhook method", "log_level": "WARNING", "secondary_message": null, "log_type": "APPLICATION", "docs": "## WARNING - 11322\r\n\r\n### Invalid webhook method\r\n\r\n You received a message to one of your Twilio numbers, but we could not send a request to your web application using your webhook URL due to an incorrect HTTP method.\r\n\r\n#### Possible Causes\r\nIncorrect HTTP method\r\n\r\n#### Possible Solutions\r\n* Twilio expects specific HTTP methods (GET or POST) for making a request to your application.\r\n* Check if the URL is configured to handle the correct HTTP method.\r\n", "causes": "Incorrect HTTP method", "solutions": "* Twilio expects specific HTTP methods (GET or POST) for making a request to your application.\r\n* Check if the URL is configured to handle the correct HTTP method.\r\n", "description": "You received a message to one of your Twilio numbers, but we could not send a request to your web application using your webhook URL due to an incorrect HTTP method.", "product": "Programmable Messaging", "date_created": "2025-01-06T08:28:03Z", "last_updated": "2025-01-06T08:28:03Z" }, { "id": 36, "code": 11750, "message": "TwiML response body too large", "log_level": "ERROR", "secondary_message": "In your response to Twilio’s request, the response body is larger than 64 kB.", "log_type": "APPLICATION", "docs": "## ERROR - 11750\r\n\r\n### TwiML response body too large\r\n\r\nIn your response to Twilio’s request, the response body is larger than 64 kB. ## Error - 11750\r\n\r\n## TwiML response body too large\r\n\r\nIn your response to Twilio's request, the response body is larger than 64 kB.\r\n\r\n#### Possible Causes\r\n* The TwiML that you are serving is larger than 64 kB\r\n* You are serving non-TwiML content in your response; e.g. error message output\r\n\r\n#### Possible Solutions\r\n* Verify that you are serving TwiML in your response to Twilio's request. \r\n* Verify that you are including this header in your TwiML response: `<?xml version=\"1.0\" encoding=\"UTF-8\"?>` \r\n* Limit your TwiML response to 64 kB or less.\r\n* Does your TwiML include the [Play verb](https://www.twilio.com/docs/voice/twiml/play)? Double-check the encoding and MIME type to ensure they are supported.\r\n* Check that your TwiML is formatted properly. To quickly verify your TwiML, you can copy and paste it into a new [TwiML bin in the Twilio Console](https://www.twilio.com/console/runtime/twiml-bins/create).\r\n* Check to see if your application is throwing errors. This may cause your application to send a large debug output back to Twilio instead of the expected TwiML.\r\n* If you are trying to send a `200` response in a status callback, use an empty TwiML response: `<Response/>`",