lancerlan

Okay I see. Thank you.

Hey, thank you for the reply. If the logs look normal, does that mean the issue is not related to the payment plugin? Do you have any idea where this issue could be originating from? I can’t think of anything else that could be causing the multiple billing attempts on my customers’ bank cards. Thank you.

The customer whose bank card got blocked placed the order at 18:23 today, so I checked the logs page and specifically looked for entries around 18:23. I’m not sure how to interpret these log files. I do see 3 logs with the name ‘payment intents.’ Does it imply that there were 3 charging attempts for this order? Thank you.

Hey, thank you for the reply.

I figured out the issue myself regarding the failed payment in the screenshot. I have another Stripe plugin active on my website exclusively for WeChat Pay. The customer was initially attempting to pay with WeChat Pay but failed, and then successfully paid with a credit card through your plugin. That explains the two payments in the screenshot.

However, this still doesn’t explain the problem. The two customers who reported this multiple-charging-attempts issue to me are not related to the payment in the screenshot. These two customers paid with PayPal through ‘PayPal by Payment Plugins’ and credit card through ‘Stripe by Payment Plugin,’ respectively. On the Stripe.com payment page, there is only one payment recorded for each of them. However, their banks did receive multiple billing attempts, and one of the customers’ banks even blocked her bank card due to that.

Also I’ve checked the “fatal-error” log file, but there isn’t any with today’s timestamp on it.

Problem resloved.

problem resolved.

Hey,

Regarding the second warning: I replaced define(‘DISABLE_WP_CRON’, true) with define(‘ALTERNATE_WP_CRON’, true), and added codes above in the .htaccess file. This resolved the second warning without causing domain issues. However, it introduced some new problems:

• Clicking in my WordPress dashboard or refreshing the UpdraftPlus page sometimes redirects to a different page. For instance, refreshing the UpdraftPlus page often redirects to the general settings page at ‘https://lanceraccessories.com/wp-admin/options-general.php.’

• I encountered two common errors when accessing pages in the WordPress dashboard

This page isn’t working // lanceraccessories.com?redirected you too many times. // Try clearing your cookies. ERR_TOO_MANY_REDIRECTS

This site can’t be reached // lanceraccessories.com?took too long to respond. // Try: * Checking the connection // * Checking the proxy and the firewall ERR_TIMED_OUT

• Additionally, I received two identical “backed up” emails from UpdraftPlus for the first time, even though it usually sent only one email after completing a backup.

Due to these new problems, I removed the recently added code from the .htaccess file and reverted ‘define(‘DISABLE_WP_CRON’, true)’ back to its original state in the wp-config file.

My concern here is whether we can safely ignore this warning. As mentioned earlier, I can see new UpdraftPlus backups in the “existing backups” section daily, indicating that the daily backups seem to be functioning as expected. In this case, does it mean that this warning can be disregarded?

____________________________________________________________

Regarding the first warning:

I made changes to the cron entry to run it every minute with the following configuration:

*/1 * * * * cd /home/master/applications/danrxadqnz/public_html && /usr/bin/php /usr/local/bin/wp cron event run –due-now

Despite setting the cron to run every minute, I’m still encountering the same warning sometimes, indicating overdue schedules. My question here is, does this minor backlog actually matter, and will it lead to actual issues on the website? If a few minutes of backlog isn’t critical, can I safely ignore this warning?

Thank you.

Hey David,

I appreciate your response. I’ve made the change to the cron entry as follows:

*/1 * * * * cd /home/master/applications/danrxadqnz/public_html && /usr/bin/php /usr/local/bin/wp cron event run –due-now

Despite setting the cron to run every minute, I’m still encountering the same warning sometimes, indicating overdue schedules. My question here is, does this minor backlog actually matter, and will it lead to actual issues on the website? If a few minutes of backlog isn’t critical, can I safely ignore this warning?

Thank you.

• This reply was modified 1 year, 4 months ago by lancerlan.

Hey David, thank you for the reply!

I’ve installed the WP Control plugin, which indicates that the most frequent interval required for cron events on my website is every 5 minutes. Does this mean that adjusting the server-based cron to run at a 5-minute frequency will resolve the issue?

To achieve this, should I modify the cron setup they provided to the one below?

