#Muneeb
1 messages ยท Page 1 of 1 (latest)
๐ happy to help
this might be either an internet connection issue or VPN related
Also I've contacted my hosting / server provider on this issue and they said that Stripe is blocking our outbound IP.
[Tue Feb 28 10:31:31.163995 2023] [core:error] [pid 209834:tid
140648906737408] [client 64.98.209.211:56830] End of script output before
headers: curl.php
Then, we test the Stripe ip with the most generic test using the same
outbound ip address that your requests use, which is 208.113.161.205:
no response from 34.237.201.68, stripe
usr_ctlimo@louisa:~/topctlimo.com/new$ ping 34.237.201.68
PING 34.237.201.68 (34.237.201.68) 56(84) bytes of data.
@astral ember Are you still there?
yes sorry taking a look at this
okay, thank you ๐
Have you added the IP addresses api.stripe.com resolves to to your server allowlist(s)? https://stripe.com/docs/ips#ip-addresses
Can you please run our reachability script on your server(s) to confirm the connectivity issues and share results here: https://github.com/stripe/stripe-reachability
ok, let me check
There's activity in our logs from other IPs on the same subnet (208.113.161.*) which would indicate we're not blocking your IP. I suspect this is a server/firewall configuration issue.
You can see at the end of the report the API connection for a test curl timesout:
hecking curl_https...
+ curl -Iv https://api.stripe.com/healthcheck
* Trying 34.200.27.109...
* TCP_NODELAY set
* connect to 34.200.27.109 port 443 failed: Connection timed out
* Trying 34.200.47.89...
* TCP_NODELAY set
* After 85329ms connect time, move on!
* connect to 34.200.47.89 port 443 failed: Connection timed out
* Trying 34.202.153.183...
* TCP_NODELAY set
* After 42663ms connect time, move on!
* connect to 34.202.153.183 port 443 failed: Connection timed out
* Failed to connect to api.stripe.com port 443: Connection timed out
* Closing connection 0
curl: (7) Failed to connect to api.stripe.com port 443: Connection timed out
ERROR: curl_https check failed
I'd try adding our IP addresses form the URL I shared to your firewall allowlist, or ask your hosting provider to configure it accordingly
ok
@quasi rock did you configure your server/host to allow connections to the IP addresses I gave you?
yes
Did you try re-running the reachability script after you did that?
yes, its same, let me check again
Have you tried making API requests from a different host/server?
What about this?