|
Hunter
|
August 4, 2017 at 3:14 pm
I am testing my event here: https://oktoberfestgermantown.com/register/
When I go to process the test payment through stripe, I get the error, “This registration step could not be completed.”
I have excluded all EE pages from cache.
I am not sure what is going on. Any ideas?
|
|
Hunter
|
August 5, 2017 at 2:31 pm
More info: It takes about a minute of the cog spinning before I get that error message. However, when I refresh, the registrations are approved and I get the event registration and payment confirmation emails.
|
|
Hunter
|
August 5, 2017 at 2:50 pm
I am also seeing this error in the console once the error appears on screen.
https://www.screencast.com/t/5FBrjbrC1
|
|
Tony
|
August 7, 2017 at 4:16 am
Hi there,
Looking at your site it looks like your event has either been removed or privately published as I can’t view it.
Can you post a link to an event I can use to test this?
|
|
Hunter
|
August 7, 2017 at 9:46 am
Hey Tony,
I can’t open the registrations because the site gets traffic enough that people try to register before it is time. Therefore, I added EE as a user. You should get an email at support.
Also, another thing I found, is that the dashboard of the site is support slow while the payment is being processed.
|
|
Josh
|
August 7, 2017 at 10:02 am
Hi Hunter,
It sounds like your host may be restricting access to the wp-admin/admin-ajax.php file, the 504 error you saw in the console also supports that idea. Here’s a similar stackexchange topic where the same thing happened:
https://wordpress.stackexchange.com/questions/106252/failed-to-load-wp-admin-admin-ajax-php
Can you contact your host to see if they are limiting access to the wp-admin/admin-ajax.php file and/or limiting the WP Heartbeat API?
|
|
Tony
|
August 7, 2017 at 10:56 am
It’s also worth taking a look at the server’s error logs to see if there are any errors from Event Espresso at the time of the payment.
I logged into your site and looked over the payment logs which look correct apart from EE being unable to identify the Payment Method and Transaction for the log (which will happen if the above is try).
|
|
Hunter
|
August 7, 2017 at 1:41 pm
Thanks guys. The host (Flywheel) increased the memory limit to 256MB and the timeout to 45 seconds. That seems to have fixed the problem.
Thanks!
|
