vivision_webhooks

[primal narwhal]

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1506825936119795867

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

• vivision_webhooks, 10 hours ago, 18 messages

[brazen lynx]

HTTP status 404 (Not found) indicates that the endpoint can't be found. Unfortunately, Stripe doesn't have the visibility how the server is set up and why the server is not reachable. I'd recommend checking with the hosting service provider why this happened

[brazen lynx]

The issue here is that your server returns 404. This is not the status code returned from Stripe

Do you have a specific endpoint in your server for receiving Webhook events? If your domain is https://www.example.com, you will also need to include the path such as /webhook on your domain to receive the events if you have any. The full path will look like https://www.example.com/webhook

[chrome iron]

i have tried many different ways

been trying for 2 days now.

[brazen lynx]

Have you tried to use other method to check whether your endpoint is able to accept a request? For example, using cURL or postman?

I'd like to reiterate that this 404 error is being returned by your server, not by Stripe, so this is unfortunately outside the scope of what we can assist with directly.

Here are a few recommendations to help resolve this:

1. Add additional logging on your server to identify why the endpoint is returning a 404 response.
2. Check with your hosting provider to confirm the endpoint is reachable and properly configured.
3. Ensure that your server is set up to accept POST requests at the webhook URL. Stripe sends webhook events as POST requests, which differs from the GET requests typically made by a browser.

[chrome iron]

i appoligize, i am unfortunatley at the mercy of what the AIstudio AI keeps saying.. Im curious, If i am in Toronto Cananda and have been doing test payments from here (all successfull). But i notice my webhook and othe rcloudrun config are set for eastUS-1 (North Carolina or ssomething). does that or could that cause an error,

sorry if its a dumb question , this s my first time trying to attempt anything of this calibre and i understand that i may be out of my element a lil bit in terms of lacking the nessisarry calibre of tech knowledge etc.

[brazen lynx]

The region difference between your location and your cloud configuration is unlikely to be the cause of a 404 error. A 404 typically means that the URL path was not found on your server, so the issue is more likely related to how the endpoint route is configured in your application rather than a regional setting.

Here are a few things I'd suggest checking:

1. Confirm that the webhook URL registered in your Stripe Dashboard exactly matches the route defined in your cloud application (including any trailing slashes or path segments)
2. Make sure your application has a route set up to handle POST requests at that specific path
3. Check your cloud deployment logs to see if the request is reaching your service at all, or if it's being rejected before it gets to your application code

Since this is related to your server configuration, the deployemnt documentation or their support team would be the best resource for troubleshooting further. You might also find it helpful to test your endpoint directly using a tool like curl or Postman to confirm it responds correctly to POST requests.

[chrome iron]

are u reffering to what it shows in the first two screen shots i uploaded and sent, how the 404 error that i resent, (refreshed stripe, and refreshed cloud console pages to snap a screen to show that stripe is getting the same 404 error message at the same time sbout the same one in cloud etc...

[brazen lynx]

Yes, what you're seeing confirms exactly what I mentioned. The 404 error appearing in both Stripe and your Cloud Console is the same event. Stripe sends the webhook to your server, your server returns a 404 response, and that error is then reflected on both sides.

This means both Stripe and Cloud Console are showing the same problem from different perspectives. Stripe is showing that it sent a request and received a 404 back, while Cloud Console is showing that it received a request but couldn't find the endpoint to handle it.

Going back to the mail analogy: it's like the sender (Stripe) getting a "return to sender" notice, and the post office at the destination (Cloud Run) also logging that a letter arrived but there was no matching mailbox. Both are recording the same failed delivery.

The fix would need to happen on your server side, specifically making sure the route or path your Cloud Run application is listening on matches the webhook URL you've configured in Stripe.

[chrome iron]

ok, so i need to either have a web hook that is striclky my web app domain/api/webhook(something etc.). or the issue is my cloud run (or firebase) issnt setup properly to make the event a closed loop after getting theinitial mesage from stripe after the successful payments etc>ce

?

[brazen lynx]

It’s not necessarily about using your web domain with the endpoint path. The issue here is that the path you configured is not accessible by Stripe. Any domain will be fine.

[chrome iron]

well between listening to what aistudio told me to try and fix ths kink during what ended up being 3 days of trial and error and all of it consisted of trouble shooting how to try and write the webhook to work,

so i would qquadruple checkc that th ewebhook url was exactly what aistudio. needed, then after sending endless creenshoots showing this ai studio woulf wnt me to try this variatuon oof it, wheere i would repeat the process oall obver about . eevey 10 mins , thhe all oevr again for another 10 mnd etc, etc,et,c

i a wondering if there is some steps o neeed to manually do in cloud run , either to have it prepped correctly to not cause this error, or maybe usher along some of th epayment data manually the first time in order for it tobe able to then work proprtly

[brazen lynx]

Unfortunately, this is not something Stripe is able to assist with beyond providing context around the error. The root cause is related to your server configuration, which falls outside the scope of Stripe's support.

If you are not familiar with managing your deployment or server settings, I’d recommend engaging an experienced developer or systems administrator to assist you further.

[chrome iron]

i totally understand,

[brazen lynx]

Just to let you know, we will not be responding to further questions regarding 404 errors or Cloud Run configuration. If you have any other questions related to Stripe API or code integrations, we are happy to help!

[chrome iron]

hen i try to ask differnt ai's to help me (talk me) through the process whilei eather video stream or send screens the whole time they first tell me to simply double check theat th ewebhooks are both matching (which is exacly what i have been doing over and over till i end up aleep at my desk, only to have dreams of that same thing). The only other things i can convince them to try and do involves going in and editing my source code which i something i would DEF have a better odds of sabatoging the code than anything else, adn AIstudio would then also explain to NOT touch any code that its alll setup to work automated that all i need to do is dounle check the webhooks match. lol fml

I really appreaciate, it. I really do

so stripe is getting the error not at the same time as (****) but im guessing because of it. ?

can i just change my setup in stripe to use the default confrimaton page and set up stripe to email the user regarding their payment\

[brazen lynx]

What kind of email are you referring to? Is it a successful payment receipt email, or successful order on your website?

[chrome iron]

The customers email after the successfful payments,

or whatever leaving confirmation page on default does

every single payment went through right from the jump, even payment types i rarely have success using (KoHo). and even types that have never worked for me before ever, (joker, gift c etc.

[brazen lynx]

It's possible to send the successful payment receipt automatically by enabling "Successful payments" in the email settings in the Dashboard: https://dashboard.stripe.com/settings/emails

More details can be found in https://docs.stripe.com/receipts

[primal narwhal]

⛔️ Stripe developers have stepped away for a short while

Please leave your questions here, and we’ll respond as soon as we're back! If you need help urgently, you can contact Stripe support for help.