https://community.appian.com/support/w/kb/807/kb-1483-connection-closed-errors-when-connecting-to-appian-cloud-from-external-resourcesen-USTelligent Community 12https://community.appian.com/support/w/kb/807/kb-1483-connection-closed-errors-when-connecting-to-appian-cloud-from-external-resourcesSun, 22 Jul 2018 21:42:50 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:2fda8510-b948-4fd1-ab8c-54e5a046a2a0Parmida Borhanihttps://community.appian.com/support/w/kb/807/kb-1483-connection-closed-errors-when-connecting-to-appian-cloud-from-external-resources#commentsCurrent Revision posted to Appian Knowledge Base by Parmida Borhani on 7/22/2018 9:42:50 PM<br /> <h2>Symptoms</h2> <p>Previously functional connections from&nbsp;external resources, such as Web API calls, to Appian Cloud instances start failing with the following exception or a similar one indicating the forceful termination of the connection to Appian:</p> <pre>The underlying connection was closed: An unexpected error occurred on a send.</pre> <h2>Cause</h2> <p>This typically indicates that the resource attempting to connect to the Appian Cloud instance is not configured to use TLS 1.1 or higher. Appian&nbsp;does not support&nbsp;TLS 1.0.</p> <h2>Action</h2> <p>Use cURL or a third-party tool such as <a href="https://www.getpostman.com/" target="_blank">Postman</a> or <a href="https://www.soapui.org/" target="_blank">SoapUI</a>&nbsp;from the origin server to verify that the connection still works as expected with a client that supports TLS 1.1. If this is the case, update the application code or client version to support TLS 1.1 or higher. Please note that Appian is unable to provide detailed instructions for updating external systems to use TLS 1.1. If you require assistance in making this change, contact the vendor or developer supplying the external system.</p> <h2>Affected Versions</h2> <p>This article applies to all versions of Appian Cloud.</p> <p>Last Reviewed: July 2018</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: web APIs, Security, web services, TLS, Cloud</div> https://community.appian.com/support/w/kb/807/kb-1483-connection-closed-errors-when-connecting-to-appian-cloud-from-external-resources/revision/7Sun, 22 Jul 2018 21:42:30 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:2fda8510-b948-4fd1-ab8c-54e5a046a2a0Parmida Borhanihttps://community.appian.com/support/w/kb/807/kb-1483-connection-closed-errors-when-connecting-to-appian-cloud-from-external-resources#commentsRevision 7 posted to Appian Knowledge Base by Parmida Borhani on 7/22/2018 9:42:30 PM<br /> <h2>Symptoms</h2> <p>Previously functional connections from&nbsp;external resources, such as Web API calls, to Appian Cloud instances start failing with the following exception or a similar one indicating the forceful termination of the connection to Appian:</p> <pre>The underlying connection was closed: An unexpected error occurred on a send.</pre> <h2>Cause</h2> <p>This typically indicates that the resource attempting to connect to the Appian Cloud instance is not configured to use TLS 1.1 or higher. Appian&nbsp;does not support&nbsp;TLS 1.0.</p> <h2>Action</h2> <p>Use cURL or a third-party tool such as <a href="https://www.getpostman.com/" target="_blank">Postman</a> or <a href="https://www.soapui.org/" target="_blank">SoapUI</a>&nbsp;from the origin server to verify that the connection still works as expected with a client that supports TLS 1.1. If this is the case, update the application code or client version to support TLS 1.1 or higher. Please note that Appian is unable to provide detailed instructions for updating external systems to use TLS 1.1. If you require assistance in making this change, contact the vendor or developer supplying the external system.</p> <h2>Affected Versions</h2> <p>This article applies to&nbsp;Appian Cloud.</p> <p>Last Reviewed: July 2018</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: web APIs, Security, web services, TLS, Cloud</div> https://community.appian.com/support/w/kb/807/kb-1483-connection-closed-errors-when-connecting-to-appian-cloud-from-external-resources/revision/6Wed, 31 Jan 2018 18:27:38 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:2fda8510-b948-4fd1-ab8c-54e5a046a2a0Nick Vigilantehttps://community.appian.com/support/w/kb/807/kb-1483-connection-closed-errors-when-connecting-to-appian-cloud-from-external-resources#commentsRevision 6 posted to Appian Knowledge Base by Nick Vigilante on 1/31/2018 6:27:38 PM<br /> <h2>Symptoms</h2> <p>Previously functional connections from&nbsp;external resources, such as Web API calls, to Appian Cloud instances start failing with the following exception or a similar one indicating the forceful termination of the connection to Appian:</p> <pre>The underlying connection was closed: An unexpected error occurred on a send.</pre> <h2>Cause</h2> <p>This typically indicates that the resource attempting to connect to the Appian Cloud instance is not configured to use TLS 1.1 or higher. Appian is in the process of deprecating TLS 1.0 support in Appian Cloud and Appian Cloud instances will no longer permit connections using TLS 1.0. For more information about Appian&#39;s deprecation of TLS 1.0, see&nbsp;<a href="/support/w/kb/289/kb-1064-appian-cloud---end-of-support-for-tls-1-0" target="_blank">KB-1064</a>.&nbsp;</p> <h2>Action</h2> <p>Use cURL or a third-party tool such as <a href="https://www.getpostman.com/" target="_blank">Postman</a> or <a href="https://www.soapui.org/" target="_blank">SoapUI</a>&nbsp;from the origin server to verify that the connection still works as expected with a client that supports TLS 1.1. If this is the case, update the application code or client version to support TLS 1.1 or higher. Please note that Appian is unable to provide detailed instructions for updating external systems to use TLS 1.1. If you require assistance in making this change, contact the vendor or developer supplying the external system.</p> <h2>Affected Versions</h2> <p>This article applies to&nbsp;Appian Cloud.</p> <p>Last Reviewed: January 2018</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: web APIs, Security, web services, TLS, Cloud</div> https://community.appian.com/support/w/kb/807/kb-1483-connection-closed-errors-when-connecting-to-appian-cloud-from-external-resources/revision/1Tue, 30 Jan 2018 22:25:47 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:2fda8510-b948-4fd1-ab8c-54e5a046a2a0Jussi Lundstedthttps://community.appian.com/support/w/kb/807/kb-1483-connection-closed-errors-when-connecting-to-appian-cloud-from-external-resources#commentsRevision 1 posted to Appian Knowledge Base by Jussi Lundstedt on 1/30/2018 10:25:47 PM<br /> <h2>Symptom</h2> <p>Previously functional connections from external resources to Appian Cloud instances, such as Web API calls, start failing with the following exception or a similar one indicating the forceful termination of the connection to Appian:</p> <pre>The underlying connection was closed: An unexpected error occurred on a send.</pre> <h2>Cause</h2> <p>This typically indicates that the resource attempting to connect to the Appian Cloud instance is not configured to use TLS 1.1 or higher. Appian is in the process of deprecating TLS 1.0 support in Appian Cloud, and Appian Cloud instances will no longer permit connections using TLS 1.0. For more information about Appian&#39;s deprecation of TLS 1.0, see&nbsp;<a href="/support/w/kb/289/kb-1064-appian-cloud---end-of-support-for-tls-1-0" target="_blank">KB-1064</a>.&nbsp;</p> <h2>Action</h2> <p>Use cURL or a third-party tool such as <a href="https://www.getpostman.com/" target="_blank">Postman</a> or <a href="https://www.soapui.org/" target="_blank">SoapUI</a>&nbsp;from the origin server to verify that the connection still works as expected with a client that supports TLS 1.1. If this is the case, update the application code or client version to support TLS 1.1 or higher. Please note that Appian is unable to provide detailed instructions for updating external systems to use TLS 1.1. If you require assistance in making this change, contact the vendor or developer supplying the external system.</p> <h2>Affected Versions</h2> <p>This article applies to all Appian Cloud instances.</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: HTTP, exception, web services</div> https://community.appian.com/support/w/kb/807/kb-1483-connection-closed-errors-when-connecting-to-appian-cloud-from-external-resources/revision/5Tue, 30 Jan 2018 22:15:19 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:2fda8510-b948-4fd1-ab8c-54e5a046a2a0Parmida Borhanihttps://community.appian.com/support/w/kb/807/kb-1483-connection-closed-errors-when-connecting-to-appian-cloud-from-external-resources#commentsRevision 5 posted to Appian Knowledge Base by Parmida Borhani on 1/30/2018 10:15:19 PM<br /> <h2>Symptoms</h2> <p>Previously functional connections from&nbsp;external resources, such as Web API calls, to Appian Cloud instances start failing with the following exception or a similar one indicating the forceful termination of the connection to Appian:</p> <pre>The underlying connection was closed: An unexpected error occurred on a send.</pre> <h2>Cause</h2> <p>This typically indicates that the resource attempting to connect to the Appian Cloud instance is not configured to use TLS 1.1 or higher. Appian is in the process of deprecating TLS 1.0 support in Appian Cloud and Appian Cloud instances will no longer permit connections using TLS 1.0. For more information about Appian&#39;s deprecation of TLS 1.0, see&nbsp;<a href="/support/w/kb/289/kb-1064-appian-cloud---end-of-support-for-tls-1-0" target="_blank">KB-1064</a>.&nbsp;</p> <h2>Action</h2> <p>Use cURL or a third-party tool such as <a href="https://www.getpostman.com/" target="_blank">Postman</a> or <a href="https://www.soapui.org/" target="_blank">SoapUI</a>&nbsp;from the origin server to verify that the connection still works as expected with a client that supports TLS 1.1. If this is the case, update the application code or client version to support TLS 1.1 or higher. Please note that Appian is unable to provide detailed instructions for updating external systems to use TLS 1.1. If you require assistance in making this change, contact the vendor or developer supplying the external system.</p> <h2>Affected Versions</h2> <p>This article applies to&nbsp;Appian Cloud.</p> <p>Last Reviewed: January 2018</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: security, web services, TLS, Cloud, web api</div> https://community.appian.com/support/w/kb/807/kb-1483-connection-closed-errors-when-connecting-to-appian-cloud-from-external-resources/revision/4Tue, 30 Jan 2018 21:59:24 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:2fda8510-b948-4fd1-ab8c-54e5a046a2a0Parmida Borhanihttps://community.appian.com/support/w/kb/807/kb-1483-connection-closed-errors-when-connecting-to-appian-cloud-from-external-resources#commentsRevision 4 posted to Appian Knowledge Base by Parmida Borhani on 1/30/2018 9:59:24 PM<br /> <h2>Symptoms</h2> <p>Previously functional connections from Appian Cloud instances to external resources, such as Web API calls, start failing with the following exception or a similar one indicating the forceful termination of the connection to Appian:</p> <pre>The underlying connection was closed: An unexpected error occurred on a send.</pre> <h2>Cause</h2> <p>This typically indicates that the resource attempting to connect to the Appian Cloud instance is not configured to use TLS 1.1 or higher. Appian is in the process of deprecating TLS 1.0 support in Appian Cloud and Appian Cloud instances will no longer permit connections using TLS 1.0. For more information about Appian&#39;s deprecation of TLS 1.0, see&nbsp;<a href="/support/w/kb/289/kb-1064-appian-cloud---end-of-support-for-tls-1-0" target="_blank">KB-1064</a>.&nbsp;</p> <h2>Action</h2> <p>Use cURL or a third-party tool such as <a href="https://www.getpostman.com/" target="_blank">Postman</a> or <a href="https://www.soapui.org/" target="_blank">SoapUI</a>&nbsp;from the origin server to verify that the connection still works as expected with a client that supports TLS 1.1. If this is the case, update the application code or client version to support TLS 1.1 or higher. Please note that Appian is unable to provide detailed instructions for updating external systems to use TLS 1.1. If you require assistance in making this change, contact the vendor or developer supplying the external system.</p> <h2>Affected Versions</h2> <p>This article applies to&nbsp;Appian Cloud.</p> <p>Last Reviewed: January 2018</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: security, web services, TLS, Cloud, web api</div> https://community.appian.com/support/w/kb/807/kb-1483-connection-closed-errors-when-connecting-to-appian-cloud-from-external-resources/revision/3Tue, 30 Jan 2018 21:58:36 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:2fda8510-b948-4fd1-ab8c-54e5a046a2a0Parmida Borhanihttps://community.appian.com/support/w/kb/807/kb-1483-connection-closed-errors-when-connecting-to-appian-cloud-from-external-resources#commentsRevision 3 posted to Appian Knowledge Base by Parmida Borhani on 1/30/2018 9:58:36 PM<br /> <h2>Symptoms</h2> <p>Previously functional connections from Appian Cloud instances to external resources, such as Web API calls, start failing with the following exception or a similar one indicating the forceful termination of the connection to Appian:</p> <pre>The underlying connection was closed: An unexpected error occurred on a send.</pre> <h2>Cause</h2> <p>This typically indicates that the resource attempting to connect to the Appian Cloud instance is not configured to use TLS 1.1 or higher. Appian is in the process of deprecating TLS 1.0 support in Appian Cloud and Appian Cloud instances will no longer permit connections using TLS 1.0. For more information about Appian&#39;s deprecation of TLS 1.0, see&nbsp;<a href="/support/w/kb/289/kb-1064-appian-cloud---end-of-support-for-tls-1-0" target="_blank">KB-1064</a>.&nbsp;</p> <h2>Action</h2> <p>Use cURL or a third-party tool such as <a href="https://www.getpostman.com/" target="_blank">Postman</a> or <a href="https://www.soapui.org/" target="_blank">SoapUI</a>&nbsp;from the origin server to verify that the connection still works as expected with a client that supports TLS 1.1. If this is the case, update the application code or client version to support TLS 1.1 or higher. Please note that Appian is unable to provide detailed instructions for updating external systems to use TLS 1.1. If you require assistance in making this change, contact the vendor or developer supplying the external system.</p> <h2>Affected Versions</h2> <p>This article applies to&nbsp;Appian Cloud.</p> <p>Last Reviewed: January 2018</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: web services, web api</div> https://community.appian.com/support/w/kb/807/kb-1483-connection-closed-errors-when-connecting-to-appian-cloud-from-external-resources/revision/2Tue, 30 Jan 2018 17:26:05 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:2fda8510-b948-4fd1-ab8c-54e5a046a2a0Jussi Lundstedthttps://community.appian.com/support/w/kb/807/kb-1483-connection-closed-errors-when-connecting-to-appian-cloud-from-external-resources#commentsRevision 2 posted to Appian Knowledge Base by Jussi Lundstedt on 1/30/2018 5:26:05 PM<br /> <h2>Symptom</h2> <p>Previously functional connections from external resources to Appian Cloud instances, such as Web API calls, start failing with the following exception or a similar one indicating the forceful termination of the connection to Appian:</p> <pre>The underlying connection was closed: An unexpected error occurred on a send.</pre> <h2>Cause</h2> <p>This typically indicates that the resource attempting to connect to the Appian Cloud instance is not configured to use TLS 1.1 or higher. Appian is in the process of deprecating TLS 1.0 support in Appian Cloud, and Appian Cloud instances will no longer permit connections using TLS 1.0. For more information about Appian&#39;s deprecation of TLS 1.0, see&nbsp;<a href="/support/w/kb/289/kb-1064-appian-cloud---end-of-support-for-tls-1-0" target="_blank">KB-1064</a>.&nbsp;</p> <h2>Action</h2> <p>Use cURL or a third-party tool such as <a href="https://www.getpostman.com/" target="_blank">Postman</a> or <a href="https://www.soapui.org/" target="_blank">SoapUI</a>&nbsp;from the origin server to verify that the connection still works as expected with a client that supports TLS 1.1. If this is the case, update the application code or client version to support TLS 1.1 or higher. Please note that Appian is unable to provide detailed instructions for updating external systems to use TLS 1.1. If you require assistance in making this change, contact the vendor or developer supplying the external system.</p> <h2>Affected Versions</h2> <p>This article applies to all Appian Cloud instances.</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: HTTP, exception, web services</div>