#6hills_error
1 messages ¡ Page 1 of 1 (latest)
đ 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/1388059978283356250
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Are you connecting from a server or from your local?
I tried connection locally and after that the server stopped working
local connection worked
theses error are coming from a server for both test and live modes
@orchid hollow errors look like this
it's mainly comes from this endpoint: api.stripe.com/v1/identity/verification_sessions
Do you mean other endpoint works fine?
Could you try this reachability test on your server and let us know the response: https://github.com/stripe/stripe-reachability/tree/master
yes, only this endpoint api.stripe.com/v1/identity/verification_sessions
Does this occur before you have a request id req_xxx?
hi! I'm taking over this thread.
sorry not sure how to answer that: here's the details or the error in raw:
raw: {
message: 'An error occurred with our connection to Stripe.',
detail: Error: write EPROTO 4078E487487F0000:error:0A000460:SSL routines:ssl3_read_bytes:tlsv1 alert no application protocol:ssl/record/rec_layer_s3.c:909:SSL alert number 120
at WriteWrap.onWriteComplete [as oncomplete] (node:internal/stream_base_commons:95:16)
at WriteWrap.callbackTrampoline (node:internal/async_hooks:130:17) {
errno: -71,
code: 'EPROTO',
syscall: 'write'
}
},
I just made an empty POST request to api.stripe.com/v1/identity/verification_sessions, and I did get a response from Stripe.
so there must be an issue on your end.
It happens only for that endpoint for use
can you try the reachablility tool mentioned above?
every status is ok, and prod transactions come through. It's only a request for that endpoint that throws this error
I understand. can you try the reachability tool in case it finds anything?
yes as mentioned above it worked and every status is ok
can you share a screenshot of the output of the reachability tool?