WPPizza – A Restaurant Plugin for WordPress › Support › General Support › WorldPay Callback handling failed
- AuthorPosts
- 18 June, 2018 at 1:44 pm #38039
Hello Oliver, hope you are well. I need your help please. I had to switch off WorldPay plugin as majority of the orders didn’t come back to us. Normal orders work all fine, via pay by cash – all printed, emailed and in order history. With WorldPay some order go through and some are lost (we only receive the receipt of payment from WorldPay). I just got logs from 2 transactions from the WorldPay:
TRANS ID: 6265825550 – £52.70
######################################################################################################
[2018-06-16 17:52:20.185 (TID:msg2Conn19-61382)] Callback handling failed
[2018-06-16 17:52:20.181 (TID:msg2Conn19-61382)] Callback Failed: Callback to http://ristorantebarolo.co.uk/delivery/wp-content/plugins/wppizza-gateway-worldpay/ipn/ipn.php: NOT OK, recevied HTTP status: 502
[2018-06-16 17:52:20.181 (TID:msg2Conn19-61382)] MerchReq-448-48 Done.
[2018-06-16 17:52:20.181 (TID:msg2Conn19-61382)] MerchReq-448-48 <HTTP Response> Parsed: text/html
[2018-06-16 17:52:20.181 (TID:msg2Conn19-61382)] MerchReq-448-48 <HTTP Response> Received: 502: Bad Gateway
[2018-06-16 17:52:19.483 (TID:msg2Conn19-61382)] MerchReq-448-48<HTTP Request> Using proxy: localhost:3128
[2018-06-16 17:52:19.454 (TID:msg2Conn19-61382)] MerchReq-448-48<HTTP Request> Using configured proxies
[2018-06-16 17:52:19.454 (TID:msg2Conn19-61382)] MerchReq-448-48<HTTP Request> to: ristorantebarolo.co.uk
[2018-06-16 17:52:19.448 (TID:msg2Conn19-61382)] MerchReq-448-48 Starting…
[2018-06-16 17:52:19.447 (TID:msg2Conn19-61382)] LegacyPaymentTemplateConfig (inst=null): setInstallation(com.worldpay.aequitas.internal.entities.V3PPMsgConfig@6eacc256)
[2018-06-16 17:52:19.443 (TID:msg2Conn19-61382)] {INFO/AdministrationCacheSource}: Refreshing Administration STEPHANLTD
[2018-06-16 17:52:19.438 (TID:msg2Conn19-61382)] Starting callback handling
######################################################################################################TRANS ID: 7766455801 – £14.60
######################################################################################################
[2018-06-15 19:30:18.522 (TID:msg2Conn18-38081)] Callback handling failed
[2018-06-15 19:30:18.520 (TID:msg2Conn18-38081)] Callback Failed: Callback to http://ristorantebarolo.co.uk/delivery/wp-content/plugins/wppizza-gateway-worldpay/ipn/ipn.php: NOT OK, recevied HTTP status: 502
[2018-06-15 19:30:18.519 (TID:msg2Conn18-38081)] MerchReq-668-42 Done.
[2018-06-15 19:30:18.519 (TID:msg2Conn18-38081)] MerchReq-668-42 <HTTP Response> Parsed: text/html
[2018-06-15 19:30:18.519 (TID:msg2Conn18-38081)] MerchReq-668-42 <HTTP Response> Received: 502: Bad Gateway
[2018-06-15 19:30:17.682 (TID:msg2Conn18-38081)] MerchReq-668-42<HTTP Request> Using proxy: localhost:3128
[2018-06-15 19:30:17.669 (TID:msg2Conn18-38081)] MerchReq-668-42<HTTP Request> Using configured proxies
[2018-06-15 19:30:17.669 (TID:msg2Conn18-38081)] MerchReq-668-42<HTTP Request> to: ristorantebarolo.co.uk
[2018-06-15 19:30:17.668 (TID:msg2Conn18-38081)] MerchReq-668-42 Starting…
[2018-06-15 19:30:17.666 (TID:msg2Conn18-38081)] LegacyPaymentTemplateConfig (inst=null): setInstallation(com.worldpay.aequitas.internal.entities.V3PPMsgConfig@385a9d71)
[2018-06-15 19:30:17.660 (TID:msg2Conn18-38081)] {INFO/AdministrationCacheSource}: Refreshing Administration STEPHANLTD
[2018-06-15 19:30:17.656 (TID:msg2Conn18-38081)] Starting callback handling
######################################################################################################Payment Response obtained HTTP ‘502’ response
The Payment Response server-side script requested data from another server and received an error from that server.
18 June, 2018 at 1:49 pm #38040says it all right there really:
your server returns a 502 when sending things back to the script (http://ristorantebarolo.co.uk/delivery/wp-content/plugins/wppizza-gateway-worldpay/ipn/ipn.php)
this must be a 200
you need to speak to your host/server admin and/or check your server logs.
this is nothing the plugin has any control overcash on delivery orders can not ever have that issue as there’s no 3rd party involved that would need to send anything back to the server
18 June, 2018 at 3:11 pm #38043Sorry for the trouble. Think I will need to look for a different hosting company in UK very shortly. They try to play ping-pong with this (TSO HOSTING): “From what I can see, this has either to be caused by a bad plugin, incorrect PHP version or the third party might have blocked our outgoing IP. I would kindly suggest that you check with them if 91.208.99.2 is blocked as that is the cloud’s outgoing IP. All I’m saying is what can be the problem and with third parties, it’s likely that they could have blocked the outgoing IP. I would definitely check if the plugin is compatible with the newest version of wordpress as you’re using an okay PHP version which is 5.6”.
Think I will go with GODAddy
18 June, 2018 at 3:30 pm #38044i can assure you that the wppizza plugin does not block anything – that would be stupid (but some other plugins might, or your hosting company , or a firewall, or your file permissions mess things up etc etc .)
suffice to say your hosting company (or server admin) should be the ones that are able to tell you why it’s a 502. nobody else will as nobody else has access to the server logsworldpay only tells you the symptoms (and from what i can see, they are not at fault here)
they are trying to send info back to your server but the server responds with 502. they will not be able to know anything else .a personal opinion – you could do what you like of course: i would SERIOUSLY reconsider using godaddy and find some – in fact any – other host (just from experience dealing with some different sites hosted on godadday – wppizza related or not)
18 June, 2018 at 4:12 pm #38045Thanks, I’m already checking out prices at GoDaddy. Got a last response from Tsohost:
“I’ve just reviewed the server log files but wasn’t able to locate anything associated. I can also confirm that TLS1.2, OpenSSL/1.0.2a, and HTTP1.1 are supported on the server, so you should be able to process payments normally. However, I would strongly recommend you to double check your plugin configuration and if it’s forced to send the outgoing requests through TLS1.2 since most of the payment systems are rejecting lower version now. If the Worldpay Gateway’s system was updated recently and your plugin is forcing lower TLS version, that could be causing your issue.”I am also thinking I may have some plugins that may cause this problem, I turned off some of them and retest this weekend, don’t know if that would help.
18 June, 2018 at 4:21 pm #38046>….double check your plugin configuration and if it’s forced to send the outgoing requests ….bla bla bla
they fundamentally misunderstand what the problem is or how this works. the plugin does NOTHING here.
when worldpay has processed an order it sends notification *directly* to the server script – behind the scenes – to [url]/wp-content/plugins/wppizza-gateway-worldpay/ipn/ipn.php. there is no tls or any other setting involved here that the plugin (could) set
but the server responds with a 502 ….> I am also thinking I may have some plugins that may cause this problem,
of course, if other plugins block things/ip’s whatever than that might well cause an issue accessing that url18 June, 2018 at 4:39 pm #38049the thing is, a 502 could be pretty much anything
(https://kinsta.com/blog/502-bad-gateway/)
only the server logs will be able to tell you the issue
and as that script gets accessed and – most likely – throws the 502 before it executed and.or wordpress gets even loaded only the server logs will be able to shed light on thisthat’s assuming it’s not some other plugin that throws this 502 of course (or perhaps some htaccess file settings or whatnot)
if i understand you correctly , this also seems to be a recent issue you end . as the gateway has not changed for months (and does no such thing as setting or not TLS etc etc or any such thing) I would suggest the issue is elsewhere
sure, if it turns out i am wrong (although i cannot see how) i would be happy to stand corrected and fix things if needs be , but without anyone providing proof (or indeed details) to that effect, there’s nothing for me to do here from what i can see
18 June, 2018 at 4:49 pm #38050Thanks Olly for the good will. They want to resolve the issue and asked me to ask the Worldpay for the ‘outgoing IP addresses, so [they] can check for any blocks on [TSO’S] side’.
I had an exact issue like that but very rarely (on around 40 orders we had one that had an outcome like that) and that was mostly when the entire site was not able to load (error with the servers) and someone was already on WorldPay at the time to pay for the order.
And I had exactly the same 3rd party plugins as I have now. Nothing new.21 June, 2018 at 4:45 pm #38145TSOHost said Encrypt SSL will solve my problem.
Today I couldn’t make a purchase on my shop (clicking on ‘order’ did not respond)
Also I couldn’t log in to WordPress (login page was refreshing).Whoa… that’s enough for me. I’ve gone back to backup from a week before to make it work. This weekend I’ll let it go because of the customers but Monday I am looking for another hosting company 100% starting with GoDaddy.
Thanks for your time
- AuthorPosts
- The topic ‘WorldPay Callback handling failed’ is closed to new replies.