*/5 * * * * cd /home/master/applications/danrxadqnz/public_html && /usr/bin/php /usr/local/bin/wp cron event run –due-now

In this new entry, I’ve included cd before /home and changed the number from 30 to 5. I’m not particularly tech-savvy, so I’m unsure about the significance of the “30” in the previous setup, but I assume it represents the schedule for the cron job. Could you please confirm if this new entry would address the problem? Your assistance is greatly appreciated. Thank you.

Hello,

Thank you for the reply.

Yes I have reverted the change as I want to keep the original domain.

Regarding the first warning: I followed the instructions and installed WP Control. In the Cron Events section, I observed that there are only four events with intervals more frequent than 30 minutes, but the warning typically indicates that there are between 5 to 8 overdue tasks. Additionally, it shows that there are 10 events with no action, all of which have intervals less frequent than 30 minutes, as shown in the attached image.

Regarding the second warning: Does this mean we should simply ignore this warning? As previously mentioned, I can see new UpdraftPlus backups in the “existing backups” section every day, suggesting that the daily backup appears to be functioning as expected. However, the recurring warning has left me somewhat puzzled, and I’m uncertain if the backup is actually running smoothly. If this warning is automatically sent to all users whose WordPress native cron is disabled, regardless of whether there is an alternative cron in place, then it would make sense to ignore this warning.

Hey,

I tried to add a new line “define( ‘ALTERNATE_WP_CRON’, true);” to the wp-config.php file, but this didn’t resolve the problem, and I’m still encountering the same warnings from UpdraftPlus.

I also experimented with changing the line “define(‘DISABLE_WP_CRON’, true);” to “define( ‘ALTERNATE_WP_CRON’, true);”. This modification did fix the scheduler problem, and I do not receive warnings from UpdraftPlus anymore. However, there was an unintended side effect: my domain name changed. Initially, my domain was lanceraccessories.com, but after changing “DISABLE” to “ALTERNATE” in the wp-config.php file, my domain transformed into: https://lanceraccessories.com/?doing_wp_cron=1698687683.9295780658721923828125

I’m seeking guidance on how to rectify this issue. Thank you.

• This reply was modified 1 year, 4 months ago by lancerlan.

Not by recreating the A records but the problem has been solved already.

Okay I see. Thank you very much.

Hi,

Thank you for reply. I’m contacting my hosting company, but I have one more question. If this error means my server is taking too long to respond to the webhook request, why it only happens with WeChat Pay? I tried to pay with credit card and Apply Pay and both were captured immediately. Does WeChat Pay work differently from those two in the plugin?

Thank you.

Yes there are logged failures. They are all from today and all from WeChat Pay.

In the Response section of each failure it says “Time out connecting to remote host”

And here is what it shows in Request section in one of these failures.

{
  "id": "evt_1MxAVqK7geiL9K9OZetRPXp6",
  "object": "event",
  "api_version": "2020-03-02",
  "created": 1681570538,
  "data": {
    "object": {
      "id": "src_1MxAVUK7geiL9K9OOsXmVjJj",
      "object": "source",
      "amount": 50,
      "client_secret": "src_client_secret_eLMk3tU8QI5eWTrhGq7P41YU",
      "created": 1681570516,
      "currency": "eur",
      "flow": "none",
      "livemode": true,
      "metadata": {
        "order_id": "6827",
        "created": "1681570515"
      },
      "owner": {
        "address": {
          "city": "MILANO",
          "country": "IT",
          "line1": "VIA DOANTELLO 17",
          "line2": "",
          "postal_code": "20131",
          "state": "MI"
        },
        "email": "[email protected]",
        "name": "MENGYING LAN",
        "phone": "3515189805",
        "verified_address": null,
        "verified_email": null,
        "verified_name": null,
        "verified_phone": null
      },
      "statement_descriptor": "Order 6827",
      "status": "chargeable",
      "type": "wechat",
      "usage": "single_use",
      "wechat": {
        "prepay_id": "wx152255169799415c52e8ce271efebf0000",
        "qr_code_url": "weixin://wxpay/bizpayurl?pr=a8cxKcEzz"
      }
    }
  },
  "livemode": true,
  "pending_webhooks": 1,
  "request": {
    "id": null,
    "idempotency_key": null
  },
  "type": "source.chargeable"
}