- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
This tracert log is from your network, right? Please check from your client side. Also check log on ec2 if it get any request from client's network.
I’d check the remote client end for any firewall rules et , ACLs and routes which may prevent the access to your server IP
Also check your Acls, security group and routes which may prevent access.
thank you for your suggestion. I have checked the security group attached to that EC2. it opens to all inbound traffic from any source, i think it should be fine. but our client from indonesia tried to traceroute to our IP and they got a timeout from this IP address > 63.217.25.150 and the request not going through.
Some internet routers disable ICMP; hence traceroute will timeout. Can your client ping your EC2 instance in Jakarta region?
%% ping 108.137.121.132
PING 108.137.121.132 (108.137.121.132): 56 data bytes
64 bytes from 108.137.121.132: icmp_seq=0 ttl=51 time=23.798 ms
64 bytes from 108.137.121.132: icmp_seq=1 ttl=51 time=22.084 ms
Also ask your client to access it via http (http://108.137.121.132/) and https (https://108.137.121.132/)
If client is unable to access it via ping, http and https from their office network (but is able to using mobile internet from their personal devices), it probably means that access is blocked, perhaps by on-premise firewall at client's site.
Contenuto pertinente
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata un anno fa
The traceroute result is from our client's server. And i have monitoring on all incoming traffic there's no request coming from our client's server IP or hostname either. The traceroute got a timeout at this IP address > 63.217.25.150 and not going through.
Since you open all inbound and from any source but not see request from your client then I think some rule blocked your client . https://ipinfo.io/63.217.25.150 show this is router belong to PCCW Global, Inc. in Singapore