# Httpclient issue with tls

**URL:** <https://forum.inductiveautomation.com/t/httpclient-issue-with-tls/52209>\
**Category:** Ignition\
**Created:** [October 21, 2021, 12:34pm UTC](https://forum.inductiveautomation.com/t/httpclient-issue-with-tls/52209 "2021-10-21T12:34:37Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [October 21, 2021, 12:39pm UTC](https://forum.inductiveautomation.com/t/httpclient-issue-with-tls/52209/2 "2021-10-21T12:39:13Z")

</div>

The server you are targeting is out of date. Newer versions of java block the insecure TLS versions it wants to use. Same problem others have encountered with Database connections:

> [@SQL Server Connection Faulted](https://forum.inductiveautomation.com/t/sql-server-connection-faulted/46393):
>
> After replacing a development installation of Ignition 8.1 with 7.9.17, I am suddenly unable to communicate with my local SQL server. The connection was fine before the reinstall but now it’s faulted and showing this error: Cannot create PoolableConnectionFactory (The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: “No appropriate protocol (protocol is disabled or cipher suites are inappropriate)”.) I’ve double checked all t…

The correct solution is have the operators of that server upgrade their security.  
The alternate solution is for you to re-enable old TLS on your end as described in that topic.

---

_[View the full topic](https://forum.inductiveautomation.com/t/httpclient-issue-with-tls/52209)._
