fevieiraleite's account

Thanks for the quick response, Michael. I'll be waiting for further information. Fernando

I'm pretty sure our API is open for any IP but I'll make sure. Can you confirm which IP address it would come from? The answer on that ticket doesn't cover the version we're using. We're using "apps.e-signlive.com". Fernando

Michael, I checked with our server provider and I was told that the IP is already whitelisted for inbound traffic. I asked them to also allow for outbound but I don't think this will change anything since it seems like the issue is that eSignLive can't hit our API. Regarding using SSL, I don't think we do, but how can I make sure? I know that we can communicate with eSignLive from our application, like creating packages, signing, etc. And yes, I can visit apps.e-signlive.com from a browser on the new server.

Yeah, allowing outbound traffic didn't work. Is there nothing you guys can check from your servers to see what's going on when it's trying to reach our API? Maybe you guys need to allow outbout traffic to our new IP?

Thanks Michael. I set up an email.callbackfailure and got the following message: Failed to communicate with the callback server. URL: https://api.boardbookit.com/api/esignlive_notification/events Payload: {"@class":"com.silanis.esl.packages.event.ESLProcessEvent","name":"PACKAGE_CREATE","sessionUser":"2MsyYXEfLY0E","packageId":"b66bb128-2e63-4fd5-acdc-318241a590b7","message":null,"documentId":null}