ahawtin

On the French site:
23 février 2022 j F Y

On the English site:
February 23, 2022 Custom F j, Y

The error occurs on the test site when we flip to French (specifically fr_CA). Just looking around at differences between the two sites (English vs French) and the date/time format is different due to preferences found in French Canada. Do you think that might be causing some difficulty?

Have to pause a bit during this diagnosis to work on another issue. I will update when I get some time to play with the date/time format.

Hello again and thank you for checking. This error only occurs only on the French site – not on the English site. Right now we are running php 8 on the English site and php 7.4 on the French site to work around this difficulty. In terms of extensions the only real difference between the two sites is loco translate. Plus the language declaration of course. I will first flip our staging site to French and see if the error occurs. Then if it does, disable loco translate.

May I ask what language you were testing in?

Hello again and thanks so much. You are of course absolutely right. We installed your plug-in then added the cache. The WooCommerce folks guide you to set change the localization selection to ‘with caching’ which brings in the redirection. I guess it is fair to say that the redirection actually bypasses the cache. So the benefit of the caching plug-in is lost in this case.

I believe that if we turn off localization in WooCommerce (in order to bring into effect the caching), your plug-in would continue to work. It would not however automatically detect the country reflected in the IP address of the user and hence would leave the currency as the default. This would force the customer to select the currency manually which is a bit inconvenient.

Thank you for your help. And again, let me say that your plug-in is excellent.

Hello again,

we did so leaving only WooCommerce and Storefront active. The redirect remains. I believe that this plug-in is the only one doing a redirect. On our test site the redirect looks like:

https://woo-test.alhawtin.com/

https://woo-test.alhawtin.com/?v=3e8d115eb4b3

I checked the plug-in code and there are of course a number of instances of redirects in the code. I don’t however understand how a redirect might persist after the plug-in is disabled and deleted.

In looking at our live site, the redirect is formulated as:

https://basicsbymail.com/?v=3e8d115eb4b3&wmc-currency=USD

or

https://basicsbymail.com/?v=3e8d115eb4b3&wmc-currency=CAD

Tonight I will see what happens when we disabled the plug-in on the live site and report back.

Hello and sorry that I wasn’t entirely clear.

The customer asked us to install multi-currency on their English language site. We did so and it works perfectly. A very good plug-in, thank you. The customer notices that the English site is now slower than their other site (the French language site). We believe it is due to the multi-currency plug-in which does a re-direct (a 307 according to the speed testing tools). We wanted to confirm that the speed would improve when we disabled the plug-in but it didn’t as the site still did the re-direct. So we thought perhaps the plug-in didn’t remove the redirect when we disabled it. We also tried removing the plug-in but it seems the redirect is still there.

I think there is no way to do multi-currency without the redirect being in place – hence a slower site.

I believe you have a js option for pro customers but it will not work with a caching plug-in. There are caching plug-ins on the sites and the sites would be way too slow without them so they have to be there.

So I think the customer will have to live with the slower speed if they want multi-currency.

I hope that is clearer.

Hey Zorem,

we were adding tracking manually. Let us know if there is anything else we can do to narrow it down.

Hello @woonami,

a ticket has been created. I will try to get a better understanding of what web site event is triggering this log entry. Have to dig a bit in the access logs on the VPS.

OK – also added a print_r of $_REQUEST to the log entry and came up with this:

2021-12-31T14:02:34+00:00 DEBUG 
====Stripe Version: 5.9.0====
====Start Log====
Stripe live mode requires SSL. As seen in payment script. $_REQUEST is
Array
(
    [woocommerce-login-nonce] => 
    [_wpnonce] => 
    [woocommerce-reset-password-nonce] => 
    [woocommerce-edit-address-nonce] => 
    [save-account-details-nonce] => 
)

So this log entry is in some way due to a login attempt? I will take a closer look. I should add that these log entries are generated by abstract-wc-stripe-payment-gateway.php at line 1753.

OK – dug out the code for the log entry. Instead of doing the test code, I will expand the log entry to provide some supplementary information in the log. That will be more helpful I believe.

I’ve added more information to the log on both the French and English sites. If there is anything that the developers would like to see in the log entry, just let me know and I will add it in. Starting now with a message to determine which of the two checks are triggering the log entry.

