# Stakeholder receiving SSL Protocal Error

**URL:** <https://community.feathery.io/t/stakeholder-receiving-ssl-protocal-error/914>\
**Category:** Support\
**Created:** [July 19, 2024, 4:26pm UTC](https://community.feathery.io/t/stakeholder-receiving-ssl-protocal-error/914 "2024-07-19T16:26:54Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![bercohen](https://avatars.discourse-cdn.com/v4/letter/b/3da27b/32.png) [@bercohen](https://community.feathery.io/u/bercohen)\
**Post date:** [July 19, 2024, 4:26pm UTC](https://community.feathery.io/t/stakeholder-receiving-ssl-protocal-error/914/1 "2024-07-19T16:26:54Z")

</div>

Hi, we just launched a newly designed form.

> **[Bato - Injury Quiz](https://form.feathery.io/to/odZtZP)**
>
> The most powerful no-code forms & workflows

Our stakeholder is receiving a err\_ssl\_protocol\_error when trying to view the form on his mobile device. Android - chrome.

 ![Screenshot_20240719_121258_Chrome](https://canada1.discourse-cdn.com/flex030/uploads/feathery/original/1X/81b75892356d18531966dfa5af717ca92531185b.jpeg)

---

<div class="post-metadata">

**Author:** ![eri](https://avatars.discourse-cdn.com/v4/letter/e/8baadc/32.png) [@eri](https://community.feathery.io/u/eri)\
**Post date:** [July 19, 2024, 5:24pm UTC](https://community.feathery.io/t/stakeholder-receiving-ssl-protocal-error/914/2 "2024-07-19T17:24:14Z")

</div>

Hi there - how are you sharing the link to them?  
I looked up this form id and it does not exist in your workspace at the moment. The “Bato - Injury Quiz” you have there have a different form id. Could this one you linked be a deleted older version?

---

<div class="post-metadata">

**Author:** ![bercohen](https://avatars.discourse-cdn.com/v4/letter/b/3da27b/32.png) [@bercohen](https://community.feathery.io/u/bercohen)\
**Post date:** [July 19, 2024, 5:26pm UTC](https://community.feathery.io/t/stakeholder-receiving-ssl-protocal-error/914/3 "2024-07-19T17:26:22Z")

</div>

Thanks I had the form link set to auto-expire.  
here is the new link

> **[Bato - Injury Quiz](https://form.feathery.io/to/jSSAI9#Injury%20Purpose)**
>
> The most powerful no-code forms & workflows

---

<div class="post-metadata">

**Author:** ![eri](https://avatars.discourse-cdn.com/v4/letter/e/8baadc/32.png) [@eri](https://community.feathery.io/u/eri)\
**Post date:** [July 19, 2024, 6:15pm UTC](https://community.feathery.io/t/stakeholder-receiving-ssl-protocal-error/914/4 "2024-07-19T18:15:54Z")

</div>

Thanks for confirming that!

Unfortunately, as this kind of error is isolated to that end user network (and can’t be reproduced on anyone’s end), it’s hard for us to investigate further at this time. This is highly likely due to their own local network settings. If you’re in direct contact, may we suggest to ask them try switching networks (maybe from WiFi to mobile data or vice versa), and if possible inform us of their ISP (if it turned out dependent on that) and their location.

---

<div class="post-metadata">

**Author:** ![bercohen](https://avatars.discourse-cdn.com/v4/letter/b/3da27b/32.png) [@bercohen](https://community.feathery.io/u/bercohen)\
**Post date:** [July 19, 2024, 6:41pm UTC](https://community.feathery.io/t/stakeholder-receiving-ssl-protocal-error/914/5 "2024-07-19T18:41:11Z")

</div>

Thanks. I will see if switching networks solves the problem for them.

My concern is, how can we be sure that many of our users won’t experience this issue when the form is live to a large audience?

---

<div class="post-metadata">

**Author:** ![peter](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.feathery.io/peter/32/7_2.png) [@peter](https://community.feathery.io/u/peter)\
**Post date:** [August 2, 2024, 4:21pm UTC](https://community.feathery.io/t/stakeholder-receiving-ssl-protocal-error/914/6 "2024-08-02T16:21:15Z")

</div>

All SSL protocol errors should now be resolved

---

<div class="post-metadata">

**Author:** ![Thropic](https://avatars.discourse-cdn.com/v4/letter/t/c57346/32.png) [@Thropic](https://community.feathery.io/u/Thropic)\
**Post date:** [August 27, 2024, 11:23pm UTC](https://community.feathery.io/t/stakeholder-receiving-ssl-protocal-error/914/7 "2024-08-27T23:23:16Z")

</div>

I’m having the same issue. We sent a form to an audience and 4/20 users let us know they received ERR\_SSL\_PROTOCOL\_ERROR response. Switching networks did resolve the issue for some of them but the error rate was quite high.

> **[Take the NFL Charity Quiz – Win Cash, Give Back, and Play Now!](https://form.feathery.io/to/ldudNe)**
>
> Benefiting the Boys and Girls Clubs of Denver

---

<div class="post-metadata">

**Author:** ![eri](https://avatars.discourse-cdn.com/v4/letter/e/8baadc/32.png) [@eri](https://community.feathery.io/u/eri)\
**Post date:** [August 28, 2024, 12:33am UTC](https://community.feathery.io/t/stakeholder-receiving-ssl-protocal-error/914/8 "2024-08-28T00:33:50Z")

</div>

@Thropic hello, we’ve made your forms available at **craftalley**.feathery.io/to/formId  
this should help in getting rid of the SSL errors

---

<div class="post-metadata">

**Author:** ![Ty\_Bogle](https://avatars.discourse-cdn.com/v4/letter/t/c68b51/32.png) [@Ty\_Bogle](https://community.feathery.io/u/Ty_Bogle)\
**Post date:** [August 28, 2024, 3:11pm UTC](https://community.feathery.io/t/stakeholder-receiving-ssl-protocal-error/914/9 "2024-08-28T15:11:13Z")

</div>

Hello, I have a form that over 100 people have completed and many including our own CEO cannot access the form. We’ll be releasing this form to over 4000 of our clients.

This image is from one of our clients.

Here is the form link. [2024-AEP HCQ](https://form.feathery.io/to/ne2sRM)

 ![image](https://canada1.discourse-cdn.com/flex030/uploads/feathery/original/1X/c36c236b8eadb4e08ba0af147e02d0ddee9fa1da.jpeg)

---

<div class="post-metadata">

**Author:** ![eri](https://avatars.discourse-cdn.com/v4/letter/e/8baadc/32.png) [@eri](https://community.feathery.io/u/eri)\
**Post date:** [August 28, 2024, 3:28pm UTC](https://community.feathery.io/t/stakeholder-receiving-ssl-protocal-error/914/10 "2024-08-28T15:28:49Z")

</div>

@Ty_Bogle you can set a feathery subdomain in your settings to change up the link a bit! this should help in getting rid of the SSL errors

 ![image](https://canada1.discourse-cdn.com/flex030/uploads/feathery/original/1X/be55b8c135187a331e128fff888974f5e4aa11de.png)

---

<div class="post-metadata">

**Author:** ![Ty\_Bogle](https://avatars.discourse-cdn.com/v4/letter/t/c68b51/32.png) [@Ty\_Bogle](https://community.feathery.io/u/Ty_Bogle)\
**Post date:** [August 28, 2024, 4:05pm UTC](https://community.feathery.io/t/stakeholder-receiving-ssl-protocal-error/914/11 "2024-08-28T16:05:39Z")

</div>

Thank you. I will try that.
