Question

Custom SSH port blocked by DO?

Posted June 26, 2018 756 views
CentOS Networking

My VPS custom ssh port is blocked by DO SUDDENLY?
I tested my port with traceroute command in different isp network and got these:
14 las-bb1-link.telia.net (62.115.33.229) 192.213 ms 206.249 ms 235.464 ms
15 palo-b22-link.telia.net (62.115.119.90) 203.622 ms 213.156 ms 297.408 ms
16 digitalocean-ic-302451-sjo-b21.c.telia.net (62.115.34.18) 185.961 ms 187.767 ms 186.540 ms
17 * 138.197.248.215 (138.197.248.215) 193.648 ms *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
31 * * *
32 * * *
33 * *

and

10 xe-8-3-2.edge2.SanJose3.Level3.net (4.53.210.205) 200.659 ms 207.372 ms 208.047 ms
11 ae-1-6.bar2.SanFrancisco1.Level3.net (4.69.140.153) 316.209 ms 315.507 ms 315.280 ms
12 DIGITAL-OCE.bar2.SanFrancisco1.Level3.net (4.14.106.122) 248.023 ms 248.047 ms 248.101 ms
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

The packet losted in DO internal network?

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.

1 answer

Hello, @Swordow

If you can’t reach your droplet via ssh on the custom port, have you tried changing the port temporary and see if the issue is caused from using a specific/custom port?

Also keep in mind that you can always get in touch with our support team and we can check this for you.

Regards,
Alex

Submit an Answer