|
sweetrose500
|
August 11, 2017 at 8:26 am
Hi – using Stripe with EE4.
The stripe transaction processes and I get the confirmation.
Screenshot: http://imgur.com/a/QsMVQ
Issues:
* Yellow box has no text in it. Gear continues to spin. Box changes to red. No text.
* Never get sent to the confirmation page.
* On the admin side, even though I have the event set to auto approve, the registrant is still “pending”.
Are these upstream errors related at all?
2017/08/11 14:11:03 [error] 16339#16339: *46501 upstream timed out (110: Connection timed out)
2017/08/11 14:11:08 [error] 16339#16339: *46505 upstream timed out (110: Connection timed out)
2017/08/11 14:11:08 [error] 16339#16339: *46509 upstream timed out (110: Connection timed out)
Also seeing this in my slow error log –>
[11-Aug-2017 14:14:19]
script_filename = /www//wp-admin/admin-ajax.php
[0x00007fb3720132d0] curl_exec() /www/wp-includes/Requests/Transport/cURL.php:162
[0x00007fb372013210] request() /www/wp-includes/class-requests.php:379
[0x00007fb372013110] request() /www/wp-includes/class-http.php:371
[0x00007fb372012f80] request() /www/wp-includes/class-http.php:612
[0x00007fb372012ee0] get() /www/wp-includes/http.php:170
[0x00007fb372012e50] wp_remote_get() /www/wp-content/plugins/event-espresso-core-reg/core/libraries/messages/EE_Messages_Scheduler.lib.php:109
[0x00007fb372012da0] initiate_scheduled_non_blocking_request() /www/wp-content/plugins/event-espresso-core-reg/core/libraries/messages/EE_Messages_Queue.lib.php:461
[0x00007fb372012cf0] initiate_request_by_priority() /www/wp-content/plugins/event-espresso-core-reg/core/libraries/messages/EE_Messages_Processor.lib.php:465
[0x00007fb372012c50] generate_for_all_active_messengers() /www/wp-content/plugins/event-espresso-core-reg/modules/messages/EED_Messages.module.php:421
[0x00007fb372012b80] payment() /www/wp-includes/class-wp-hook.php:298
[0x00007fb372012aa0] apply_filters() /www/wp-includes/class-wp-hook.php:323
[0x00007fb372012a30] do_action() /www/wp-includes/plugin.php:453
[0x00007fb372012920] do_action() /www/wp-content/plugins/event-espresso-core-reg/core/EE_Payment_Processor.core.php:498
[0x00007fb372012840] update_txn_based_on_payment() /www/wp-content/plugins/event-espresso-core-reg/core/EE_Payment_Processor.core.php:134
[0x00007fb372012720] process_payment() /www/wp-content/plugins/event-espresso-core-reg/modules/single_page_checkout/reg_steps/payment_options/EE_SPCO_Reg_Step_Payment_Options.class.php:2101
[0x00007fb372012670] _attempt_payment() /www/wp-content/plugins/event-espresso-core-reg/modules/single_page_checkout/reg_steps/payment_options/EE_SPCO_Reg_Step_Payment_Options.class.php:1744
[0x00007fb3720125d0] _process_payment() /www/wp-content/plugins/event-espresso-core-reg/modules/single_page_checkout/reg_steps/payment_options/EE_SPCO_Reg_Step_Payment_Options.class.php:1610
[0x00007fb372012520] process_reg_step() /www/wp-content/plugins/event-espresso-core-reg/modules/single_page_checkout/EED_Single_Page_Checkout.module.php:1367
[0x00007fb372012480] _process_form_action() /www/wp-content/plugins/event-espresso-core-reg/modules/single_page_checkout/EED_Single_Page_Checkout.module.php:524
[0x00007fb372012400] _initialize() /www/wp-content/plugins/event-espresso-core-reg/modules/single_page_checkout/EED_Single_Page_Checkout.module.php:141
[11-Aug-2017 14:14:24]
script_filename = /www//index.php
[0x00007fb3720165a0] curl_exec() /www/wp-includes/Requests/Transport/cURL.php:162
[0x00007fb3720164e0] request() /www/wp-includes/class-requests.php:379
[0x00007fb3720163e0] request() /www/wp-includes/class-http.php:371
[0x00007fb372016250] request() /www/wp-includes/class-http.php:612
[0x00007fb3720161b0] get() /www/wp-includes/http.php:170
[0x00007fb372016120] wp_remote_get() /www/wp-content/plugins/event-espresso-core-reg/core/libraries/messages/EE_Messages_Scheduler.lib.php:109
[0x00007fb372016070] initiate_scheduled_non_blocking_request() /www/wp-content/plugins/event-espresso-core-reg/core/libraries/messages/EE_Messages_Queue.lib.php:461
[0x00007fb372015fc0] initiate_request_by_priority() /www/wp-content/plugins/event-espresso-core-reg/core/libraries/messages/EE_Messages_Processor.lib.php:128
[0x00007fb372015f30] batch_generate_from_queue() /www/wp-content/plugins/event-espresso-core-reg/modules/messages/EED_Messages.module.php:274
[0x00007fb372015e90] run_cron() /www/wp-content/plugins/event-espresso-core-reg/modules/messages/EED_Messages.module.php:242
[0x00007fb372015e30] execute_batch_request() /www/wp-content/plugins/event-espresso-core-reg/core/EE_Module_Request_Router.core.php:220
[0x00007fb372015d90] _module_router() /www/wp-content/plugins/event-espresso-core-reg/core/EE_Module_Request_Router.core.php:173
[0x00007fb372015cc0] resolve_route() /www/wp-content/plugins/event-espresso-core-reg/core/EE_Front_Controller.core.php:246
[0x00007fb372015c00] pre_get_posts() /www/wp-includes/class-wp-hook.php:298
[0x00007fb372015b20] apply_filters() /www/wp-includes/class-wp-hook.php:323
[0x00007fb372015ab0] do_action() /www/wp-includes/plugin.php:515
[0x00007fb3720159f0] do_action_ref_array() /www/wp-includes/class-wp-query.php:1683
[0x00007fb372015320] get_posts() /www/wp-includes/class-wp-query.php:3248
[0x00007fb3720152a0] query() /www/wp-includes/class-wp.php:617
[0x00007fb372015230] query_posts() /www/wp-includes/class-wp.php:735
|
|
Josh
|
August 11, 2017 at 8:49 am
Hi there,
May I ask what’s the URL of your site’s Thank you page set in Event Espresso > General Settings > Critical pages?
|
|
sweetrose500
|
August 11, 2017 at 8:50 am
Sure, it’s https://www.nacephilly.com/thanks-for-your-purchase/
It shows “page status OK” in the admin side.
|
|
Josh
|
August 11, 2017 at 9:17 am
Would you be able to run the same test with the default WP theme temporarily activated along with all other plugins deactivated?
|
|
sweetrose500
|
August 11, 2017 at 9:39 am
I did it with the default theme – the text in the boxes after entering credit card info did show up – first the yellow box – then the red box – however, the transaction did complete as before.
Didn’t try with plugins disabled yet. Will do that next. Any ideas in the meantime?
|
|
Josh
|
August 11, 2017 at 9:50 am
The other theme is likely hiding the notifications text with some CSS.
|
|
sweetrose500
|
August 11, 2017 at 11:36 am
Ok, tried it with plugins disabled and still had the issue.
I continue to get the email confirmation and the transactions still are getting processed.
I did try it with a coupon code for a 100% discount. When I did this, the system read the discount and went right to the thank you page – no issue – but of course no payment was processed.
|
|
Josh
|
August 11, 2017 at 11:53 am
Two things you can check/change:
1) Check to see what’s returned for “remote_posting” on the Event Espresso > Maintanance > System Information page
2) You can go to Event Espresso > Messages > Settings and set the messages to send on a separate request. This will help if there are any bottlenecks happening during the final step of the checkout when the payment response is captured.
|
|
sweetrose500
|
August 11, 2017 at 11:55 am
1) Your server has fsockopen and cURL enabled.
2) It’s already set to “separate request”
|
|
Josh
|
August 11, 2017 at 11:58 am
Can you check the browser’s console for errors when the spinning gear doesn’t stop?
|
|
sweetrose500
|
August 11, 2017 at 12:40 pm
See linked –> http://imgur.com/a/naDYt
|
|
sweetrose500
|
August 11, 2017 at 12:50 pm
I cleared that message and it didn’t fix it.
|
|
Josh
|
August 11, 2017 at 1:20 pm
That doesn’t look like an error. Can you try activating WP_DEBUG? You can set it to log errors only by following this guide:
https://codex.wordpress.org/Debugging_in_WordPress#Example_wp-config.php_for_Debugging
Also, you can get the logs that get recorded for each transaction’s payments in Event Espresso > Payment Methods > Logs. It will likely not have errors there, but if there is an error related to the Stripe API they may get logged there.
|
|
sweetrose500
|
August 11, 2017 at 1:41 pm
Log files –> https://www.dropbox.com/s/mlbxmfkrnunuans/Logs.zip?dl=0
Thanks.
|
|
Josh
|
August 11, 2017 at 1:52 pm
Those logs were’nt what I was referring to, but since there are a number of (110: Connection timed out) errors logged there, you can try the solutions posted here:
https://www.tekovic.com/fixing-timeout-between-nginx-and-php-fpm
https://distinctplace.com/2017/04/22/nginx-upstream-timed-out/
|
|
sweetrose500
|
August 11, 2017 at 4:09 pm
I use Flywheel for hosting and went back to them. Here’s what they told me:
I just tried a transaction like you suggested, and I’m seeing the issue just as you describe. However, it doesn’t look like there’s much we can do about it on our end. I did bump the timeout up a little more, but the root issue is: the Event Espresso plugin is just doing _something_ that is either exceptionally inefficient or that requires far too much memory.
Given that this site is on a Tiny plan, already has maximum cache settings and now a timeout significantly above the normal settings, I’m afraid our only recommendation is to work with the plugin’s support and/or a developer to figure out what the hangup is with that process. I do have an example of the error from the site’s logs, which I’ll include at the end of the email, if that’s helpful.
Sorry we can’t be more directly helpful than that, but hopefully that gets you pointed in a helpful direction at least. Let us know if you have any questions or if we can help with anything else in the meantime.
Here are the errors I mentioned (the first from the slow_error logs, the second from the error log):
[11-Aug-2017 21:58:08] [pool site-124731] pid 23404
script_filename = /www//index.php
[0x00007fcf494135a0] curl_exec() /www/wp-includes/Requests/Transport/cURL.php:162
[0x00007fcf494134e0] request() /www/wp-includes/class-requests.php:379
[0x00007fcf494133e0] request() /www/wp-includes/class-http.php:371
[0x00007fcf49413250] request() /www/wp-includes/class-http.php:612
[0x00007fcf494131b0] get() /www/wp-includes/http.php:170
[0x00007fcf49413120] wp_remote_get() /www/wp-content/plugins/event-espresso-core-reg/core/libraries/messages/EE_Messages_Scheduler.lib.php:109
[0x00007fcf49413070] initiate_scheduled_non_blocking_request() /www/wp-content/plugins/event-espresso-core-reg/core/libraries/messages/EE_Messages_Queue.lib.php:461
[0x00007fcf49412fc0] initiate_request_by_priority() /www/wp-content/plugins/event-espresso-core-reg/core/libraries/messages/EE_Messages_Processor.lib.php:128
[0x00007fcf49412f30] batch_generate_from_queue() /www/wp-content/plugins/event-espresso-core-reg/modules/messages/EED_Messages.module.php:274
[0x00007fcf49412e90] run_cron() /www/wp-content/plugins/event-espresso-core-reg/modules/messages/EED_Messages.module.php:242
[0x00007fcf49412e30] execute_batch_request() /www/wp-content/plugins/event-espresso-core-reg/core/EE_Module_Request_Router.core.php:220
[0x00007fcf49412d90] _module_router() /www/wp-content/plugins/event-espresso-core-reg/core/EE_Module_Request_Router.core.php:173
[0x00007fcf49412cc0] resolve_route() /www/wp-content/plugins/event-espresso-core-reg/core/EE_Front_Controller.core.php:246
[0x00007fcf49412c00] pre_get_posts() /www/wp-includes/class-wp-hook.php:298
[0x00007fcf49412b20] apply_filters() /www/wp-includes/class-wp-hook.php:323
[0x00007fcf49412ab0] do_action() /www/wp-includes/plugin.php:515
[0x00007fcf494129f0] do_action_ref_array() /www/wp-includes/class-wp-query.php:1683
[0x00007fcf49412320] get_posts() /www/wp-includes/class-wp-query.php:3248
[0x00007fcf494122a0] query() /www/wp-includes/class-wp.php:617
[0x00007fcf49412230] query_posts() /www/wp-includes/class-wp.php:735
2017/08/11 21:58:45 [error] 21567#21567: *1427 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 63.227.151.128, server: http://www.nacephilly.com, request: “POST /wp-admin/admin-ajax.php HTTP/1.0”, upstream: “fastcgi://unix:/tmp/site-124731.sock”, host: “www.nacephilly.com”, referrer: “https://www.nacephilly.com/registration-checkout/?uts=1502488525”
|
|
sweetrose500
|
August 11, 2017 at 5:14 pm
Also, everything in the transaction logs is successful.
|
|
sweetrose500
|
August 13, 2017 at 3:24 am
Hi team – let me know what I can try next. I spent time going through other support requests and don’t see any problems like the one I’m experiencing … and I need to get it resolved ASAP.
Again, transaction still being processed fine but users aren’t directed to the thank you screen.
|
|
Tony
|
August 14, 2017 at 3:39 am
Hi there,
If you go to Event Espresso -> Messages, you’ll be on the message activity tab.
Do you have a lot of messages sitting waiting to send? (Blue status bar)
The setting that Josh recommend setting to ‘on separate request’:
You can go to Event Espresso > Messages > Settings and set the messages to send on a separate request. This will help if there are any bottlenecks happening during the final step of the checkout when the payment response is captured.
Test what happens if that setting is set to ‘on same request’.
What I suspect from the above is the server is choking when trying to generate/send a batch of emails within the message queue so lets see if the above works before moving forward.
|
|
sweetrose500
|
August 14, 2017 at 3:45 am
Hi Tony – all of the messages are green. The only transactions I’ve tested are the ones I’ve been testing – there’s been no volume through the site so far.
I just tested setting it to “same request” and THE PAYMENT COMPLETED!!!!! HOORAY!!!!!!!
I am going to test a little more today just to confirm, so let’s leave the case open for the moment, but I am very encouraged!
|
|
Tony
|
August 14, 2017 at 5:13 am
Ok, so sounds like something is going on when EE is using wp_cron on your site.
all of the messages are green.
Are they all payment related messages? ‘Payment received’ for example?
You mentioned your getting the confirmation emails, is that all of them, payment and registration?
I just tested setting it to “same request” and THE PAYMENT COMPLETED!!!!! HOORAY!!!!!!!
Great, but the strange part of that is the ‘on separate request’ setting was designed to reduce the load on the server during the registrations. What it does is add any messages that need to be sent to the message queue, the message queue uses wp_cron to work through batches of messages to generate then send them in batches.
The ‘on same request’ setting does all of that on the request before redirecting to the thank you page. So if you select 20 tickets EE may needs to update the transaction/registrations, then generate 20 individual registration messages, (plus others depending on setup but keeping the numbers easy) then send those 20 messages, then direct you to the thank you page which all takes time and resources.
Some message types (such as payment related messages) skip that and instant send as they are considered high prioirty which is why I’m asking about the specific message types above.
|
|
sweetrose500
|
August 14, 2017 at 5:44 am
Hi Tony – yes, all of the messages are green and payment-related –> all of them are “Payment Received”.
Is there anything I can look @ re: wp_cron or specifically ask of my hosting company (Flywheel) settings-wise?
|
|
Tony
|
August 14, 2017 at 7:41 am
Ok, 2 things to test.
Set the option back to ‘on separate request’ and add a registration using an offline payment method, finalize so you should get to the thank you.
Does it load and do the registration emails send?
Then install the WP Crontrol plugin and go to Tools -> Cron Events.
Does it mention that Cron is disabled?
Can you see a list of ‘events’ there? – http://take.ms/ID83b
|
|
sweetrose500
|
August 14, 2017 at 7:49 am
Hi Tony – earlier in testing I had tried testing by using a discount code that was 100% – the transaction went through fine and I got the confirmation.
Screenshot attached of the Cron. It’s active.
–> http://imgur.com/a/bFA9s
|
|
Tony
|
August 14, 2017 at 8:01 am
Earlier in testing I had tried testing by using a discount code that was 100% – the transaction went through fine and I got the confirmation.
That’s not the same test, you need to test a paid registration using a payment method, Free registrations (like when using 100% discount codes) don’t use payment methods.
I’m testing the payment method step is finalizing the registration and triggering messages when a payment method is selected, you have the default registration status set to Approved on your events so it’s a similar test but not the same path.
Screenshot attached of the Cron. It’s active
Ok, great.
|
|
sweetrose500
|
August 14, 2017 at 8:05 am
Just checked the check payment as described – it went through with no problem.
|
|
Tony
|
August 14, 2017 at 10:16 am
Hmm, and that was with the messages set to on separate request, right?
|
|
sweetrose500
|
August 14, 2017 at 10:23 am
Correct, yes.
|