Al

Hello Rashed,

the sites aren’t using either a load balancer or reverse proxy.

The code snippets you are using in the SSL detection would be very helpful. I guess I can go and dig them out of the code but you could save me some time if you were to provide them. Then I can build out our test plug-in.

Al

Thanks for getting back to me. I am going to take another look at the access log to see what is triggering the SSL error log entry in the Stripe Gateway log. Will report back what I find.

The site status report:

### WordPress Environment ###

WordPress address (URL): https://basicsbymail.com
Site address (URL): https://basicsbymail.com
WC Version: 6.0.0
REST API Version: ? 6.0.0
WC Blocks Version: ? 6.3.3
Action Scheduler Version: ? 3.3.0
WC Admin Version: ? 2.9.4
Log Directory Writable: ?
WP Version: 5.8.2
WP Multisite: –
WP Memory Limit: 512 MB
WP Debug Mode: –
WP Cron: ?
Language: en_CA
External object cache: –

### Server Environment ###

Server Info: Apache/2
PHP Version: 7.4.26
PHP Post Max Size: 128 MB
PHP Time Limit: 900
PHP Max Input Vars: 1000
cURL Version: 7.73.0
OpenSSL/1.0.2k-fips

SUHOSIN Installed: –
MySQL Version: 5.5.5-10.3.32-MariaDB
Max Upload Size: 128 MB
Default Timezone is UTC: ?
fsockopen/cURL: ?
SoapClient: ?
DOMDocument: ?
GZip: ?
Multibyte String: ?
Remote Post: ?
Remote Get: ?

### Database ###

