node.js - PayPal IPN Handshake fails. IPN was not sent, and the handshake was not verified. Please review your information -


this not duplicate issue have read through of this , this , more.

i have setup elb on amazon test ipn ipn simulator

then have verified ssl certificates:

openssl s_client -connect payments-staging.******.com:443 connected(00000003) depth=3 c = se, o = addtrust ab, ou = addtrust external ttp network, cn = addtrust external ca root verify error:num=19:self signed certificate in certificate chain verify return:0 --- certificate chain  0 s:/ou=domain control validated/ou=positivessl wildcard/cn=*.buddybid.com    i:/c=gb/st=greater manchester/l=salford/o=comodo ca limited/cn=comodo rsa domain validation secure server ca  1 s:/c=gb/st=greater manchester/l=salford/o=comodo ca limited/cn=comodo rsa domain validation secure server ca    i:/c=gb/st=greater manchester/l=salford/o=comodo ca limited/cn=comodo rsa certification authority  2 s:/c=gb/st=greater manchester/l=salford/o=comodo ca limited/cn=comodo rsa certification authority    i:/c=se/o=addtrust ab/ou=addtrust external ttp network/cn=addtrust external ca root  3 s:/c=se/o=addtrust ab/ou=addtrust external ttp network/cn=addtrust external ca root    i:/c=se/o=addtrust ab/ou=addtrust external ttp network/cn=addtrust external ca root --- server certificate -----begin certificate----- miifujccbdqgawibagirai7nmzktnqcw0stxqgmb53iwdqyjkozihvcnaqelbqaw gzaxczajbgnvbaytakdcmrswgqydvqqiexjhcmvhdgvyie1hbmnozxn0zxixedao bgnvbactb1nhbgzvcmqxgjaybgnvbaoteunptu9etybdqsbmaw1pdgvkmtywnayd vqqdey1dt01pre8gulnbiervbwfpbibwywxpzgf0aw9uifnly3vyzsbtzxj2zxig q0ewhhcnmtuwota5mdawmdawwhcnmtgwote2mjm1otu5wjbbmsewhwydvqqlexhe b21haw4gq29udhjvbcbwywxpzgf0zwqxhtabbgnvbastffbvc2l0axzlu1nmifdp bgrjyxjkmrcwfqydvqqdda4qlmj1zgr5ymlklmnvbtccasiwdqyjkozihvcnaqeb bqadggepadccaqocggebamklbacsonr9yst31olo6sqw+7zxni6upk8vnezlfnue nusfska7fcc78dstqagqebcigsci4gqupin0w8oowtd13w047ux7o9hqp+jhcpwr ejppwu4y0xa5pch6ij4e2uiyycqxtda3upgcfijbeo4e5m81txwozddo7q6l9+js 3bwhnj9yvz+ejflfxgrp1nhvtjce+bjeuc/wgoppwgwqtwalfqd4zfwa4ckowvzt k8vnmpp8gzjoo8qfzfhmos1dbhhemxapup9ex8ljaxhgq3a0snhxflci5mnaeva9 /pwfwdhy9bx8zzv8wssbka0qpkpyimnz/v9yd+0kvoecaweaaaocadkwgghvmb8g a1udiwqymbaafjcvajquwgvykoosvnpfq7q6knrnmb0ga1uddgqwbbrfnzibvfgb 4po2yikl8kqnao3ulzaobgnvhq8baf8ebamcbaawdaydvr0taqh/baiwadadbgnv hsuefjaubggrbgefbqcdaqyikwybbquhawiwtwydvr0gbegwrja6bgsrbgeeabix aqicbzarmckgccsgaqufbwibfh1odhrwczovl3nly3vyzs5jb21vzg8uy29tl0nq uzaibgzngqwbagewvaydvr0fbe0wszbjoeegryzdahr0cdovl2nybc5jb21vzg9j ys5jb20vq09nt0rpulnbrg9tywluvmfsawrhdglvblnly3vyzvnlcnzlcknblmny bdcbhqyikwybbquhaqeeetb3me8gccsgaqufbzachknodhrwoi8vy3j0lmnvbw9k b2nhlmnvbs9dt01pre9su0feb21haw5wywxpzgf0aw9uu2vjdxjlu2vydmvyq0eu y3j0mcqgccsgaqufbzabhhhodhrwoi8vb2nzcc5jb21vzg9jys5jb20wjwydvr0r bcawhoioki5idwrkewjpzc5jb22cdgj1zgr5ymlklmnvbtanbgkqhkig9w0baqsf aaocaqeaai/pz2pchz2qu+rsu7jk8vqcobzw0zkbf+h9qn6cae0ndgyt3wztv7d+ jjtgg/goztsbmf59iw2cocr61/ct7rievinouq7icvc3r80jfzw3adre3q0g0nku xddtxlbonwr78ytt6xh6ijke+eiwrlcs5zln6r7kqgsksbak2ndd/rcysge0iryd meuxh7vnudcxvwad5jfy1o9zp4zgyud1iwujfd02bykmehfruzkrye4ven5sowyv lo6bkcdaf7voj/gcsoxazgl3i2w7j6ojhpxbc70jed2h/hjpngklu+frx0e+onhl okgf7h/t+jjkypgcyfqryosuhwklfg== -----end certificate----- subject=/ou=domain control validated/ou=positivessl wildcard/cn=*.*****.com issuer=/c=gb/st=greater manchester/l=salford/o=comodo ca limited/cn=comodo rsa domain validation secure server ca --- no client certificate ca names sent --- ssl handshake has read 6059 bytes , written 421 bytes --- new, tlsv1/sslv3, cipher ecdhe-rsa-aes128-gcm-sha256 server public key 2048 bit secure renegotiation supported compression: none expansion: none ssl-session:     protocol  : tlsv1.2     cipher    : ecdhe-rsa-aes128-gcm-sha256     session-id: 7490afbbc42cf60a6b44d760a2fb977d768d13db78515d0c54081e979397e47d     session-id-ctx:     master-key: 583a2d57ef3339b97e37e17cfa0e3a17173ff3b3bb97231477acdd97d2cc02886a6b04b21dc3109e5b4be0913ed79145     key-arg   : none     psk identity: none     psk identity hint: none     srp username: none     tls session ticket lifetime hint: 300 (seconds)     tls session ticket:     0000 - 90 4a 48 33 b9 ff 8a 5c-a9 cd 2a 79 89 38 7b 7c   .jh3...\..*y.8{|     0010 - 91 62 72 de 8f 1e 57 b3-98 99 70 69 35 96 a7 f8   .br...w...pi5...     0020 - c5 26 1b eb 59 75 63 9c-c6 1b b4 91 5f a0 70   .&..yuc......_.p     0030 - fd 6e c4 fc 6e 25 7d d7-7d 51 9f 5e 22 03 1a 91   .n..n%}.}q.^"...     0040 - a2 ec 42 73 48 e4 e4 70-5d 1a 10 b9 38 d3 60 c9   ..bsh..p]...8.`.     0050 - 9e 42 47 d4 02 dc a5 91-75 c6 b8 80 27 32 ce 52   .bg.....u...'2.r     0060 - 26 85 56 eb 46 d5 a2 be-a9 1e 74 17 05 84 b0 fb   &.v.f.....t.....     0070 - cb 34 06 b4 02 d7 a3 0b-76 21 78 c8 2d b3 e3 6a   .4......v!x.-..j     0080 - 7e 57 52 7e d7 32 6d 76-0c 50 00 bd 79 aa 3a e3   ~wr~.2mv.p..y.:.     0090 - 20 7d 27 96 97 d9 ea 3d-67 54 b9 f4 bf d8 f2 b6    }'....=gt......      start time: 1453929662     timeout   : 300 (sec)     verify return code: 19 (self signed certificate in certificate chain) --- closed

