connect to 2606:4700:3033::ac43:db2d port 443 from :: port 50807 failed: Timed out
What steps have you taken to resolve the issue?
I tried to get help from Discord, unfortunately no solution was found but some info may be helpful there: Discord.
I have tried accessing from my PC (South East Asia) and two EC2 instances in Virginia, none can access. My client from another country in East Asia also cannot access it but he cannot even resolve the domain:
C:\Users\admin>curl -6
https://aitoolsworkspace.com/
-vvv
* Could not resolve host: aitoolsworkspace.com
* shutting down connection #0
curl: (6) Could not resolve host: aitoolsworkspace.com
As for me, I am using Cloudflare DNS (1.1.1.1) and I can resolve it but if I try pinging the IP, I cannot. Everything works fine with IPv4.
https://bgp.tools/
→ The AS number shown under “You are connecting from” like this: “Cloudflare, Inc. (AS13335)”
https://bgp.he.net/
→ The AS number shown like this: “Your ISP is AS13335 (Cloudflare, Inc.)”
I see a mix of both “Vietel” (single-t) and “Viettel” (double-t) networks, and when alone considering the “Viettel” (double-t) networks, I see these two:
AS7552 Viettel Group
AS24086 Viettel Corporation.
Both of those are able to make a traceroute to the DNS resolver at 2606:4700:4700::1111, - however, none of them are successfully tracing to 2606:4700:3033::ac43:db2d.
Traces to 2606:4700:3033::ac43:db2d end immediately, either by not giving any results at all, or by ending after the second hop (e.g. within Viettel, likely at a Viettel gateway).
As a result of that, (and assuming one of the above networks are correct for where you see the issue), I will therefore suggest you to contact Viettel for further assistance.
That said, -
One guess, which comes to my mind, is that, you’re maybe collateral damage to problems caused by Viettel, such as e.g.:
That could sound like you have some sort of WARP / Zero Trust running?
I will suggest you to turn off every kind of VPN, as well as VPN-like stuff (e.g. WARP / Zero Trust), and then try again, when they are all turned off.
From AS14618 in Ashburn, Virginia, US, the IPv6 address 2606:4700:3033::ac43:db2d is also reachable.
Can you get the AS number from your client as well?
Hi, thank you it’s indeed my mistake. My EC2 instance did NOT have IPv6 capacity. I assigned an IPv6 and now it can connect to the site. My client ISP also didn’t provide him with an IPv6, that’s why. Seem like it’s an actual block from my ISP, I will contact them. Thank you very much and sorry for the trouble.