#kb_api
gritty caveBOT
👋 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/1435653597751808050
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
tiny elbow
I have also upgraded to the latest SDK package as of this morning, that did not help.
var products = _productService.List(new ProductListOptions { Active = true });
This is failing to ever execute, I have only 3 products.
C:\Users\Administrator>curl -I https://api.stripe.com
HTTP/1.1 404 Not Found
Server: nginx
Date: Wed, 05 Nov 2025 14:58:12 GMT
Content-Type: application/json
Content-Length: 362
Connection: keep-alive
C:\Users\Administrator>nslookup api.stripe.com
Server: one.one.one.one
Address: 1.1.1.1
Non-authoritative answer:
Name: api.stripe.com
Addresses: 34.200.27.109
34.202.153.183
34.200.47.89
C:\Users\Administrator>curl -v https://api.stripe.com/v1/products
- Host api.stripe.com:443 was resolved.
- IPv6: (none)
- IPv4: 34.200.47.89, 34.200.27.109, 34.202.153.183
- Trying 34.200.47.89:443...
- schannel: disabled automatic use of client certificate
- ALPN: curl offers http/1.1
- ALPN: server accepted http/1.1
- Connected to api.stripe.com (34.200.47.89) port 443
- using HTTP/1.x
GET /v1/products HTTP/1.1
Host: api.stripe.com
User-Agent: curl/8.13.0
Accept: /
< HTTP/1.1 401 Unauthorized
< Server: nginx
< Date: Wed, 05 Nov 2025 14:57:26 GMT
< Content-Type: application/json
wary pivot
Nothing has changed from a networking/infra perspective recently?
Also that last log shows that you are getting a response
I see 401 unauthorized
tiny elbow
Yes, but that is just a curl test.
To ensure that I am not getting a 403 Forbidden.
We have made zero changes, Stripe actually took our platform offline last night because of this. We get the product information from Stripe to list on the site, and we cannot, so the site hung.
wary pivot
Stripe actually took our platform offline last night because of this
What do you mean by this? Like your account has been closed?
tiny elbow
No. Like this bug that is happening caused the entire site to crash.
wary pivot
Can you run this on the affected server: https://github.com/stripe/stripe-reachability
And share the results in here
tiny elbow
Have a windows version?
wary pivot
No unfortunately not
But if you haven't changed anything on your network and can't reach us it is possible the ip was blacklisted for some reason (can happen if it's a shared ip)
But you'd have to write into our support team for them to investigate this
tiny elbow
It is not a shared IP
tiny elbow
I created a ticket, they said 24 hours. 🙁
wary pivot
I also recommend opening a ticket with your hosting provider
In case something changed on their end from a network perspective
tiny elbow
But I have nothing to prove though, all curl tests and nsloopups are good.
wary pivot
Hm that doesn't make sense
Are all stripe api calls hanging from the sdk
Or just the product list one
What does running curl -Iv https://api.stripe.com/healthcheck return
tiny elbow
I through it through a proxy and it now works, same code.
C:\Users\Administrator>curl -Iv https://api.stripe.com/healthcheck
- Host api.stripe.com:443 was resolved.
- IPv6: (none)
- IPv4: 34.200.47.89, 34.200.27.109, 34.202.153.183
- Trying 34.200.47.89:443...
- schannel: disabled automatic use of client certificate
- ALPN: curl offers http/1.1
- ALPN: server accepted http/1.1
- Connected to api.stripe.com (34.200.47.89) port 443
- using HTTP/1.x
HEAD /healthcheck HTTP/1.1
Host: api.stripe.com
User-Agent: curl/8.13.0
Accept: /
< HTTP/1.1 200 OK
HTTP/1.1 200 OK
< Server: nginx
Server: nginx
< Date: Wed, 05 Nov 2025 16:02:07 GMT
Date: Wed, 05 Nov 2025 16:02:07 GMT
< Content-Type: text/plain; charset=utf-8
Content-Type: text/plain; charset=utf-8
< Content-Length: 66
Content-Length: 66
< Connection: keep-alive
Connection: keep-alive
< access-control-allow-origin: *
access-control-allow-origin: *
< Strict-Transport-Security: max-age=31556926; includeSubDomains; preload
Strict-Transport-Security: max-age=31556926; includeSubDomains; preload
<
- Connection #0 to host api.stripe.com left intact
tiny elbow
Are all stripe api calls hanging from the sdk
I would presume at this point, all of them.
But I cannot get the server to boot as this is the first call
If I surf to that address : api.stripe.com at your service! What can I do for you today? (Up)