Support

Home Forums Event Espresso Premium Finalizing registration has begun resulting in a 403 error on our site.

Finalizing registration has begun resulting in a 403 error on our site.

Posted: October 6, 2014 at 1:20 am

Viewing 9 reply threads


benjamin b

October 6, 2014 at 1:20 am

Customers buying tickets and selecting Paypal (we’re using Paypal Standard) are no longer getting forwarded to Paypal. Upon selecting the only option of Paypal and clicking “Finalize Registration” the popup with the gear spinning and the message “Please wait while we process your registration.
Do not refresh the page or navigate away while this is happening.
Thank you for your patience.” just stays stuck indefinitely. If the customer then follows this message at the bottom of the screen:
“If you are not automatically redirected to the payment website within 10 seconds…” and clicks on “Click Here” then it forwards them to this page:

http://worldvegansummit.com/registration-checkout/?action=espresso_process_payment_options&next_step=finalize_registration&e_reg_url_link&revisit&selected_gateway=Paypal_Standard&rm=2&cmd=_cart&item_name_1=GREENLEVEL/INCLUDINGMEALS350+taxforWorldVeganSummit&Expo-AttendeeRegistration&amount_1=350&quantity_1=1&item_name_2=MarinadelRayLACountySalesTax&amount_2=31.5&quantity_2=1&business=registrationsworldvegansummit.com&return=http://worldvegansummit.com/thank-you/?e_reg_url_link=1-bd4ffade2df27b5b629bd83f56f926b7&cancel_return=http://worldvegansummit.com/registration-cancelled/&notify_url=http://worldvegansummit.com/transactions/?e_reg_url_link=1-bd4ffade2df27b5b629bd83f56f926b7&ee_gateway=Paypal_Standard&upload=1&currency_code=USD&image_url=https://gator1841.hostgator.com/~gvr/images/paypal-style/GVR-WVS-PAYPAL-REGISTRATION-HEADER.png&no_shipping_=1&ee=_register&step=finalize_registration

And results in a “ERROR 403 – FORBIDDEN” on Host Gator. Just discovered this today when someone reported it, not sure how long it has been happening. I can’t seem to spot any errors in the log files. The last successful registration was on September 27th which was after we had updated to the latest version (4.4.3.p) on September 24th. Any ideas what might be causing this?


Lorenzo Orlando Caum

  • Support Staff

October 6, 2014 at 11:19 am

Hi, could you check with Host gator to see if they have recently made any changes to your site?

Or have you recently installed an security plugins?


Lorenzo


benjamin b

October 7, 2014 at 5:39 pm

Here is what hostgator replied with when I inquired as to the 403 error:

We appreciate your detailed explanation as to what was occurring. After some further investigation it appears that there was a plugin that was causing you to hit a mod_sec rule in Apache:

