Title: Woozy Face's Replies | WordPress.org --- # Woozy Face [ ](https://wordpress.org/support/users/shaady4/) * [Profile](https://wordpress.org/support/users/shaady4/) * [Topics Started](https://wordpress.org/support/users/shaady4/topics/) * [Replies Created](https://wordpress.org/support/users/shaady4/replies/) * [Reviews Written](https://wordpress.org/support/users/shaady4/reviews/) * [Topics Replied To](https://wordpress.org/support/users/shaady4/replied-to/) * [Engagements](https://wordpress.org/support/users/shaady4/engagements/) * [Favorites](https://wordpress.org/support/users/shaady4/favorites/) Search replies: ## Forum Replies Created Viewing 15 replies - 1 through 15 (of 133 total) 1 [2](https://wordpress.org/support/users/shaady4/replies/page/2/?output_format=md) [3](https://wordpress.org/support/users/shaady4/replies/page/3/?output_format=md)… [7](https://wordpress.org/support/users/shaady4/replies/page/7/?output_format=md) [8](https://wordpress.org/support/users/shaady4/replies/page/8/?output_format=md) [9](https://wordpress.org/support/users/shaady4/replies/page/9/?output_format=md) [→](https://wordpress.org/support/users/shaady4/replies/page/2/?output_format=md) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Secure Passkeys] Shortcode not working for me](https://wordpress.org/support/topic/shortcode-not-working-for-me-3/) * [Woozy Face](https://wordpress.org/support/users/shaady4/) * (@shaady4) * [8 months ago](https://wordpress.org/support/topic/shortcode-not-working-for-me-3/#post-18679525) * Hi, similar issue here using the button under the woo login form works but if i put a shortcode on the same page and hide the one created by the plugin (cause styling and stufff) it doesn’t work for me either i also use elementor. Can you maybe, perhaps, if you are willing to, and don’t waste any of your time on it, think about making your awesome plugin more compatible with elementor? But only if you are willing to if not i can live with that! also thank you for the moment you took to read this message, i’m sorry if you are going to repeat yourself, or if i wasted your time. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[All-In-One Security (AIOS) – Security and Firewall] Help I am behind a vpn now](https://wordpress.org/support/topic/help-i-am-behind-a-vpn-now/) * Thread Starter [Woozy Face](https://wordpress.org/support/users/shaady4/) * (@shaady4) * [1 year, 5 months ago](https://wordpress.org/support/topic/help-i-am-behind-a-vpn-now/#post-18208151) * 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. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[WooCommerce Stripe Payment Gateway] Issue with SEPA Tokens in WooCommerce Stripe Payment Gateway Version 8.5.2](https://wordpress.org/support/topic/issue-with-sepa-tokens-in-woocommerce-stripe-payment-gateway-version-8-5-2/) * Thread Starter [Woozy Face](https://wordpress.org/support/users/shaady4/) * (@shaady4) * [1 year, 9 months ago](https://wordpress.org/support/topic/issue-with-sepa-tokens-in-woocommerce-stripe-payment-gateway-version-8-5-2/#post-18019394) * 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! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[WooCommerce Stripe Payment Gateway] Issue with SEPA Tokens in WooCommerce Stripe Payment Gateway Version 8.5.2](https://wordpress.org/support/topic/issue-with-sepa-tokens-in-woocommerce-stripe-payment-gateway-version-8-5-2/) * Thread Starter [Woozy Face](https://wordpress.org/support/users/shaady4/) * (@shaady4) * [1 year, 9 months ago](https://wordpress.org/support/topic/issue-with-sepa-tokens-in-woocommerce-stripe-payment-gateway-version-8-5-2/#post-18019388) * 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 1 year, 9 months ago by [Woozy Face](https://wordpress.org/support/users/shaady4/). - This reply was modified 1 year, 9 months ago by [Woozy Face](https://wordpress.org/support/users/shaady4/). Reason: Formatting issues * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[WooCommerce Stripe Payment Gateway] Issue with SEPA Tokens in WooCommerce Stripe Payment Gateway Version 8.5.2](https://wordpress.org/support/topic/issue-with-sepa-tokens-in-woocommerce-stripe-payment-gateway-version-8-5-2/) * Thread Starter [Woozy Face](https://wordpress.org/support/users/shaady4/) * (@shaady4) * [1 year, 10 months ago](https://wordpress.org/support/topic/issue-with-sepa-tokens-in-woocommerce-stripe-payment-gateway-version-8-5-2/#post-17960779) * > 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 1 year, 10 months ago by [Woozy Face](https://wordpress.org/support/users/shaady4/). * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[WooCommerce Stripe Payment Gateway] Issue with SEPA Tokens in WooCommerce Stripe Payment Gateway Version 8.5.2](https://wordpress.org/support/topic/issue-with-sepa-tokens-in-woocommerce-stripe-payment-gateway-version-8-5-2/) * Thread Starter [Woozy Face](https://wordpress.org/support/users/shaady4/) * (@shaady4) * [1 year, 10 months ago](https://wordpress.org/support/topic/issue-with-sepa-tokens-in-woocommerce-stripe-payment-gateway-version-8-5-2/#post-17960141) * 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 1 year, 10 months ago by [Woozy Face](https://wordpress.org/support/users/shaady4/). * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[All-In-One Security (AIOS) – Security and Firewall] all of a sudden my site redirects everything to 127.0.0.1](https://wordpress.org/support/topic/all-of-a-sudden-my-site-redirects-everything-to-127-0-0-1/) * Thread Starter [Woozy Face](https://wordpress.org/support/users/shaady4/) * (@shaady4) * [2 years, 3 months ago](https://wordpress.org/support/topic/all-of-a-sudden-my-site-redirects-everything-to-127-0-0-1/#post-17451394) * 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 2 years, 3 months ago by [Woozy Face](https://wordpress.org/support/users/shaady4/). * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[All-In-One Security (AIOS) – Security and Firewall] all of a sudden my site redirects everything to 127.0.0.1](https://wordpress.org/support/topic/all-of-a-sudden-my-site-redirects-everything-to-127-0-0-1/) * Thread Starter [Woozy Face](https://wordpress.org/support/users/shaady4/) * (@shaady4) * [2 years, 3 months ago](https://wordpress.org/support/topic/all-of-a-sudden-my-site-redirects-everything-to-127-0-0-1/#post-17444890) * 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. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[All-In-One Security (AIOS) – Security and Firewall] Cookie slug leeds to 127.0.0.1 seems not accepted since last update?!](https://wordpress.org/support/topic/slug-leeds-to-127-0-0-1-seemsnot-accepted-since-last-update/) * Thread Starter [Woozy Face](https://wordpress.org/support/users/shaady4/) * (@shaady4) * [2 years, 8 months ago](https://wordpress.org/support/topic/slug-leeds-to-127-0-0-1-seemsnot-accepted-since-last-update/page/2/#post-17080740) * 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 2 years, 8 months ago by [Woozy Face](https://wordpress.org/support/users/shaady4/). * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[All-In-One Security (AIOS) – Security and Firewall] Cookie slug leeds to 127.0.0.1 seems not accepted since last update?!](https://wordpress.org/support/topic/slug-leeds-to-127-0-0-1-seemsnot-accepted-since-last-update/) * Thread Starter [Woozy Face](https://wordpress.org/support/users/shaady4/) * (@shaady4) * [2 years, 8 months ago](https://wordpress.org/support/topic/slug-leeds-to-127-0-0-1-seemsnot-accepted-since-last-update/page/2/#post-17069747) * What are you talking about [@alihosseini20368](https://wordpress.org/support/users/alihosseini20368/). Please start your own topic. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[All-In-One Security (AIOS) – Security and Firewall] Cookie slug leeds to 127.0.0.1 seems not accepted since last update?!](https://wordpress.org/support/topic/slug-leeds-to-127-0-0-1-seemsnot-accepted-since-last-update/) * Thread Starter [Woozy Face](https://wordpress.org/support/users/shaady4/) * (@shaady4) * [2 years, 9 months ago](https://wordpress.org/support/topic/slug-leeds-to-127-0-0-1-seemsnot-accepted-since-last-update/#post-17046627) * 4 days later same issue [@hjogiupdraftplus](https://wordpress.org/support/users/hjogiupdraftplus/) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[All-In-One Security (AIOS) – Security and Firewall] Cookie slug leeds to 127.0.0.1 seems not accepted since last update?!](https://wordpress.org/support/topic/slug-leeds-to-127-0-0-1-seemsnot-accepted-since-last-update/) * Thread Starter [Woozy Face](https://wordpress.org/support/users/shaady4/) * (@shaady4) * [2 years, 9 months ago](https://wordpress.org/support/topic/slug-leeds-to-127-0-0-1-seemsnot-accepted-since-last-update/#post-17036852) * Okay that gave access back, thanks! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[All-In-One Security (AIOS) – Security and Firewall] Cookie slug leeds to 127.0.0.1 seems not accepted since last update?!](https://wordpress.org/support/topic/slug-leeds-to-127-0-0-1-seemsnot-accepted-since-last-update/) * Thread Starter [Woozy Face](https://wordpress.org/support/users/shaady4/) * (@shaady4) * [2 years, 9 months ago](https://wordpress.org/support/topic/slug-leeds-to-127-0-0-1-seemsnot-accepted-since-last-update/#post-17030655) * 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](https://send.easycomp.cloud/download/031868aec0421e9e/#_8-Meh33nZ6BNomdmPEVKg). I know it is tempting so, [click here instead, if you are not the one who is giving support ](https://www.dont.click/) 😉 . Thanks! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[All-In-One Security (AIOS) – Security and Firewall] Cookie slug leeds to 127.0.0.1 seems not accepted since last update?!](https://wordpress.org/support/topic/slug-leeds-to-127-0-0-1-seemsnot-accepted-since-last-update/) * Thread Starter [Woozy Face](https://wordpress.org/support/users/shaady4/) * (@shaady4) * [2 years, 9 months ago](https://wordpress.org/support/topic/slug-leeds-to-127-0-0-1-seemsnot-accepted-since-last-update/#post-17028666) * 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! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[All-In-One Security (AIOS) – Security and Firewall] Cookie slug leeds to 127.0.0.1 seems not accepted since last update?!](https://wordpress.org/support/topic/slug-leeds-to-127-0-0-1-seemsnot-accepted-since-last-update/) * Thread Starter [Woozy Face](https://wordpress.org/support/users/shaady4/) * (@shaady4) * [2 years, 9 months ago](https://wordpress.org/support/topic/slug-leeds-to-127-0-0-1-seemsnot-accepted-since-last-update/#post-17027294) * It happend again…. Viewing 15 replies - 1 through 15 (of 133 total) 1 [2](https://wordpress.org/support/users/shaady4/replies/page/2/?output_format=md) [3](https://wordpress.org/support/users/shaady4/replies/page/3/?output_format=md)… [7](https://wordpress.org/support/users/shaady4/replies/page/7/?output_format=md) [8](https://wordpress.org/support/users/shaady4/replies/page/8/?output_format=md) [9](https://wordpress.org/support/users/shaady4/replies/page/9/?output_format=md) [→](https://wordpress.org/support/users/shaady4/replies/page/2/?output_format=md)