Question

could not connect to remote host to tcp 80

Posted January 22, 2020 292 views
Networking

could not connect from DO clean droplet to domain.com:80

smc2-nl# telnet domain.com 80
Trying 1.1.1.1…
^C
smc2-nl#

My ip 2.2.2.2

smc2-nl# iptables -vnL
Chain INPUT (policy ACCEPT 6928 packets, 468K bytes)
pkts bytes target prot opt in out source destination

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination

Chain OUTPUT (policy ACCEPT 5813 packets, 706K bytes)
pkts bytes target prot opt in out source destination

smc2-nl#

From other servers everything is ok.

edited by alexdo

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
3 answers

Hello, @promzonaservices

Have you tried whitelisting the IP of the droplet and then trying again (if you’re having access of course). Can you also perform a traceroute command from your droplet and compare this to a traceroute test from other server/location to see where the packet loss is?

Running traceroute from Linux:

traceroute 1.1.1.1

Windows:

tracert 1.1.1.1
  • Make sure to change 1.1.1.1 with the actual IP address or domain name

Let me know how it goes.

Regards,
Alex

hi, @alexdo

smc2-nl# traceroute 1.1.1.1
traceroute to 1.1.1.1 (1.1.1.1), 30 hops max, 60 byte packets
1 128.199.32.253 (128.199.32.253) 0.737 ms 128.199.32.254 (128.199.32.254) 0.724 ms 0.798 ms
2 138.197.250.112 (138.197.250.112) 1.188 ms 138.197.250.120 (138.197.250.120) 0.985 ms 138.197.250.98 (138.197.250.98) 1.079 ms
3 138.197.250.84 (138.197.250.84) 0.947 ms 138.197.250.88 (138.197.250.88) 0.928 ms 138.197.250.84 (138.197.250.84) 1.026 ms
4 ams-ix.as13335.net (80.249.211.140) 6.086 ms 6.080 ms 6.652 ms
5 one.one.one.one (1.1.1.1) 1.250 ms 1.245 ms 1.229 ms
smc2-nl#

  • Hello, @promzonaservices

    You would need to replace 1.1.1.1 with the actual IP address or domain name that you’re trying to reach. Also please perform the test both from your droplet and from external server/machine so we can compare the results.

    Regards,
    Alex

smc2-nl# traceroute update.rnova.org
traceroute to update.rnova.org (212.92.98.85), 30 hops max, 60 byte packets
1 128.199.32.253 (128.199.32.253) 0.901 ms 0.877 ms 0.860 ms
2 138.197.250.106 (138.197.250.106) 1.121 ms 138.197.250.114 (138.197.250.114) 0.969 ms 138.197.250.112 (138.197.250.112) 0.960 ms
3 138.197.250.80 (138.197.250.80) 0.735 ms 138.197.250.94 (138.197.250.94) 0.703 ms 138.197.250.74 (138.197.250.74) 5.197 ms
4 * * *
5 spb-ivc-cr2.ae11-0.rascom.as20764.net (80.64.96.0) 42.918 ms * *
6 81.27.252.147.rascom.as20764.net (81.27.252.147) 40.752 ms 40.481 ms 40.450 ms
7 188.93.17.1 (188.93.17.1) 45.346 ms 45.069 ms 45.089 ms
8 212.92.98.85 (212.92.98.85) 43.165 ms 43.150 ms 43.131 ms
smc2-nl#

And from other DO droplet (tcp 80 is ok here):

smc-nl# traceroute update.rnova.org
traceroute to update.rnova.org (212.92.98.85), 30 hops max, 60 byte packets
1 68.183.0.253 (68.183.0.253) 7.034 ms 68.183.0.254 (68.183.0.254) 1.227 ms 1.157 ms
2 138.197.250.112 (138.197.250.112) 1.954 ms 1.442 ms 138.197.250.96 (138.197.250.96) 1.046 ms
3 138.197.250.88 (138.197.250.88) 0.992 ms 138.197.250.84 (138.197.250.84) 0.942 ms 138.197.250.92 (138.197.250.92) 0.952 ms
4 * * *
5 * spb-ivc-cr2.ae11-0.rascom.as20764.net (80.64.96.0) 44.650 ms *
6 81.27.252.147.rascom.as20764.net (81.27.252.147) 41.115 ms 41.357 ms 40.510 ms
7 188.93.17.1 (188.93.17.1) 64.630 ms 64.585 ms 64.566 ms
8 212.92.98.85 (212.92.98.85) 45.637 ms 45.421 ms 45.026 ms
smc-nl#

Submit an Answer