Not applicable
•
6 Messages
ssh to Amazon E2 fails to connect after local xfinity "upgrade"
Since my local Xfinity service was "upgraded" (mid July 2023), I can no longer ssh-connect (using Putty) to my EC2 site at Amazon Web Services. Before "upgrade", I could use Putty, ssh to connect to ec2-18-216-187-221.us-east-2.compute.amazonaws.com
I am successful at connecting to web site at https://18.216.187.221
Ping fails "Request timed out" (see below)
tracert stops at after packet leave "as3549-pe01.ashburn.va.ibone.comcast.net (75.149.231.170)" (see below)
Testing port 22 at ec2-18-216-187-221.us-east-2.compute.amazonaws.com also fails
Pinging ec2-18-216-187-221.us-east-2.compute.amazonaws.com [18.216.187.221] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
tracert 18.216.187.221
1 100.93.197.66 (100.93.197.66) 13.577 ms 18.288 ms 13.124 ms
2 po-310-357-rur901.ross.pa.pitt.comcast.net (69.139.167.69) 13.957 ms 26.641 ms 16.321 ms
3 96.110.49.62 (96.110.49.62) 15.436 ms 18.021 ms 12.359 ms
4 po-200-xar02.ross.pa.pitt.comcast.net (96.110.49.201) 13.345 ms 20.631 ms 12.256 ms
5 96.110.2.229 (96.110.2.229) 15.850 ms 19.057 ms 16.491 ms
6 be-31641-cs04.pittsburgh.pa.ibone.comcast.net (96.110.42.173) 20.103 ms 16.645 ms 15.792 ms
7 be-1411-cr11.pittsburgh.pa.ibone.comcast.net (96.110.38.142) 16.037 ms 14.714 ms 16.308 ms
8 be-303-cr12.beaumeade.va.ibone.comcast.net (96.110.39.145) 21.626 ms 18.655 ms 22.845 ms
9 be-1212-cs02.beaumeade.va.ibone.comcast.net (68.86.84.149) 22.907 ms 31.364 ms 23.532 ms
10 be-3213-pe13.ashburn.va.ibone.comcast.net (68.86.166.214) 23.973 ms 30.430 ms 23.867 ms
11 as3549-pe01.ashburn.va.ibone.comcast.net (75.149.231.170) 23.487 ms 22.598 ms 30.298 ms
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
flatlander3
Problem Solver
•
1.5K Messages
2 years ago
Your ssh server is crashed or your firewalled/blocked locked everyone out. From a non-Xfinity network:
PORT STATE SERVICE
22/tcp filtered ssh
PORT STATE SERVICE
80/tcp open http
Can ya kick your virtual machine in the head to reboot it? Or have them reboot your instance? If you got it locked down by single IP access and it changed, well....port 22 is asking for abuse, and perhaps something more like fail2ban, and known hostile lists sort of like what snort does, or other block lists with your normal firewall throttling is more of what you are looking for on public facing services.
(edited)
0
0
XfinityMarcus
Official Employee
•
1.7K Messages
2 years ago
@flatlander3, thank you for assistance with this issue. @Anon269285, is this issue still currently ongoing for you?
0
0