# Getting hammered with ERR\_SSL\_PROTOCOL\_ERROR **URL:** \ **Category:** Support\ **Tags:** netlify-dns-https-ssl\ **Created:** [June 16, 2022, 7:43pm UTC](https://answers.netlify.com/t/getting-hammered-with-err-ssl-protocol-error/68352 "2022-06-16T19:43:05Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![Hotsauce](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/hotsauce/32/25104_2.png) [@Hotsauce](https://answers.netlify.com/u/Hotsauce)\ **Post date:** [June 16, 2022, 7:43pm UTC](https://answers.netlify.com/t/getting-hammered-with-err-ssl-protocol-error/68352/1 "2022-06-16T19:43:05Z")
Site: nostalgic-leavitt-186d07 ([HotUtils.com](http://HotUtils.com)) Our users are experiencing frequent net::ERR\_SSL\_PROTOCOL\_ERROR on our api calls from the site. A simple retry and it works, but it is happening at a very frequent rate. We have done all the troubleshooting we can on our side, just at a complete loss of what is going on. Please help. ---
**Author:** ![woutervandam](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/woutervandam/32/20688_2.png) [@woutervandam](https://answers.netlify.com/u/woutervandam)\ **Post date:** [June 17, 2022, 10:21am UTC](https://answers.netlify.com/t/getting-hammered-with-err-ssl-protocol-error/68352/2 "2022-06-17T10:21:39Z")
We’re seeing the same. ---
**Author:** ![Hotsauce](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/hotsauce/32/25104_2.png) [@Hotsauce](https://answers.netlify.com/u/Hotsauce)\ **Post date:** [June 17, 2022, 12:48pm UTC](https://answers.netlify.com/t/getting-hammered-with-err-ssl-protocol-error/68352/3 "2022-06-17T12:48:40Z")
An update to our issue, we had to remove the redirect/proxy we were using. Removing that has solved the issue for the time being. There must be an issue in that system right now. ---
**Author:** ![woutervandam](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/woutervandam/32/20688_2.png) [@woutervandam](https://answers.netlify.com/u/woutervandam)\ **Post date:** [June 17, 2022, 2:00pm UTC](https://answers.netlify.com/t/getting-hammered-with-err-ssl-protocol-error/68352/4 "2022-06-17T14:00:04Z")
Are you talking about the redirect rules specified in netlify.toml? ---
**Author:** ![Hotsauce](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/hotsauce/32/25104_2.png) [@Hotsauce](https://answers.netlify.com/u/Hotsauce)\ **Post date:** [June 17, 2022, 2:18pm UTC](https://answers.netlify.com/t/getting-hammered-with-err-ssl-protocol-error/68352/5 "2022-06-17T14:18:04Z")
yes we had our external API calls going through it, and that was causing the random SSL errors. ---
**Author:** ![perry](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/perry/32/16_2.png) [@perry](https://answers.netlify.com/u/perry)\ **Post date:** [June 17, 2022, 4:53pm UTC](https://answers.netlify.com/t/getting-hammered-with-err-ssl-protocol-error/68352/6 "2022-06-17T16:53:26Z")
hi there Hotsauce, were you proxying to netlify? we generally advise against that: > [@\[Support Guide\] Why not proxy to Netlify?](https://answers.netlify.com/t/support-guide-why-not-proxy-to-netlify/8869): > > Last reviewed by Netlify Support Staff in August 2023 Netlify runs a CDN backed by several separate network service providers, and our CDN [automatically routes your web visitors’ traffic to a network-nearby server](https://answers.netlify.com/t/support-guide-how-are-requests-routed-to-the-nearest-netlify-cdn-node/105) to give them the fastest possible response time…as long as you let their browsers talk directly to our CDN! We know you want your [your web traffic to be fast](https://www.netlify.com/tags/performance/); your [deploys and rollbacks to be atomic](https://docs.netlify.com/site-deploys/overview/); and your [Analytics data](https://www.netlify.com/products/analytics/) to be useful. If you proxy to Netlify, you’ll have problems… ---
**Author:** ![Hotsauce](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/hotsauce/32/25104_2.png) [@Hotsauce](https://answers.netlify.com/u/Hotsauce)\ **Post date:** [June 17, 2022, 7:23pm UTC](https://answers.netlify.com/t/getting-hammered-with-err-ssl-protocol-error/68352/7 "2022-06-17T19:23:08Z")
We were making our external api calls through the netlify forwarding, and it was working great for the past year or so. 1-2 days ago all this SSL error stuff began happening. We configured CORS on our web server, and pointed everything directly at the server now, and the problem has been solved, but this created a ton of chaos on our Production system and would love to know why this changed or what the cause was. ---
**Author:** ![hrishikesh](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/hrishikesh/32/74607_2.png) [@hrishikesh](https://answers.netlify.com/u/hrishikesh)\ **Post date:** [June 19, 2022, 12:53pm UTC](https://answers.netlify.com/t/getting-hammered-with-err-ssl-protocol-error/68352/8 "2022-06-19T12:53:44Z")
This was affecting a few more users and has since been fixed. Are you still seeing this? ---
**Author:** ![jgoldshlag](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/jgoldshlag/32/38299_2.png) [@jgoldshlag](https://answers.netlify.com/u/jgoldshlag)\ **Post date:** [June 19, 2022, 4:53pm UTC](https://answers.netlify.com/t/getting-hammered-with-err-ssl-protocol-error/68352/9 "2022-06-19T16:53:56Z")
We stopped using the netlify redirects, and switched to directly talking to our backend api server, so no idea if this is still going on