{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 聊天终结者 的问题《Demo Docusign API: java.net.SocketException Connec》','https://www.manongdao.com/q-448120.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
We started receiving this error recently. Our API has been working for over four years. Did something change on the DEMO website?
Caused by: java.net.SocketException invoking https://demo.docusign.net/API/3.0/AccountManagement.asmx: Connection reset
标签：
docusignapi
相关问题
- listStatusChanges api gives error after passing mo
- Mix and match templates with documents
- Docusign: Creating a Document with dynamic content
- Preview tags with docusign API
- Checkbox validation using Docusign REST API
相关文章
- Docusign return parameters in embedded signing by
- Retrieving information from a signed document Docu
- Programmatically signing a document
- docusign send on behalf functionality
- Filtering Envelopes based on a type
- “Bad Request” message in JWT OAuth authentication
- Docusign - API to reactivate a closed user
- Not able to pass in values to docusign template
Per DS Support, DocuSign has ended support for TLS1.0 in Demo from May 29th, 2018 and will soon end the support in PROD as well. Please test the connection on your end if you are using TLS1.0, if yes then you need to upgrade it to
TLS1.1+to again start using DS APIs. I am assuming if you have not done any code changes then this is the issue which you are seeing in your application.