Woozy Face

I tried disabling all plugins and only enabling the All In One WP Security plugin. The login page is shown, but I get a “login failed, wrong details” message. I’ve already added myself to the whitelist and, just in case, I fetched the cookie as well. I can log in using the same credentials without the plugin activated.

Looks like my reply is stuck in moderation limbo—guess we’ll have to wait for it to escape and bring the results with it!

Hello WooCommerce Team,

The issue with SEPA tokens in WooCommerce Stripe Payment Gateway Version 8.5.2 has been successfully resolved, and I’d like to provide a detailed rundown of the steps we took and which solutions worked.

Issue Recap:

We were encountering an accession error when trying to process SEPA payments with tokens attached to a customer, specifically for recurring subscription payments. Stripe identified that the issue was due to charging a consumed source without reattaching it, along with the use of a deprecated Sources API.

Steps Taken and Results:

1. Discussion with Stripe Support: We identified that the source was being consumed and not properly reattached before attempting a charge. Stripe advised checking the source status before making the request, as consumed sources cannot be reused.
   Outcome: This clarified the core issue. It was crucial to ensure sources were either reattached or a new one was used.
2. Migration to Payment Methods API: Stripe also recommended migrating to their Payment Methods API, which handles token management more efficiently and avoids issues with consumed sources.
   Outcome: While this step was not immediately implemented, it’s part of our long-term plan to prevent future issues.
3. Plugin Update: After updating to WooCommerce Stripe Payment Gateway Version 8.6, as suggested by the support team, we monitored the transactions closely.
   Outcome: The update resolved the accession error. The issue no longer occurred after the update, and transactions with SEPA tokens were successfully processed without errors.

What Worked:

• Updating to WooCommerce Stripe Gateway Version 8.6: This fixed the immediate issue, as the updated version likely handled the SEPA token process differently.
• Regular monitoring of Stripe logs: This ensured that any recurring issues were quickly identified and addressed.

What Did Not Work Initially:

• Continuing with the old Sources API: Attempting to process payments with the deprecated API without migration led to persistent errors until we moved forward with the update.

Thanks to the update and following Stripe’s advice, the issue has been fully resolved. I appreciate all the support and guidance provided throughout the process.

Best regards,
Woozy Face

• This reply was modified 5 months, 2 weeks ago by Woozy Face.
• This reply was modified 5 months, 2 weeks ago by Woozy Face. Reason: Formatting issues

If it’s a subscription, can you tell me which plugin you used? Have you re-authenticated your Stripe account? Also, I’m curious to know if you’re using the new checkout experience or sticking with a legacy one.

we use the new experience, in combination with WooCommerce subscriptions.

By the way, we’re launching version 8.6 today. I’d appreciate it if you could test it using the latest version and let us know if you still have this problem.

I’ll get back to you with the status. I’ve updated the plugin, so now I have to wait until September 1st. Since this issue is only occurring with one specific client, we can’t just bill them without cause.

• This reply was modified 6 months, 2 weeks ago by Woozy Face.

i reopen it since I had not received any notifications of an update to this topic.

This happens only on subscriptions.

• This reply was modified 6 months, 2 weeks ago by Woozy Face.

Hello,

Hi,

Sorry to re-open this ticket, but I’ve discovered what the issue is. I use a VPN server behind my web host server. For some reason, it is capturing every visitor’s IP address as the local IP address of the server itself, assigned by the VPN IP Pool. This issue is causing significant problems, including website downtime when a hacker is blocked by IP, as it redirects all visitors to localhost. I’ve reached out to OpenVPN support, but they couldn’t provide a solution. Do you have any insights or suggestions on how to address this within the All in One Security plugin for WordPress? Thank you.

• This reply was modified 1 year ago by Woozy Face.

Hi,

I’ve resolved the issue by taking the following steps: removing the plugin, .htaccess rules, deleting all aiowps tables in my database, as well as the relevant section within the options table. Afterward, I reinstalled the plugin, configured it, and now it’s functioning properly again. Prior to this, I had already checked all your suggestions, but none of them turned out to be the cause of the issue.

Dear Developer,

I felt compelled to share the latest twist in my ongoing battle with this confounding issue. In a bid to confront this enigma, I boldly reset and meticulously reconfigured both the whitelist and slug settings. Astonishingly, there was a glimmer of hope as everything worked perfectly for a single day. However, this fleeting respite has only deepened my frustration.

What perplexes me most is the sinister nature of this problem. It’s as if there’s a malevolent bug clandestinely at play, slowly eroding my sanity with each recurrence. It’s become an insidious force, devouring my brain cells one by one.

I humbly request your expertise, dear Developer. There must be an underlying bug or glitch, lurking in the shadows, eluding my grasp. Is there a way to patch this torment once and for all?

Your timely assistance would be a ray of hope in this nightmarish journey.

Sincerely,
I forgot my name that part of my brain just went…

• This reply was modified 1 year, 5 months ago by Woozy Face.

What are you talking about @alihosseini20368. Please start your own topic.

4 days later same issue @hjogiupdraftplus

Okay that gave access back, thanks!

I sincerely apologize for not addressing the error earlier. As per the console logs, it clearly indicated that the WSOD was, in fact, a 403 error.

Certainly, I have a personal preference for not using Pastebin, and instead, I’ve devised my own solution. I’ve limited the download rate to a maximum of 1, so I kindly request other readers to refrain from clicking on this link to the actual file. I know it is tempting so, click here instead, if you are not the one who is giving support ?? .

Thanks!

Recently, I encountered an issue where my website’s wp-login.php page displayed a White Screen of Death (WSOD) after temporarily disabling your plugin by renaming the plugin folder to ‘disabled.yourreallylongfoldername’ via FTP. After doing this, I was able to log in successfully.

It appears that something goes awry in a seemingly random manner, almost like a ‘now this, then that’ scenario, as opposed to a more predictable ‘if this, then that’ situation. I hope that analogy makes sense!

If anyone has any suggestions or insights related to this specific issue, I’d greatly appreciate it. Thank you!

It happend again….

That’s not what I meant. I’m familiar with how that feature works. I understand that I need to visit the URL to retrieve a pack of cookies ??, but the complete functionality breaks down. For instance, if I access the correct secret word, like ‘/?someword=1’, it doesn’t recognize the input and redirects me to the localhost, i.e., 127.0.0.1. It usually happens after an update of the plug-in. If I do reset it as described above it usually works again but then after some time.