#krutarth_reachability

1 messages · Page 1 of 1 (latest)

trim saddleBOT
tawdry sirenBOT
#

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

trim saddleBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1252627960410669077

📝 Have more to share? Add details, code, screenshots, videos, etc. below.

tawdry sirenBOT
oak geyser
trim saddleBOT
#

krutarth_reachability

night geyser
#

output:

========================================
Checking os...
OK: os check

Checking ip...

  • curl -4 --write-out \n ifconfig.co/json
    {
    "ip": "49.36.67.194",
    "ip_decimal": 824460226,
    "country": "India",
    "country_iso": "IN",
    "country_eu": false,
    "region_name": "Gujarat",
    "region_code": "GJ",
    "zip_code": "380007",
    "city": "Ahmedabad",
    "latitude": 23.0276,
    "longitude": 72.5871,
    "time_zone": "Asia/Kolkata",
    "asn": "AS55836",
    "asn_org": "Reliance Jio Infocomm Limited",
    "user_agent": {
    "product": "curl",
    "version": "8.4.0",
    "raw_value": "curl/8.4.0"
    }
    }
    OK: ip check
    ========================================
    Checking route...
    /usr/sbin/traceroute
  • traceroute -n -m 20 api.stripe.com
    traceroute: Warning: api.stripe.com has multiple addresses; using 52.74.114.251
    traceroute to api.stripe.com (52.74.114.251), 20 hops max, 40 byte packets
    1 192.168.29.1 3.887 ms 5.537 ms 3.438 ms
    2 10.245.144.1 5.952 ms 8.320 ms 8.137 ms
    3 172.16.25.1 8.309 ms 8.274 ms 7.903 ms
    4 192.168.74.190 7.410 ms
    192.168.74.192 8.225 ms
    192.168.74.190 7.726 ms
    5 172.26.100.228 7.653 ms 8.262 ms 7.763 ms
    6 172.26.100.210 8.624 ms 7.806 ms 8.075 ms
    7 192.168.38.29 8.139 ms
    192.168.38.25 7.950 ms
    192.168.38.29 8.091 ms
    8 * * *
    9 * * *
    10 * * *
    11 * * *
    12 * * *
    13 * 103.198.140.64 74.689 ms 59.539 ms
    14 * * *
    15 * * *
    16 * 99.82.178.28 995.238 ms *
    17 * * *
    18 * * *
    19 * * *
    20 * * *
    OK: route check
    ========================================
    Checking curl_https...
  • curl -Iv https://api.stripe.com/healthcheck
  • Trying 52.74.98.83:443...
  • Connected to api.stripe.com (52.74.98.83) port 443
  • ALPN: curl offers h2,http/1.1
  • (304) (OUT), TLS handshake, Client hello (1):
  • CAfile: /etc/ssl/cert.pem
  • CApath: none
  • SSL connection timeout
  • Closing connection
    curl: (28) SSL connection timeout
    ERROR: curl_https check failed

How to resolve this?

oak geyser
#

Hard to say, do you have rules in your network controlling where you're allowed to make requests to?

night geyser
#

No rules!
The apis are working in the same machine for the last 1.5 yeears

#

They stopped working today, nothing is changed. Even no os update or anything