# Twilio 7.9.13 - Account Faulted: the trustAnchors parameter must be non-empty

**URL:** <https://forum.inductiveautomation.com/t/twilio-7-9-13-account-faulted-the-trustanchors-parameter-must-be-non-empty/53923>\
**Category:** Ignition\
**Tags:** ignition79\
**Created:** [December 9, 2021, 5:07am UTC](https://forum.inductiveautomation.com/t/twilio-7-9-13-account-faulted-the-trustanchors-parameter-must-be-non-empty/53923 "2021-12-09T05:07:48Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![will](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/will/32/5037_2.png) [@will](https://forum.inductiveautomation.com/u/will)\
**Post date:** [December 9, 2021, 5:07am UTC](https://forum.inductiveautomation.com/t/twilio-7-9-13-account-faulted-the-trustanchors-parameter-must-be-non-empty/53923/1 "2021-12-09T05:07:48Z")

</div>

Does anyone have any Twilio 7.9 projects active? I have a project that mysteriously started giving me SSL/certificate issues. I think it may have something to do with Twilio updating their own Root Certificates or something? Maybe we need to add another trusted certificate into Java?

Error: **Faulted: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty**

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/4/4/4408af21fd11e64c070ddb66a5f4b08f2a7e6113.png)

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [December 9, 2021, 2:18pm UTC](https://forum.inductiveautomation.com/t/twilio-7-9-13-account-faulted-the-trustanchors-parameter-must-be-non-empty/53923/2 "2021-12-09T14:18:31Z")

</div>

Pretty much every case I can remember where there was a TLS/SSL problem with a Twilio connection has been caused by a corporate proxy/firewall/MITM appliance getting in the way and replacing the certificate, which is either invalid or needs to be added to Ignition’s trust list.

---

<div class="post-metadata">

**Author:** ![will](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/will/32/5037_2.png) [@will](https://forum.inductiveautomation.com/u/will)\
**Post date:** [December 10, 2021, 3:39pm UTC](https://forum.inductiveautomation.com/t/twilio-7-9-13-account-faulted-the-trustanchors-parameter-must-be-non-empty/53923/3 "2021-12-10T15:39:20Z")

</div>

Solved;

This did originally occur because someone put this Azure-deployed VM behind a Load Balancer. After putting everything back to normal by removing said Load balancer it still wasn’t working… until I restarted the gateway. Now back to normal.