[Tue Oct 07 12:37:52 2014] [error] [client 192.185.1.20] ModSecurity: Access denied with code 403 (phase 2). Match of “rx (/wp-content/plugins/one-click-plugin-updater)|(/wp-content/plugins/mapquest-map-builder/tinymce/callback.htm)|(www/delivery/ajs.php)|(www/admin/dashboard.php)|(/pl/download\\\\?file=http|/index\\\\.php/admin/system_config/save/section/payment/|^/b/ss/mxma …” against “REQUEST_FILENAME” required. [file “/opt/mod_security/hg_rules.conf”] [line “997”] [id “1234234”] [msg “JITP:1234234-RFI-REQUEST_FILENAME=gator1841.hostgator.com”] [hostname “worldvegansummit.com”] [uri “/registration-checkout/”] [unique_id “VDQk8MC5DJ4AAD8tXxwAAACq”]

However, after whitelisting the 1234234 rule, the Event Espresso plugin threw a Fatal uncaught exception error:

Fatal error: Uncaught exception ‘EE_Error’ with message ‘Could not find a valid primary registration for this transaction’ in /home/vegan/public_html/worldvegansummit.com/wp-content/plugins/event-espresso-core-reg/core/db_models/EEM_Gateways.model.php:842 Stack trace: #0 /home/vegan/public_html/worldvegansummit.com/wp-content/plugins/event-espresso-core-reg/core/db_models/EEM_Gateways.model.php(797): EEM_Gateways->_get_return_page_url(Object(EE_Transaction)) #1 /home/vegan/public_html/worldvegansummit.com/wp-content/plugins/event-espresso-core-reg/modules/single_page_checkout/EED_Single_Page_Checkout.module.php(1722): EEM_Gateways->process_payment_start(Object(EE_Line_Item), Object(EE_Transaction)) #2 /home/vegan/public_html/worldvegansummit.com/wp-content/plugins/event-espresso-core-reg/modules/single_page_checkout/EED_Single_Page_Checkout.module.php(479): EED_Single_Page_Checkout->_process_finalize_registration() #3 [internal function]: EED_Single_ Page_Checkout->run(Object(WP_Query)) #4 /home/vegan/public_html/worldvega in /home/vegan/public_html/worldvegansummit.com/wp-content/plugins/event-espresso-core-reg/core/db_models/EEM_Gateways.model.php on line 842

Now, I’m not entirely sure if that’s because there is no valid transaction being passed (as this is just a hotlink to the page), or if there is an actual exception being caused by the plugin. I would recommend taking this information to the developers directly to see what may be causing the issue.

Hoping it was fixed I just tried checking out again with a fresh ticket selection and attendee information, but it gets stuck in the exact same place and if I follow the “If you are not automatically redirected to the payment website within 10 seconds” CLICK HERE link, it no longer results in a 403 error just this output, screenshot here:
http://worldvegansummit.com/images/temp/EE-screenshot1.png
and here’s the source code of that:
http://worldvegansummit.com/images/temp/EE-screenshot2.png

Tried the process again in another browser, same result.

We’ve got just 4 other plug-ins installed and running. I have tried deactivating all of them but still getting the same result.

You can go to:
http://worldvegansummit.com/attendee-registration/
if you want to try some test registrations and replicate this.

If it helps I can give you access to WP, ftp etc.

Thanks,

Ben


benjamin b

October 7, 2014 at 10:43 pm

One thing that might be important to know in trying to replicate this, I remember a few days after updating to the latest EE4, I had gone into the Payment Method settings and clicked on the Paypal Standard tab as I needed to grab the URL for the paypal checkout image for use somewhere else, and I ended up clicking the Update Paypal Standard Settings button at the bottom of the form there, even though I had not changed anything at all in the settings. I remember thinking, well I didn’t need to update that, I didn’t change anything. So I imagine it is possible that submitting an update to the settings there triggered a dormant bug that might be in the latest EE4.


Tony

  • Support Staff

October 8, 2014 at 5:17 am

Hi Benjamin,

Can you enable WP_Debug please, I’d like to run some test registrations and see if I can narrow this down some.

I know you mention you have tried this without the other plugins active, but could you once again de-activate these while we run some tests please.

I suspect there is still something being blocked on the server rather than an issue with EE4 (I ran some test registrations on a couple of different servers using PayPal sandbox, without issue) so we need to try an narrow this down some.


benjamin b

October 9, 2014 at 9:13 pm

Sorry for the delay, I had to tweak some pages to accommodate for disabling plugins. I appreciate your time on this – hoping we can get it fixed soon – we expect some traffic this weekend.

I have disabled all other plug-ins, including akismet and I have enabled WP_Debug.


benjamin b

October 9, 2014 at 9:19 pm

If you wish to FTP to code in some debugging output, I can supply credentials via email.


benjamin b

October 9, 2014 at 9:22 pm

…also I noticed WP_Debug isn’t complaining about anything, even during checkout process, but it’s definitely “On” as it was a giving a warning on the site for on one of my other plugins before they were disabled.


Josh

  • Support Staff

October 10, 2014 at 9:16 am

Hi Benjamin

I found a bug in the custom “PayPal lets you checkout with a credit card…” message that was added to this page, and it may be causing a domino effect on the payment page. Here’s the code you added:

Do you see where the second <font> element isn’t closed? You need to add a </font> before the closing </div>

After you fix this, the payment page may work as expected, but let us know if it doesn’t and we can investigate further.


benjamin b

October 10, 2014 at 12:04 pm

That fixes it! Wow, I feel like an idiot for not looking at the code I added there closer and furthermore should have realized that the template was edited 1 day before a visitor complained of the checkout processes hanging. Thank you! I also tested out the “Click Here if it’s been more than 10 seconds” link at the bottom and it also now redirects properly without showing that malformed page.

Viewing 9 reply threads

The support post ‘Finalizing registration has begun resulting in a 403 error on our site.’ is closed to new replies.

Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.

Event Espresso