Ben Meredith

I just attempted on my test site to go through the onboarding steps for 2fa (once on camera after a different time off camera) and had no trouble, so I am not sure what might be causing your issues, but I’m keen to get to the bottom of it.

Thanks!

…and I am juuuust now putting together that you are doing the 2FA onboarding, not the general onboarding. Let me try that on my test site to see if I see what you are seeing. Hold please.

Great question. Here’s a video that hopefully helps to explain what I mean (My 10PM brain last night didn’t do the best job of explaining what I meant)

Let me know if you need further clarification!

Hey @rebeccajd!

Welcome to the WordPress forums, and Solid Security! We can definitely get things sorted out here.

Some of the options under the tools menu are relatively advanced, and best done only by somebody who knows what they are doing. Specifically the options like removing admin users or changing database settings can go sideways easily

I’d recommend starting with the onboarding wizard, and going through there. We wrote this documentation to help get you started: https://solidwp.com/documentation/security/setup-guide/getting-started-with-solid-security/

Just walking through the onboarding and following the steps in that document will protect you from 99% of threats to your site.

Let me know if there’s any part of that doc that is confusing at all. I can both correct the doc, and get you all set.

Hi @kevp75,

That error message is most likely originating from the Two-Factor Authentication (2FA) module, based on some digging around in the codebase I just did.

Given that, my first troubleshooting step would be to disable the 2FA module (temporarily) and see if that allows onboarding to finish successfully.

If it does, then you can try again to enable 2FA and see if that works.

Let us know if that works.

Hi @giadaway !

Apologies for the slow turnaround here.

I just created a test site, added Solid Security, WooCommerce, and enabled “login during checkout” in the WooCommerce settings. Then I attempted several different ways to get the problem to happen, with no luck.

In order to resolve this problem, we’ll need to be able to replicate it, and that will probably start with some clear steps to see the problem happening. If you can provide us with a rundown of what settings you have related to that configured, what other plugins or theme settings you have configured, etc, that might get us closer to resolving things.

Also, try the process with the developer console open and let us know if you see any errors.

We’ll be happy to get to the bottom of it with you, either way.

Hey @teccrow,

Apologies for the slow turnaround here. I made a video for you to see how this might be resolved.

https://www.loom.com/share/d58e7fde8a4f4723bc396570d8bc912c?sid=0a5547a5-db19-47f4-9368-98cedb2b54fb

If you’re still seeing issues, I’ll need you to confirm what’s different about your setup than the one in my video. Thanks!

Hey @alphablossom

Following up here to make sure things are all set. Since we haven’t heard back, we’ll assume that @shanedelierrr ‘s recommendations worked.

If you still need assistance, definitely open a new forum post here!

Hey @captgoodhope !

We want to make sure you’re all set here. Because it’s been a few days, I’m inclined to mark this post as resolved, only because our system for monitoring replies makes it easy for Support forum posts to get missed.

So I am going to mark this one as resolved, but don’t hesitate at all to reach out again if you’re still having trouble!

Hey @herrschuessler

First off, apologies for the slow turnaround here.

Next, I just attempted on a test site to replicate what you’ve reported here, and was not able to. Here’s a video:

I also had a couple folks from our team attempt to replicate this and none of us are having any luck.

We’re closed over the weekend, so we might not see a reply until Monday, but as I mentioned in the video, the moment we are able to replicate this, we’re eager to resolve it. At this point, we’re not seeing a way to replicate it.

@sharonmay YES!

It sounds to me like this is resolved. When you check the list of webhook endpoints at https://dashboard.stripe.com/webhooks is it showing any of them with an error?

If not, you’re probably right that cache was to blame. That brings up an age-old adage that I should have lead with:

Something weird happening on your website? It’s probably caching.

Confucius, Probably

Let us know if things are not resolved, by opening a new forum post here.

I’m going to mark this as resolved for now, and head over to add a bit to the documentation about cache.

Well that was quick: our senior engineer got back to me with this code snippet that mimics that helper function:

https://gist.github.com/ravinderk/65575722eb90362421067992cc64dcb2

We figured it out!

This is an issue when the following order of events takes place:

1. Connect to Stripe
2. Manually (within the Stripe Dashboard) remove a Stripe webhook endpoint.
3. Attempt to disconnect from Stripe (from within the StellarPay Dashboard).
4. See errors.

What caused the issue is that when disconnecting Stripe, StellarPay goes and tries to unset the webhook endpoint URLs, and when it didn’t find the endpoint URLs, it fails in a non-graceful way.

In a future version (likely 1.4.0 forthcoming) we’ll solve the issue by telling StellarPay to just go ahead and disconnect from Stripe, even if you don’t find any webhook endpoint URLs.

Thanks for your patience and for your help making the product better. If you want to learn more about what’s happening on that Stripe connection, I recently wrote up a blurb about it in our documentation.

Thanks again! I’ll mark this issue as resolved, but if you’re still having issues don’t hesitate to open a new post here.

Hey @anphira !

Great questions, and one of them sent me down a code rabbit-hole that I never emerged from yesterday. (SO, apologies for the slow turnaround on replying!)

First question: StellarPay subscriptions currently supports Simple products only. The roadmap for adding in additional features is still very much in flux based on user input and demand, so we’d welcome a detailed comment on this feedback post.

Second question: There’s not currently helper function similar to wcs_user_has_subscription, but it’s definitely possible with some custom code. I’ve reached out to the development team on that, and will see what they can cook up for you.

This will make great documentation content, so thanks for helping us to make this new product better!

I’ll mark this post as resolved, but please keep the questions coming!

Hey Thomas (@zysservice) !

That email sounds like it’s coming from Stripe, and I have lots of questions about it.

(I’m also digging into why they are recommending an email on our end that is not functional, which feels like a separate issue. Your post here is the first I’ve seen that particular email address.)

For now, please reach out to us at https://stellarwp.com/contact-us/ and mention me (Ben Meredith) by name, which will get your message routed to me properly.

We’ll handle this for sure, but you’re right that the public forum is not a great spot for it. (so I’ll mark this as resolved here in favor of actually resolving it via email).

Thanks!