Urgent: 500 Offline Error because of egacy-sepa-tokens script

Hi @lawshub,

Thanks for reaching out!

I understand you’re experiencing issues with your store pages going offline and showing a 500 error after the woocommerce-gateway-stripe-subscriptions-legacy-sepa-tokens-repairs was executed.

Will this script run every night?

This script is not designed to run every night. In most cases, it runs once when there is an update to the plugin. It’s unusual that it’s causing your pages to go offline. In general, the 500 error typically indicates a server issue.

It is possible that while the script is running it conflicted with one of your plugins, but I’m glad to see you were able to find a workaround to the issue.

Should the issue happen again, I recommend running a conflict test to be able to pinpoint where the conflict could be located. You may find details on how to run a conflict test here.

I hope this helps.

Thanks for your reply!

This script is not designed to run every night. In most cases, it runs once when there is an update to the plugin.

We have Version 8.5.1 installed now, will it run on the next update(s) as well?

Hi there @lawshub

Just to clarify, are there any subscriptions offered on your site? On a test site of mine, with no subscription functionality, this Action never appeared.

Moreover, based on the code:

Handles repairing the Subscriptions using SEPA’s Legacy payment method.

This class extends the WCS_Background_Repairer for scheduling and running the individual migration actions.

Therefore, to loop back to the original issue here:

We are pretty sure that this is the reason, our uptime monitor alerted 1 min after this log entry that woocommerce-gateway-stripe-subscriptions-legacy-sepa-tokens-repairs was executed

What troubleshooting steps were followed thus far, and what were the results?

I hope this is helpful! We look forward to your response. In the meantime, please let us know if you have any further questions or concerns.

Yes we sell mostly subscriptions.

After the second time it occurred I made a update of the woocommerce plugin from Version 9.1.1 to 9.1.2, that already helped. I guess it was not the newer version of woocommerce but the disabling/enabling process of the update process that helped.

Is there a change that WC_Stripe_Subscriptions_Repairer_Legacy_SEPA_Tokens will be executed in the future again or was this a one time process? If it will not be executed anymore there would be no danger anymore for us.

Hi @lawshub

Yes we sell mostly subscriptions.

Kindly elaborate further on this. As in, what subscription plugin is in use, what payment method(s) are affected, and if SEPA is among them.

After the second time it occurred I made a update of the woocommerce plugin from Version 9.1.1 to 9.1.2, that already helped. I guess it was not the newer version of woocommerce but the disabling/enabling process of the update process that helped.

Just to be sure, kindly explain further what differences you noticed and if the issue remains on your end, or otherwise (that part is unclear, I’m afraid).

I assume by disabling/enabling, you mean the process of updating a plugin via the wp-admin. Am I getting this?

Is there a change that WC_Stripe_Subscriptions_Repairer_Legacy_SEPA_Tokens?will be executed in the future again or was this a one time process? If it will not be executed anymore there would be no danger anymore for us.

Do you see it in the screen at WooCommerce > Status > Scheduled Actions or otherwise?

We are using the Woocommerce Subscription Plugin. The issue is that some pages ore showing offline with 500 error, like the cart page. So no specific payment method is affected.

I assume by disabling/enabling, you mean the process of updating a plugin via the wp-admin. Am I getting this?

Exactly

Do you see it in the screen at WooCommerce > Status > Scheduled Actions or otherwise?

Yes, it was shown there as executed, and exactly in the minute it was executed the pages went offline with code 500. Right now no further execution are scheduled, but I’m afraid it can be scheduled again (e.g. after an update of the Stripe module) and lead to the same error again.

So can you tell me, will this script scheduled in the future again (e.g. after an update of the Stripe module), or was that only in use for this explicit module version?

Thank you for reaching back, @lawshub , clarifying things further.

As you are using WooCommerce Subscriptions, a premium plugin, please contact us at WooCommerce.com > My Account > Support. You may need to create an account before you can access that page.

Please include a link to this forum thread, so that we can keep track of what’s already been done.

We will be able to help you further there.

Feel free to post back here, with how the issue was resolved, once troubleshooting is completed! ??

The issue should be resolved if the woocommerce-gateway-stripe-subscriptions-legacy-sepa-tokens-repairs will not executed in the future anymore. So can you tell me, will this script scheduled in the future again (e.g. after an update of the Stripe module), or was that only in use for this explicit module version?

Hi @lawshub,

Just to reiterate on what my colleague just shared above, this particular forum is meant for general support with the core functionality of WooCommerce Stripe Payment Gateway.

In order to get further assistance on our premium extensions like WooCommerce Subscriptions, please contact us at Woo.com > My Account > Support.

Please include a link to this forum thread, so that we can keep track of what’s already been done.
Our Happiness Engineers will be able to help you further there.

Thank you for your patience and understanding.