WC Database Version: 6.0.0
WC Database Prefix: wp_
Total Database Size: 129.06MB
Database Data Size: 89.51MB
Database Index Size: 39.55MB
wp_woocommerce_sessions: Data: 0.81MB + Index: 0.02MB + Engine MyISAM
wp_woocommerce_api_keys: Data: 0.01MB + Index: 0.01MB + Engine MyISAM
wp_woocommerce_attribute_taxonomies: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wp_woocommerce_downloadable_product_permissions: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wp_woocommerce_order_items: Data: 2.03MB + Index: 0.85MB + Engine MyISAM
wp_woocommerce_order_itemmeta: Data: 12.29MB + Index: 8.34MB + Engine MyISAM
wp_woocommerce_tax_rates: Data: 0.00MB + Index: 0.01MB + Engine MyISAM
wp_woocommerce_tax_rate_locations: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wp_woocommerce_shipping_zones: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wp_woocommerce_shipping_zone_locations: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wp_woocommerce_shipping_zone_methods: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wp_woocommerce_payment_tokens: Data: 0.02MB + Index: 0.01MB + Engine MyISAM
wp_woocommerce_payment_tokenmeta: Data: 0.04MB + Index: 0.03MB + Engine MyISAM
wp_woocommerce_log: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
canadelle_target: Data: 0.04MB + Index: 0.01MB + Engine MyISAM
elita_target: Data: 0.01MB + Index: 0.01MB + Engine MyISAM
sale_process: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
shadowline_target: Data: 0.01MB + Index: 0.01MB + Engine MyISAM
stanfields_target: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wh_pharmasave: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wp_actionscheduler_actions: Data: 0.78MB + Index: 0.45MB + Engine MyISAM
wp_actionscheduler_claims: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wp_actionscheduler_groups: Data: 0.00MB + Index: 0.01MB + Engine MyISAM
wp_actionscheduler_logs: Data: 3.49MB + Index: 0.81MB + Engine MyISAM
wp_aioseo_cache: Data: 0.17MB + Index: 0.03MB + Engine InnoDB
wp_aioseo_notifications: Data: 0.03MB + Index: 0.06MB + Engine InnoDB
wp_aioseo_posts: Data: 1.52MB + Index: 0.02MB + Engine InnoDB
wp_aws_cache: Data: 2.63MB + Index: 0.00MB + Engine MyISAM
wp_aws_index: Data: 2.06MB + Index: 1.02MB + Engine MyISAM
wp_commentmeta: Data: 0.02MB + Index: 0.03MB + Engine MyISAM
wp_comments: Data: 4.54MB + Index: 1.80MB + Engine MyISAM
wp_db7_forms: Data: 0.11MB + Index: 0.00MB + Engine MyISAM
wp_lecm_rewrite: Data: 0.04MB + Index: 0.01MB + Engine MyISAM
wp_links: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wp_mailchimp_carts: Data: 0.38MB + Index: 0.02MB + Engine MyISAM
wp_mailchimp_jobs: Data: 1.70MB + Index: 0.06MB + Engine MyISAM
wp_mgmlp_folders: Data: 0.01MB + Index: 0.01MB + Engine MyISAM
wp_on_amazon: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wp_on_ebay: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wp_options: Data: 9.63MB + Index: 0.49MB + Engine MyISAM
wp_pimwick_gift_card: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wp_pimwick_gift_card_activity: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wp_postmeta: Data: 30.97MB + Index: 15.08MB + Engine MyISAM
wp_posts: Data: 2.95MB + Index: 1.09MB + Engine MyISAM
wp_shipment_batch_process: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wp_termmeta: Data: 0.03MB + Index: 0.03MB + Engine MyISAM
wp_terms: Data: 0.02MB + Index: 0.05MB + Engine MyISAM
wp_term_relationships: Data: 0.38MB + Index: 0.83MB + Engine MyISAM
wp_term_taxonomy: Data: 0.02MB + Index: 0.04MB + Engine MyISAM
wp_testimonials: Data: 0.01MB + Index: 0.00MB + Engine MyISAM
wp_tm_taskmeta: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wp_tm_tasks: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wp_usermeta: Data: 7.05MB + Index: 5.64MB + Engine MyISAM
wp_users: Data: 0.58MB + Index: 0.53MB + Engine MyISAM
wp_watchlist: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_wcpdf_invoice_number: Data: 0.07MB + Index: 0.04MB + Engine MyISAM
wp_wc_admin_notes: Data: 0.01MB + Index: 0.00MB + Engine MyISAM
wp_wc_admin_note_actions: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wp_wc_category_lookup: Data: 0.00MB + Index: 0.01MB + Engine MyISAM
wp_wc_customer_lookup: Data: 0.31MB + Index: 0.27MB + Engine MyISAM
wp_wc_download_log: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wp_wc_order_coupon_lookup: Data: 0.00MB + Index: 0.01MB + Engine MyISAM
wp_wc_order_product_lookup: Data: 0.57MB + Index: 0.55MB + Engine MyISAM
wp_wc_order_stats: Data: 0.26MB + Index: 0.17MB + Engine MyISAM
wp_wc_order_tax_lookup: Data: 0.13MB + Index: 0.15MB + Engine MyISAM
wp_wc_product_meta_lookup: Data: 0.65MB + Index: 0.83MB + Engine MyISAM
wp_wc_rate_limits: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_wc_reserved_stock: Data: 0.19MB + Index: 0.00MB + Engine MyISAM
wp_wc_tax_rate_classes: Data: 0.00MB + Index: 0.01MB + Engine MyISAM
wp_wc_webhooks: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wp_woocommerce_stock_action: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wp_woocommerce_stock_action_fr: Data: 0.03MB + Index: 0.00MB + Engine MyISAM
wp_woo_shippment_provider: Data: 0.03MB + Index: 0.00MB + Engine MyISAM
wp_wss_log: Data: 2.76MB + Index: 0.08MB + Engine MyISAM
wp_wt_iew_action_history: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_wt_iew_cron: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_wt_iew_ftp: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_wt_iew_mapping_template: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_yoast_seo_links: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wp_yoast_seo_meta: Data: 0.00MB + Index: 0.00MB + Engine MyISAM

### Post Type Counts ###

acf-field: 7
acf-field-group: 1
attachment: 1898
custom_css: 1
customize_changeset: 4
mgmlp_media_folder: 13
nav_menu_item: 19
page: 10
post: 1
product: 379
product_variation: 3974
productsliderwoo: 1
revision: 104
shop_coupon: 3
shop_order: 4169
shop_order_refund: 204
user_request: 1
wpcf7_contact_form: 1

### Security ###

Secure connection (HTTPS): ?
Hide errors from visitors: ?

### Active Plugins (36) ###

