Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Ping goes to a different IP address? Why? (RESOLVED because I can't type properly)
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Ping goes to a different IP address? Why? (RESOLVED because I can't type properly)

geodirkgeodirk Member
edited November 2019 in Help

So I'm trying to setup my nginx server without luck. I'm always getting a timeout error. From the commandline, I can curl localhost and I get the correct nginx welcome page. Same thing if I curl my IP address. When I curl my domain name, I get this:

curl: (7) Failed to connect to chat.securemeetup.net port 80: No route to host

Trying to just ping either my domain name or my IP address from the server itself, I get something strange:

root@localhost:/etc# ping 104.224.xxx.xxx
PING 104.224.xxx.xxx (104.224.xxx.xxx) 56(84) bytes of data.
From 72.37.144.xx icmp_seq=1 Time to live exceeded
From 72.37.144.xx icmp_seq=2 Time to live exceeded
^C

Why would this happen? Why would it all of a sudden route to a totally different IP address on a different continent?

Comments

  • Mr_TomMr_Tom Member, Host Rep

    A gateway/routing device further upstream is reporting the failure before it gets to your IP.

    Thanked by 1geodirk
  • @Mr_Tom said:
    A gateway/routing device further upstream is reporting the failure before it gets to your IP.

    Anything I can do about it? Or is this someone else's problem that will eventually clear up?

  • rm_rm_ IPv6 Advocate, Veteran
    edited November 2019

    geodirk said: Why would it all of a sudden route to a totally different IP address on a different continent?

    What continent did you expect? Both 104.224.73.189 and 72.37.144.90 appear to be in the US. Also it is useless to hide your IPs, but show your domain chat.securemeetup.net, which resolves to the full IP.

    Check your "104...." IP for typos, are you using the correct one. If yes, then it's not properly routed to the Internet currently, try contacting your provider.

    Thanked by 1solaire
  • DPDP Administrator, The Domain Guy

    Trace and you'll see.

  • @rm_ said:
    Also it is useless to hide your IPs, but show your domain chat.securemeetup.net, which resolves to the full IP.

    Doh!

  • @thedp said:
    Trace and you'll see.

    From my server to itself:

    root@localhost:/etc# traceroute chat.securemeetup.net
    traceroute to chat.securemeetup.net (104.224.73.189), 64 hops max
      1   104.244.72.1  0.425ms  0.295ms  0.316ms
      2   204.68.252.128  0.575ms  0.424ms  0.424ms
      3   154.25.12.69  1.382ms  1.236ms  1.272ms
      4   154.54.38.145  5.492ms  5.485ms  5.450ms
      5   130.117.1.117  5.712ms  5.508ms  5.310ms
      6   130.117.15.150  4.966ms  4.937ms  4.915ms
      7   89.149.143.130  83.518ms  83.567ms  84.141ms
      8   72.37.144.90  83.714ms  83.675ms  83.622ms
      9   72.37.144.89  83.611ms  83.686ms  83.649ms
     10   72.37.144.90  83.721ms  83.672ms  83.670ms
     11   72.37.144.89  83.656ms  83.878ms  83.728ms
     12   72.37.144.90  84.111ms  83.962ms  84.199ms
     13   72.37.144.89  83.702ms  83.734ms  91.338ms
    

    Then it just cycles between those last two IP addresses forever...

  • DPDP Administrator, The Domain Guy

    Check with your provider about the routing.

  • rm_rm_ IPv6 Advocate, Veteran
    edited November 2019

    geodirk said: From my server to itself

    Did you double-check the IP? Such trace shows you are using a different IP entirely, than what your server has. Post the output of ip addr and ip route.

    edit: yep, you have a typo: 224 => 244.

    1   104.244.72.1  0.425ms  0.295ms  0.316ms
    Thanked by 2uptime geodirk
  • Thanked by 1Janevski
  • geodirkgeodirk Member
    edited November 2019

    @rm_ said:

    edit: yep, you have a typo: 224 => 244.

    Sigh...yep...stupid typo. I've been an idiot twice today...and the day is still young. :-(

    Thanks all! Problem resolved.

Sign In or Register to comment.