markh

e-SignLive Callback failed.

Friday, July 13, 2018 at 08:32am
0 votes
Hello, Our network admins moved our DNS servers yesterday and this morning our esign callback is failing. Failed to communicate with the callback server. URL: https://URL.in.question/Esign/EsignComplete.aspx Payload: {"@class":"com.silanis.esl.packages.event.ESLProcessEvent","name":"PACKAGE_COMPLETE","sessionUser Move was complete last night and all the places I know to look show that it is fully propagated. All pages show up fine. Any suggestions on what to check next? Thanks for your time, Mark
Duo_Liang

Reply to: e-SignLive Callback failed.

Friday, July 13, 2018 at 09:38am
0 votes
Hi Mark, Could it because of the IP White list issue as this is off the top of my head. Or you could always try sending a request which simulates the callback call via POSTMAN from outside of your network to see if the callback URL is accessible. Just in case, if you have changed your callback URL, you should update it trough WebUI or make a api call, guidance here. Hope this could help you!

Duo Liang OneSpan Evangelism and Partner Integrations Developer

markh

Reply to: e-SignLive Callback failed.

Friday, July 13, 2018 at 09:45am
0 votes
Hello, Thanks for your reply. The only thing that has changed is DNS provider. Our fear is that the esignlive dns cache has the old info and we will just have to wait for their cache to expire. MH
Duo_Liang

Reply to: e-SignLive Callback failed.

Friday, July 13, 2018 at 10:02am
0 votes
Hi Mark, Could you check the firewall at your side to see whether you have received the callback call? Because I consulted with our developers and it seems we don't have dns cache issue at our side. Duo Liang

Duo Liang OneSpan Evangelism and Partner Integrations Developer

markh

Reply to: e-SignLive Callback failed.

Friday, July 13, 2018 at 11:12am
0 votes
Hello, Thanks for your help. I was on the phone with esignlive tech support and while we stepped though the process, what ever was making their webhook call fail stopped. I hate things that fix themselves, but my guess is their DNS refreshed and were able to get to us once again. All is well. Thanks again, Mark

Hello! Looks like you're enjoying the discussion, but haven't signed up for an account.

When you create an account, we remember exactly what you've read, so you always come right back where you left off

LoginSign Up