then went , validated ciphers/security via ssllabs.com this results (a) sent.

and yet no ipn

i have spent 2 days on issue , appreciate if can shine light on this. frustrating , funny enough paypal using stackoverflow ticketing system find lame can't expose here business information.

i'm sure there must lot of people out there has same issue.


Comments

Post a Comment

Popular posts from this blog

authentication - Mongodb revoke acccess to connect test database -

i have ec2 instance mongodb 3.2.0 installed. have user admin access. can connect user , perform operation remotely. 1 can connect database test remote if knows ip mongo 11.11.11.11. although not able make operations, want restrict access user credentials can connect server. first need create users , grant roles users, example: use admin db.createuser( { user: "myuseradmin", pwd: "abc123", roles: [ { role: "useradminanydatabase", db: "admin" } ] } ) then need start server --auth parameter mongod --auth more information here
Read more

r - Update two sets of radiobuttons reactively - shiny -

i have read ( how make choices in radiobuttons reactive in shiny? ) shows me how update radiobutton s in reactive way. however, when try , update 2 sets of buttons same data, 1 set renders. example: server: # create example data wafer <- rep(c(1:3), each=3) length <- c(1,1,2,1,1,1,3,5,1) width <- c(3,1,6,1,1,1,1,1,6) dd <- data.frame(wafer, length, width) shinyserver(function(input, output, session){ # create reactive dataframe store data values <- reactivevalues() values$df <- data.frame() # lengths , widths of wafer user input <- eventreactive(input$do, { subset(dd, wafer %in% input$wafer, select = length:width) }) # update reactive data frame lengths , widths have been selected user input observe({ if(!is.null(a())) { values$df <- rbind(isolate(values$df), a()) } }) output$wl <- renderdatatable({ a() }) # update radio buttons unique length , widths stored in values$df # ever "observe" put first in co...
Read more

ios - Realm over CoreData should I use NSFetchedResultController or a Dictionary? -

i'm working on app using core data , nsfetchedresultcontroller many reasons switch use realm. saw there "realm version" of nsfetchedresultcontroller on github wouldn't compatible current code using core data. the view controller displaying list of people same school, address book. list sublist of people studied in same city. so thinking make 1 unique request database retrieve list of people , filter locally list within 1 dictionary per school [string: anyobject] string section name within tableview , anyobject array of people. first solution, make nsfetchedresultcontroller each school predicate filtering location. delete actions etc.. handled delegates -> not compatible realm create dictionaries , update them each actions... -> works realm it's annoying code. any better solution? edit: i need clarify request: i'd write class inherit uitableviewcontroller. this class has list of people sorted in alphabetical order the tableview has ...
Read more