• Resolved sharon

    (@sharonmay)


    I’ve getting emails from Stripe to say my webhook endpoint is not working. This is what they say ”23 requests returned HTTP 404, indicating the URL doesn’t exist. You should verify the endpoint URL is correct in your Stripe webhook settings”.

    I have looked at the Stripe and it says ”HTTP status code 200 (OK)”.

    Stripe say that I need to return any status code between HTTP 200 to 299 for Stripe to consider the webhook event successfully delivered. So to me, this looks ok, though I’m no expert on this matter.

    It also says ”No failed webhook attempts in the past 15 days” in the Failed section.

    We’ve been receiving payments and they are going through ok. Or at least it appears so.

    When I login to my website, it won’t show anything under Payments other than ”Something went wrong. There was an error during authentication.”

    I also clicked on a link which opened this ”{“code”:”rest_no_route”,”message”:”No route was found matching the URL and request method.”,”data”:{“status”:404}}”

    I’ve checked everything that I can do, so please could you give me some advice. Many thx

    • This topic was modified 1 month, 2 weeks ago by sharon.

    The page I need help with: [log in to see the link]

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Support Ben Meredith

    (@benmeredithgmailcom)

    Hey @sharonmay !

    Glad you reached out, here!

    StellarPay, as a part of connecting to Stripe, automatically configures webhook (event) endpoint URLs. What those do is allow Stripe to communicate whenever something happens on the Stripe side, back to your website where StellarPay is installed.

    The message from Stripe there is indicating that the webhook endpoint URL that was functional no longer is. That can happen if (for example) you set up a testing site, connected to Stripe, and then later moved things to a production (live) site. Every time an event happens within Stripe that is set to go to that endpoint, it’ll try, fail, and let you know that it fails.

    So, I’ll need your help to see what specific endpoint URLs are failing, and if they are legitimate, it might point to some issue on your site that is blocking them. It could also be an “all clear, nothing to worry about” moment, if the URL is for a test site or something.

    Can you pass along the specific URL?

    There’s no security issue with sharing a webhook URL, as the only way to *do* anything with it is to be authenitcated with a token, etc. So you sharing the endpoint URL is not a problem.

    Plugin Support Ben Meredith

    (@benmeredithgmailcom)

    Hey @sharonmay

    I’m still digging into this while I wait to hear back from you, but your post here prompted me to write a comprehensive blurb in our documentation about (a) what webhooks are and (b) what’s going on when you connect to Stripe.

    Here’s that specific section of our docs (inspired by you! Thanks!)

    When you first connect to Stripe using StellarPay, the entire process of establishing those webhooks is done for you automatically. During that process, StellarPay tells Stripe to check and validate the specific endpoint URL that it is configuring. If it fails, it lets you know during the “onboarding” connection to Stripe.

    Since it sounds like yours did not let you know, that means that it was, at least initially, working.

    Then at some point in the intervening time, it stopped working. That points to something “outside” of StellarPay (and even potentially outside of WordPress itself) blocking requests to your website.

    A list of other plugins (specifically caching or security plugins) would be helpful as we continue to help you diagnose the issue.

    Thread Starter sharon

    (@sharonmay)

    Hello thank you for replying. My url is https://mad4mutts.co.uk/ and the webhook is https://mad4mutts.co.uk/wp-json/stellarpay/stripe/webhook/live

    Hope this is what you need. Ty Sharon

    Thread Starter sharon

    (@sharonmay)

    I’ve just seen your last message, it was very helpful. I installed the Health Check & Troubleshooting plugin, disabled everything and had a play around. I think it could be the LiteSpeed Cache plugin.

    It’s late where I am so tomorrow I’m going to install another. Come to think of it, your plugin is working okay on my other website and I don’t have the LiteSpeed Cache plugin installed. It’s probably the settings but I’ve been meaning to uninstall it for ages in favor of the one I’m using on my other website. So, I will let you know how it goes.

    Thread Starter sharon

    (@sharonmay)

    Morning, I removed the LiteSpeed Cache plugin and uploaded the other. I can now see the details in StellarPay dashboard – Payments that was there before because of the error i guess.

    I’m not sure if this is normal, but when I click on https://mad4mutts.co.uk/wp-json/stellarpay/stripe/webhook/live, it’s still showing this {“code”:”rest_no_route”,”message”:”No route was found matching the URL and request method.”,”data”:{“status”:404}}.

    Ty for your help. Sharon

    Plugin Support Ben Meredith

    (@benmeredithgmailcom)

    @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.

    Thread Starter sharon

    (@sharonmay)

    Nothing is showing errors. Yeah.

    I would like to make a suggestion for your website if I may, a troubleshooting section and a link to your support. I couldn’t find either before coming here.

    Many thx for your help Sharon

Viewing 7 replies - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.