#AlexTakitani
broken lava
snow grail
Hi there
You said: ```It's redirecting to a stripe page, not to the one we ask it to
works on development, but not in production
Can you give me an example Checkout Session ID where you are seeing it redirect to an unexpected URL?
snow grail
Yeah that works
And what URL do you expect it to be redirecting to versus where are you seeing it redirect?
This is a live Checkout Session so I can't test with that
stoic cipher
it should go to our success page
that we pass when creating the checkout session
its leading us to this page: https://stripe.com/br/payments/checkout
hollow obsidian
Is this something you're also able to reproduce in test mode?
hollow obsidian
Hmm... do you have an example Checkout Session that already did the redirect that I can take a look at?
stoic cipher
Ok! Thanks
hollow obsidian
You're absolutely sure that you have no redirect configured at your success URL right? Were you using the same URL for your test mode sessions?
hollow obsidian
and were you using the same URL for your test mode sessions?
stoic cipher
aside from my test being localhost, and production our production url, yes
hollow obsidian
Can you do one more test for me - in production can you try using a different URL (like https://www.example.com/ ) for the success URL?
stoic cipher
Can't you debug the session I sent you, to check the urls?
Deploying this test to production will take some time from us
hollow obsidian
I looked at the session, but as far as I can see it's saying we went to the original URL (https://monespace.lakube.com/payments/20674?new_order=true)
stoic cipher
yes, that's where it should go
hollow obsidian
Yeah as far as I can see in our logs that's where it says we're redirecting to - so that's why I'm asking if you can do a different test (to see if it's something that happening in livemode no matter what URL you use, or if it's somethign weird with that URL specifically)
If it's faster - can you do a test mode checkout session that points to https://monespace.lakube.com/payments/20674?new_order=true instead of localhost and see what happens?
stoic cipher
I'm deploying a change to redirect to google for my user
give me a few mins please
This one redirected corretly
hollow obsidian
Yeah, so I think this is an issue with your specific URL
Is there any chance someone on your end reconfigured it to redirect to something else?
hollow obsidian
Do you have any logging on your end to see if that URL is being hit in any way?
stoic cipher
Yes, we repeated the test
my test went to the correct page
on another computer it goes to the wrong page
tryed cleaning cookies and such
raven rose
That sounds very unexpected, are you sure those sessions are being created with the same success url targets?
stoic cipher
yes, they only differ on the id of the order
raven rose
Can you share the ID of a session that ends up on an unexpected URL (and what that is)
Is this happening in both live and test mode?
If you sent a test mode session url I can try myself, too
raven rose
Unfortunately I can't try a live mode session myself
stoic cipher
I have this on my logs
Mar 01 20:16:14Z la-kube app/web.1 App 232 output: [f320549a-5910-4ae7-8d9b-95b454bd2670] method=GET path=/payments/20687 format=html controller=PaymentsController action=show status=302 duration=15.91 view=0.00 db=2.42 location=https://checkout.stripe.com/ params={"new_order"=>"true", "controller"=>"payments", "action"=>"show", "id"=>"20687"} exception= exception_object=
the location is weird
raven rose
That seems like it might be a referrer?
raven rose
https://checkout.stripe.com/c/pay/cs_live_a18jQHZeJAfmtgmwD5bqrPXSNTUmJl6rdnVEnA...
When i try to access the success url from here i get redirected to a login page
stoic cipher
yes, that's normal
I'm looking at the logs for older orders
and I don't have that location
Feb 21 14:40:32Z la-kube app/web.1 App 232 output: [1144fbe8-810d-464e-9874-0a31e0614325] method=GET path=/payments/20195 format=html controller=PaymentsController action=show status=200 duration=427.98 view=8.42 db=18.72 params={"new_order"=>"true", "controller"=>"payments", "action"=>"show", "id"=>"20195"} exception= exception_object=
modest adder
Hey synthrider has to go but I am catching up.
modest adder
Do you have any logging on your end to see if that URL is being hit in any way?
Just to completely clarify this point. Even when the user is actually directed to https://stripe.com/br/payments/checkout are you seeing a log line in your servers that shows your success URL being hit properly?
stoic cipher
yes
I have a user now, that was failing
and just worked
and this time, no location=https://checkout.stripe.com/ in the url
modest adder
Have you double checked your server's response to see if it is possible that it is redirecting to that br/payments/checkout page? After we've directed the user to your site I don't think Stripe.js would be able to redirect again
And I assume there are no errors in your server logs around the times that this error has happened?