sam_wag

[fiery grove]

Hello 👋
I don't see an outage on our end. You'd likely want to talk to your hosting provider to see if they're incorrectly blocking outgoing requests somehow

[stark parrot]

thanks, i am waiting on Dreamhosts' response. Does this report from someone else with a similar problem make sense?

"It sounds like the problem was caused by Stripe. We were able to demonstrate that if we send a curl command to Stripe’s API from my IP, it was timing out, yet working for other IPs. Stripe said AWS may have blocked the IP and they are investigating."

[fiery grove]

Can you share the IP you're making the requests from?

[stark parrot]

Yes one moment

69.163.163.11

[fiery grove]

yeah I'm not seeing on our blocklist/banlist

I'd recommend writing in via our support team
https://support.stripe.com/?contact=true

That way support can put you in touch with the right team who can investigate, It would be a good idea to reach out to AWS too just in case they're blocking the IP

[stark parrot]

Thanks.

I don't use AWS though

[fiery grove]

Stripe infra uses AWS and they could block IP if they deem it malicious. Also, seems like you already have a ticket with us?

[stark parrot]

Yeah I was using the web chat and discovered this discord. You've been more responsive, thank you. I can continue on the email ticket if needed

[fiery grove]

Yeah would recommend continuing through email as they'd have deeper context. But really, you/your hosting provider should talk to AWS

[muted minnow]

Hey @stark parrot what did you hear from your hosting provider?

[stark parrot]

We are completing some test from the server side and requests made to Stripe are sent but never replied, it looks like they have a block on their end over our servers or your IP address 69.163.163.129

This is the output for a traceroute you can Share with Stripe team:

dh_dtzdpt@greatersagegrouse:~/skelepedia.org$ traceroute api.stripe.com
traceroute to api.stripe.com (54.68.165.206), 30 hops max, 60 byte packets
1 ip-69-163-160-1.dreamhost.com (69.163.160.1) 1.780 ms 1.719 ms 1.670 ms
2 pdx1-cr-2.sd.dreamhost.com (66.33.200.3) 0.937 ms pdx1-cr-1.sd.dreamhost.com (66.33.200.2) 0.909 ms 0.865 ms
3 pdx1-bdr-1.sd.dreamhost.com (66.33.200.0) 0.827 ms 0.745 ms 0.693 ms
4 amazon2.nwax.net (198.32.195.102) 1.174 ms 1.124 ms 1.062 ms
5 * * *
6 * * *
7 * * *
8 * * *

That's from Dreamhost. It's a slightly different IP than the one I gave earlier, so I was wondering if you could check that one

[muted minnow]

api.stripe.com is configured to not respond to ICMP requests (which traceroute and ping use) so it is expected for traceroute to not reach our servers

[stark parrot]

ok -- a curl request also doesn't work

or any api requests

[muted minnow]

That IP is not on any of our block lists as far as I can see. I can reach out to the colleague on your ticket to add that to the AWS request

Though as hanzo said, it may be helpful to reach out to AWS yourself as well.

I'd highly recommend working through that ticket in future to keep all of this in one place. Same team as this server manages your ticket and we can talk about more details specific to your situaiton through email than we can on a public server

[stark parrot]

AWS charges for tech support and I only use stripe and dreamhost for my product

Thanks for your time though, I'll tell dreamhost and try to get them to reach out

I'll keep it back in the email