Add minutes: by ahawtin – 1.0
Address download plugin: by Al Hawtin – 1.0.0
Advanced Custom Fields: by Delicious Brains – 5.11.4
Advanced Woo Search: by ILLID – 2.43
All in One SEO: by All in One SEO Team – 4.1.5.3
Canada Post Shipping For WooCommerce: by Small Fish Analytics Inc. – 2.9.4
Contact Form 7: by Takayuki Miyoshi – 5.5.3
Contact Form CFDB7: by Arshid – 1.2.6.2
Delete Expired Transients: by WebAware – 2.0.7
Ebay stock update: by Al Hawtin – 1.0.0
Email download plugin: by Al Hawtin – 1.0.0
Google Analytics for WordPress by MonsterInsights: by MonsterInsights – 8.3.0
Hanes inventory analysis: by ylefebvre – 1.0
LitExtension Customer Password Plugin: by LitExtension – 1.0.0
LitExtension SEO Plugin: by LitExtension – 1.0.1
Mailchimp for WooCommerce: by Mailchimp – 2.5.4
Minimal Coming Soon & Maintenance Mode: by WebFactory Ltd – 2.33
Order pick list plugin: by Al Hawtin – 1.0.0
Reset sale pricing: by ylefebvre – 1.0
Sale price process: by Al Hawtin – 1.0.0
Show stock: by Al Hawtin – 1.0
List stock action table: by Al Hawtin – 1.0.0
Storefront Top Bar: by Wooassist – 1.1.1
Category Order and Taxonomy Terms Order: by Nsp-Code – 1.5.9
UpdraftPlus - Backup/Restore: by UpdraftPlus.com
DavidAnderson – 1.16.69

WooCommerce Address Book: by Hall Internet Marketing – 2.0.0
Advanced Shipment Tracking for WooCommerce: by zorem – 3.3.1
Variation Swatches for WooCommerce: by RadiusTheme – 2.1.1.4
WooCommerce Stripe Gateway: by WooCommerce – 5.9.0
WooCommerce Multi Currency Premium: by VillaTheme – 2.1.22.4
WooCommerce PDF Invoices & Packing Slips: by Ewout Fernhout – 2.11.1
WooCommerce Sequential Order Numbers: by SkyVerge – 1.9.5
WooCommerce: by Automattic – 6.0.0
WP Crontrol: by John Blackbourn & contributors – 1.12.0
WPB Product Slider for WooCommerce: by wpbean – 2.0.9.2
Smart Coupons for WooCommerce: by WebToffee – 1.3.6

### Inactive Plugins (1) ###

WooCommerce Extended Coupon Features FREE: by Soft79 – 3.2.8

### Settings ###

API Enabled: –
Force SSL: ?
Currency: CAD ($)
Currency Position: left
Thousand Separator: ,
Decimal Separator: .
Number of Decimals: 2
Taxonomies: Product Types: simple (simple)
grouped (grouped)
variable (variable)
external (external)
pw gift card (pw-gift-card)

Taxonomies: Product Visibility: exclude-from-search (exclude-from-search)
exclude-from-catalog (exclude-from-catalog)
featured (featured)
outofstock (outofstock)
rated-1 (rated-1)
rated-2 (rated-2)
rated-3 (rated-3)
rated-4 (rated-4)
rated-5 (rated-5)

Connected to WooCommerce.com: –

### WC Pages ###

Shop base: #6 - /shop/
Cart: #7 - /cart/
Checkout: #8 - /checkout/
My account: #9 - /my-account/
Terms and conditions: ? Page not set

### Theme ###

Name: Storefront Child Theme
Version: 1.0.0
Author URL: https://stuartduff.com
Child Theme: ?
Parent Theme Name: Storefront
Parent Theme Version: 3.9.1
Parent Theme Author URL: https://woocommerce.com/
WooCommerce Support: ?

### Templates ###

Overrides: storefront-child-theme-master/woocommerce/emails/email-order-details.php
storefront-child-theme-master/woocommerce/emails/email-order-items.php

### Action Scheduler ###

Cancelled: 1
Oldest: 2021-12-08 13:54:57 +0000
Newest: 2021-12-08 13:54:57 +0000

