Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Hi,

I have the same problem.

The error that I get is:

System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Authentication failed because the remote party has closed the transport stream.

Everything was working fine until the beginning of May. The error occurs when my system tries to PUT new request into the Webhook. 

Any idea what might cause this problem?

Thanks,

Nikola

Hi @Nikola! I moved your reply to a new post so that we can better help with the trouble that you’re having 🙂

 

From the looks of the error message, it sounds like something has changed in the way that the app receiving the webhook has changed the way it expects to receive data. If yo haven’t changed anything else in the Zap, then that would be the most likely cause. Are you able to find out if anything has changed on the receiving end of the webhook? And just to make sure that we’re on the same page, is the webhook sending information to a third party app or a resource that you control (eg a database)? 

my 2 cents: it isn’t a slam dunk that the other end point has changed, Zapier could have changed how it fires PUTs too, sorry Zapier. Do a test - redirect the PUT to a test tool like webhook.site and visually inspect what the PUT looks like at the other end, is the json good, are fields missing, etc

I’ve had issue where Zapier says what the PUT looks like and guess what - it looks different at the other end

Hi @Nikola! I moved your reply to a new post so that we can better help with the trouble that you’re having 🙂

 

From the looks of the error message, it sounds like something has changed in the way that the app receiving the webhook has changed the way it expects to receive data. If yo haven’t changed anything else in the Zap, then that would be the most likely cause. Are you able to find out if anything has changed on the receiving end of the webhook? And just to make sure that we’re on the same page, is the webhook sending information to a third party app or a resource that you control (eg a database)? 

Nothing has changed in the application.

 

@Nikola Thanks for the update on the application. Could you possible try what @bubba198 described:

Do a test - redirect the PUT to a test tool like webhook.site and visually inspect what the PUT looks like at the other end, is the json good, are fields missing, etc

 

and see if that gives you a clue as to what’s happening?

Terms & Conditions