|
cleopatra
|
June 28, 2016 at 4:01 am
I suddenly stopped receiving booking notifications.
A quick look at EE told me the paypal payment notifications are wonky, ie not being reconised by EE. Bookings are not being marked as paid, so the system is not sending out confirmations to myself or clients.
I’ve looked at paypal settings and IPN is on and working.
If I can’t get this fixed i’ll have to kill the online booking system, as it stands it takes people money but doesn’t confirm their booking to me or the client 🙁
Any help would be awesome??
|
|
Tony
|
June 28, 2016 at 6:44 am
Hi there,
Just noting that we have received your support token request and will continue to troubleshoot this further there.
|
|
GorgeousGetaway
|
June 28, 2016 at 6:55 am
Experienced the same issue this morning with EE3 install Version 3.1.37.0.P
All was fine last night – bookings this morning aren’t responding to the paypal ipn (status = SENT). I’ve tried resending from paypal. no joy – have had to manually confirm bookings.
|
|
Tony
|
June 28, 2016 at 8:41 am
Hi there,
PayPal have been rolling out updates to their servers which now require your server supports (and uses) TLS 1.2 for HTTPS connections:
https://devblog.paypal.com/upcoming-security-changes-notice/
Can you contact your host and confirm if they support TLS 1.2? If not they will need to update the server in order for PayPal to work correctly.
|
|
GorgeousGetaway
|
June 28, 2016 at 10:33 am
Hi,
Contacted my hosting – seems i was running on php version 5.4. Need to be running on 5.5 or above for the website to use TLS 1.2. Changed it – will see if works next booking.
|
|
Josh
|
June 28, 2016 at 3:23 pm
You can also set up a PayPal sandbox account to test before the next booking comes in.
|
|
GorgeousGetaway
|
June 28, 2016 at 5:03 pm
Hi,
The change to 5.6 (and 5.7) didnt actually work instantly. I changed back to 5.5 – that didnt work (Even after resending the IPN) so i emailed hosting with more details..
Just now i received an booking approved so all seems to be working on mine now!
@Cleopatra i’m wondering if yours has started working now and whether any changes made for it to work?
My hosting company said paypal upgraded something and removed their IP from a whitelist. That may have been the reason – TLS 1.2 isn’t actually required until June 2017
|
|
GorgeousGetaway
|
June 28, 2016 at 5:17 pm
Just to further note This only started working in the past hour or so.
An IPN that came in at 22:12 didnt get to EE.
An IPN that came in at later 23:20 did get to EE and approved a booking.
I further confirmed this by resending the IPN that failed at 22:12 – that worked and the booking is now approved!
|
|
cleopatra
|
June 29, 2016 at 12:38 am
@Josh, yes one of your guys made a booking and paid via a sandbox account, all worked as it should. I put through a live booking & payment and no dice.
Having gone around in circles with Tony (EE) via premium support. At midnight last night there was no fix. He had bounced the issue to my hosting company. No clue what was wrong.
I changed the site to php5.6 (from php5.3) yesterday afternoon, also as advised by Tony “IPN encoding is set to windows-1252, normally we’d expect a different error with this but I would recommend setting that to UTF-8 within your PayPal account anyway”.
This morning, i check the system with a live booking and payment and all is working as it should.
So to anyone else in this position, I have no idea what fixed it, if indeed it needed fixing etc. but we’re back in business 🙂
|
|
Tony
|
June 29, 2016 at 3:24 am
He had bounced the issue to my hosting company. No clue what was wrong.
Whilst I understand where your coming from, that isn’t what I said.
The connection to PayPal to validate the IPN returned ‘403 Forbidden’ which means the connection was refused, so either the connection was blocked by your host or refused by PayPal.
I requested to confirm with your host that the connection was not being blocked by your host before moving onto PayPal as I had checked over your site config and could find no issue there, nor any issue with the request being made.
I suspect this was an issue with PayPal rather than your host, it doesn’t make sense for the validations to randomly start working again with no other changes, either way I’m glad it’s now working 🙂
@GorgeousGetaway
Could I take a look at your ipn logs on your site? I’ll need FTP access to your serer to take a look, if that’s ok can you send login details using this form:
https://eventespresso.com/send-login-details/
I’d like to confirm if your issue was the same as Cleopatra’s.
|
|
cleopatra
|
June 29, 2016 at 3:32 am
@Tony Not a dig at you at all, you did an awesome job. You had a jolly good dig around, investigating and testing. You did bounce it to my host, and rightly so as the fault wasn’t with EE.
“No clue what was wrong” was meant as ‘I have no clue what was wrong’. Apologies for any misunderstanding and thanks for your support 🙂
|
|
Josh
|
June 29, 2016 at 12:21 pm
TLS 1.2 isn’t actually required until June 2017
It’s actually the requirement for SHA-256 based certificates that’s being rolled out first:
https://devblog.paypal.com/upcoming-security-changes-notice/
|