Complete: 2,348
Oldest: 2021-11-29 13:42:58 +0000
Newest: 2021-12-30 12:33:19 +0000

Failed: 1
Oldest: 2021-07-31 11:49:31 +0000
Newest: 2021-07-31 11:49:31 +0000

Pending: 3
Oldest: 2021-12-30 12:48:19 +0000
Newest: 2021-12-31 11:54:08 +0000

### Status report information ###

Generated at: 2021-12-30 08:41:52 -04:00

We don’t do any caching on the site. The caching plug-ins are problematic in WooCommerce so we elected to go with more VPS resources.

Could there be a conflict? Well the theme is Storefront so hopefully not with the theme. With another plug-in – always a possibility. It would however be hard to work that through given that these errors are intermittent. And hard to do on our staging site which doesn’t see much traffic. It will be helpful to see how the SSL test is conducted as we can then add some code to functions.php to mimic this functionality every few minutes to see if we come up with the same problem. If the developers were to provide a code snippet from the plug-in where this check is done we can use that in our test code. When we build the test code, we’ll hit the site every five minutes for a day to see what it reports.

Just to recap what I’ve done so far:

1. Messaged with Stripe support. They report no issue on their end with transactions or webhooks.
2. Discussed the SSL implementation with our hosting company – Knownhost. They had a look and see no issues. They were responsible for the configuration of the VPS as well as issuing the cert on the site so they know it is clean.
3. Ran an SSL test on Qualsys. SSL implementation rated as an ‘A’.

Al

This is a VPS and I have looked at the server logs and don’t see an SSL error occurring at the time the log entry is made. I should however confirm with you what the timestamp in the Stripe gateway log is based on. Is it the server time which in this case would be EST. Or UTC?

It would be good to know how this SSL test is done. And what would spawn the test. Is there a Stripe gateway cron job that tests for SSL? That also seems a bit odd as the timing of the error report isn’t rhythmic which I would expect from a cron job. Would the test be a CURL against the URL and check for an error? I can then check the access logs to see if that is happening. But again, no SSL error logged so that seems unlikely.

I can only think of one mechanism in Apache which would see SSL disappear for a time. That would occur with heavy site loading and no workers are available for the session. Sure don’t see any resource exhaustion at this point, especially since the errors are sometimes reported early morning.

OK – I dug into the English log and found the identical error. It occurs much less frequently. Still confused as to why it occurs but it does occur on both sites. Here is the log entry in which I found it along side other log entries registered only as “account”. Very puzzling.

2021-12-29T11:20:57+00:00 DEBUG 
====Stripe Version: 5.9.0====
====Start Log====
account
====End Log====

2021-12-29T12:04:55+00:00 DEBUG 
====Stripe Version: 5.9.0====
====Start Log====
Stripe live mode requires SSL.
====End Log====

2021-12-29T13:24:42+00:00 DEBUG 
====Stripe Version: 5.9.0====
====Start Log====
account
====End Log====

2021-12-29T16:43:19+00:00 DEBUG 
====Stripe Version: 5.9.0====
====Start Log====
account
====End Log====

Yes, the site does use SSL. Are there problems on check-out – isn’t that a bit hard to determine as customers could be encountering problems and might just depart. The log error messages persist:

2021-12-29T15:43:41+00:00 DEBUG 
====Stripe Version: 5.9.0====
====Start Log====
Stripe live mode requires SSL.
====End Log====

2021-12-29T15:45:44+00:00 DEBUG 
====Stripe Version: 5.9.0====
====Start Log====
Stripe live mode requires SSL.
====End Log====

2021-12-29T15:47:13+00:00 DEBUG 
====Stripe Version: 5.9.0====
====Start Log====
Stripe live mode requires SSL.
====End Log====

2021-12-29T15:47:15+00:00 DEBUG 
====Stripe Version: 5.9.0====
====Start Log====
Stripe live mode requires SSL.
====End Log====

2021-12-29T15:49:44+00:00 DEBUG 
====Stripe Version: 5.9.0====
====Start Log====
Stripe live mode requires SSL.
====End Log====

2021-12-29T16:13:00+00:00 DEBUG 
====Stripe Version: 5.9.0====
====Start Log====
Stripe live mode requires SSL.
====End Log====