Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
SSL Errors + FAILED PAYMENT | Event Espresso - Staging Server

Support

Home Forums Event Espresso Premium SSL Errors + FAILED PAYMENT

SSL Errors + FAILED PAYMENT

Posted: August 5, 2013 at 9:25 pm

Viewing 9 reply threads


Peter Morin

August 5, 2013 at 9:25 pm

Hello,

I am running the latest and greatest EE (downloaded the latest rev this evening). Using the Stripe gateway. I have a functioning SSL cert, however when I go to the payment settings screen (which takes forever to load up), I get this error: “Attention: A valid SSL Certificate is required on your website in order to process payments using this gateway!” which I assume is the reason why my payments are not working. I have installed EE many times on many different sites and never got this error before. Please help.


Seth Shoultes

  • Support Staff

August 5, 2013 at 10:38 pm

What is the URL to the site, please?


Peter Morin

August 6, 2013 at 3:45 am

http://Www.isaca-Atlantic.ca but I do not have any active events as I didn’t want people trying them out with the card issue.


Peter Morin

August 6, 2013 at 8:34 am

I am waiting to launch registration….anything that can help me? I am desperate!


Josh

August 6, 2013 at 8:38 am

Hi Peter,

The SSL check on the settings page uses a PHP function to check for SSL support on your site. It’s not a fool proof check but it works most of time. It will not affect the way the gateway works.

Do you have your Stripe account set to Live or Testing Mode?


Peter Morin

August 6, 2013 at 8:47 am

I am in testing mode with Stripe….


Peter Morin

August 6, 2013 at 9:08 am

When I check the Stripe logs, I don’t see any traffic from EE.


Josh

August 6, 2013 at 9:48 am

A couple things to check: Make sure that cURL is installed on your server. This information is available in Event Espresso>System status.

Also it’s important that the Stripe secret key and publishable keys match your account exactly. Any leading or trailing white space copied/pasted into the field will make for an invalid key.

If you are testing the Stripe gateway, use your test keys, otherwise use your live keys.


Peter Morin

August 6, 2013 at 10:54 am

Figured it out! Currency code mismatch between EE and Stripe. How do i make that error in the payment settings screen go away, takes forever to have the screen come up.


Josh

August 6, 2013 at 12:21 pm

It’s not really an error but more of a Warning message, and it shouldn’t slow down the Payment settings page.

It may be that fopen is disabled on your server, in which case you can check to see if it’s an option to enable it.

Or you can comment out the block of code in /gateways/stripe/settings.php like this:

<?php /*
if (espresso_check_ssl() == FALSE){
	espresso_ssl_required_gateway_message();
}
*/ ?>
Viewing 9 reply threads

The support post ‘SSL Errors + FAILED PAYMENT’ 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 - Staging Server