Michael Posted June 26, 2015 Report Posted June 26, 2015 I had a client report to me he had a lot of payment received emails and they are recorded in the client mail log. I told him I would monitor the other customers and see if it was a bug or if it was just his account. I then had another customer getting them, they didn't contact me but I got them on my side. And in the client mail log they also had one after another at different times. Nothing in the cron jobs is stuck, and nothing looks odd to me. It's also recorded in the gateway logs with the same information. I believe it's related to: http://www.blesta.com/forums/index.php?/topic/4356-paypal-transactions-not-recorded-invoice-stays-open/#entry34934 so I've linked this thread there. For now Paul said to disable the non merchant emails if you get the same issue as me. Settings > Company > Emails > Email templates > Payment Received (Non-Merchant) > Edit > untick Enable. After investigation we believe it's not a Blesta bug as payments go threw but a PayPal IPN issue. I've contacted PayPal technical support @ https://ppmts.custhelp.com/ Quote
serge Posted June 27, 2015 Report Posted June 27, 2015 Just an other idea, if blesta do not give HTTP 200 status code when Paypal send first IPN, so paypal is re-trying later IPN during about 4 days I think. You may check your nginx/apache webserver log to know what was the returned HTTP status code or check also error log for webserver Quote
Adam Posted June 27, 2015 Report Posted June 27, 2015 Mike, Check the PayPal IPN history page: https://www.paypal.com/us/cgi-bin/webscr?cmd=_display-ipns-history (Profile -> Profile & Settings -> My Selling tools on the left hand side -> Instant payment notifications -> IPN History Page). That will show you the payload that PayPal sent, and the respond back it got from the server. /adam Quote
Michael Posted June 27, 2015 Author Report Posted June 27, 2015 Just an other idea, if blesta do not give HTTP 200 status code when Paypal send first IPN, so paypal is re-trying later IPN during about 4 days I think. You may check your nginx/apache webserver log to know what was the returned HTTP status code or check also error log for webserver We checked the apache logs and no 302 was found just 200. Mike, Check the PayPal IPN history page: https://www.paypal.com/us/cgi-bin/webscr?cmd=_display-ipns-history (Profile -> Profile & Settings -> My Selling tools on the left hand side -> Instant payment notifications -> IPN History Page). That will show you the payload that PayPal sent, and the respond back it got from the server. /adam Correct we found it there that it's just not giving up so I've contacted PayPal technical support to find out why Quote
Paul Posted June 29, 2015 Report Posted June 29, 2015 Mike, have you had this happen again to any more users or is it still just the 2? Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.