Docusign app getting error this page isn't working right now, local host can't currently handle this request, http error 500

userXuOa 0
Viewed 41

I'm developing an app based on the Docusign C# Quickstart. Its working fine on my development PC (Win 11) in Visual Studio 2019 using IIS Express. However, when I publish it to IIS (v10) on my development PC it runs and I can authenticate with Docusign just fine (once I got the proper redirect URI registered: https://localhost/ds/callback) but the step that actually sends the envelope is returning the following error in the browser:

This page isn't working right now. Local host can't handle this request http error 500

Any help is appreciated. I logged a support ticket with Docusign, but still waiting for a response.

docusignapi asp.net-core
2 Answers

Quickstart is just an app to show you how to use DocuSign APIs. The redirect after signing is back to localhost, and your app, once ready to be deployed to server, has to be set with a proper URL, at which point you'll need to update the redirect URI to the one based on your server. The 500 error is coming from your app, not from DocuSign. You need to figure out why your app cannot handle the URL that is set for redirect after signing by DocuSign.

Inbar Gazit0

The base API address demo.docusign.net/restapi is used to reach the development/ test platform. The na4.docusign.net/restapi address is one of DocuSign's (many) production platforms.

Remember that, once you have passed the Go-Live process, you have two Client IDs (integration keys) one for the test platform, one for all of the production platforms. Each has its own settings.

Added

The error

This page isn't working right now. 
Local host can't handle this request http error 500

Is from IIS. Use IIS logging to see the URL request that is coming in that can't be handled.

To see if it is the redirect from the initial OAuth Authorization Code grant URL, examine the initial URL redirect to account.docusign.com (prod URL).

The redirect contained as a query parameter in the initial OAuth redirect must:

  1. Be correct for your instance of IIS.
  2. Be allowed by your setting for the client ID (integration key) in DocuSign 1, Be properly handled by your IIS and its app.
Larry K0
Related