# Unhandled ssl status code: 16384 ( 4000) (SOLVED) **URL:** \ **Category:** Bugs\ **Created:** [February 14, 2020, 2:59pm UTC](https://forum.defold.com/t/unhandled-ssl-status-code-16384-4000-solved/64451 "2020-02-14T14:59:44Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![Mathias\_Westerdahl](https://forum-defold.b-cdn.net/user_avatar/forum.defold.com/mathias_westerdahl/32/228_2.png) [@Mathias\_Westerdahl](https://forum.defold.com/u/Mathias_Westerdahl)\ **Post date:** [February 14, 2020, 8:36pm UTC](https://forum.defold.com/t/unhandled-ssl-status-code-16384-4000-solved/64451/5 "2020-02-14T20:36:26Z")
> Defold 1.2.162 > We’ve replaced the internal SSL library to mbedTls, and the `http.request()` can now work with a lot more secure sites, including [Playfab](https://www.defold.com/community/projects/89570/) In the [1.2.162 Release](https://forum.defold.com/t/defold-1-2-162-has-been-released/62959), we moved from using `axTls` to `mbedTls` for supporting https requests towards sites with more modern handshakes. I very much suspect this change to be the cause of this issue. It is always unfortunate when we happen to break some functionality that has worked previously. But sometimes it happens, and we’re sorry about that. In this instance, it was a feature we didn’t know the library had, and we didn’t have a test for it (since it came with the library). Also, it is the reason it wasn’t specifically documented. I can agree that we can do better in terms of communication, and with the new [release process](https://forum.defold.com/t/new-release-process/64080) we hope to be able to, with the help of our power users, test a new BETA release’s features before they get published. As for a proper fix, we’ll look into it, but I currently have no ETA. As for a workaround, you can try to send via HTTP instead (if possible). --- _[View the full topic](https://forum.defold.com/t/unhandled-ssl-status-code-16384-4000-solved/64451)._