carlt Posted July 13, 2017 Posted July 13, 2017 Hi I'm following the Webhooks guide in the wiki (using requestb.in) but the Service Manager events aren't making it into my RequestBin. I've tried the Incidents Created and Updated events. Looking at EspServerService.log the issue seems to be SSL related - 'Failed to read beginning of SSL/TLS record'. Is this a Service Manager issue? 877103 13 Jul 2017 3:37 PM error general 2876 post_http_request: ChilkatLog: SynchronousRequest: DllDate: Mar 11 2016 ChilkatVersion: 9.5.0.56 UnlockPrefix: HORNBLHttp Username: LIVENODE4:SYSTEM Architecture: Little Endian; 64-bit Language: Visual C++ 12.0 / x64 VerboseLogging: 0 domain: requestb.in port: 443 ssl: 1 httpRequest: httpVersion: 1.1 verb: POST path: /12ei3g01 contentType: text/xml; charset=utf-8; charset=utf-8 charset: utf-8 sendCharset: 0 mimeHeader: --httpRequest fullRequest: a_synchronousRequest: generateRequestHeader: httpRequestGenStartLine: genStartLine: startLine: POST /12ei3g01 HTTP/1.1 --genStartLine --httpRequestGenStartLine addCookies: Not auto-adding cookies. sendCookies: 1 cookieDir: --addCookies --generateRequestHeader fullHttpRequest: domain: requestb.in port: 443 ssl: 1 openHttpConnection: Opening connection directly to HTTP server. httpHostname: requestb.in httpPort: 443 ssl: 1 socket2Connect: connect2: connectImplicitSsl: clientHandshake: clientHandshake2: readHandshakeMessages: Failed to read beginning of SSL/TLS record. --readHandshakeMessages --clientHandshake2 --clientHandshake Client handshake failed. (3) --connectImplicitSsl ConnectFailReason: 103 --connect2 --socket2Connect connect: Socket connection closed. --openHttpConnection --fullHttpRequest success: 0 --a_synchronousRequest success: 0 --fullRequest totalTime: Elapsed time: 15 millisec Failed. --SynchronousRequest --ChilkatLog
James Ainsworth Posted July 13, 2017 Posted July 13, 2017 Hi @carlt Thanks for your post. I worked through the example with Request Bin and found I had the same message as you. It is possibly that something has changed with Request Bin or we may have added security which Request Bin doesn't adhere to. I've put the question to our developers to see if they can shed some light on this. Another test tool can be found here. I'm not so familiar with setting this up, but it might be an alternative to Request Bin. If that too doesn't work then we can look to see if it is something on our side. Regards, James
James Ainsworth Posted July 13, 2017 Posted July 13, 2017 Hi @carlt We may have found the issue in a 3rd Party tool (Chilkat). We are currently testing a newer version of Chilkat which looks like it corrects the issue. Provided the new version does not impact anything else we will look to have this updated as soon as possible. Regards, James . 2
Gerry Posted July 13, 2017 Posted July 13, 2017 @carlt Further to @James Ainsworth update, we have now rolled in the updated library we use for some comms related stuff. This will be on dev tomorrow, will make beta by Monday and should be into production in two days after that subject to testing and validation. Gerry 2
carlt Posted July 14, 2017 Author Posted July 14, 2017 OK thanks for the update @James Ainsworth and @Gerry
James Ainsworth Posted August 17, 2017 Posted August 17, 2017 Hi @carlt I just wanted to come back to this post as I've tested the Webhooks to confirm that these are now working. I just wanted to make sure that you were aware that the updates have been provided and that this should now be working for you. Regards, James
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now