super-admin - 28 mins ago »
If you suspect a DNS issues causing this problem, you should change your DNS server to 1.1.1.1 or 8.8.8.8 and see if this still occurs.
Surely if ping is giving a response it can't be DNS? I wonder if traceroute (or tracert as Microsoft call it) shows anything interesting when Chrome is failing.
Martin Liddle - 3 mins ago »
super-admin - 28 mins ago »
If you suspect a DNS issues causing this problem, you should change your DNS server to 1.1.1.1 or 8.8.8.8 and see if this still occurs.Surely if ping is giving a response it can't be DNS? I wonder if traceroute (or tracert as Microsoft call it) shows anything interesting when Chrome is failing.
It's working again now. I will try that next time. Thanks Martin.
super-admin - 1 hour ago »
I am curious to find out whether you still have this problem Graham.
Chrome has been through two zero-day exploit updates of late, so you should be running the latest just for this.
If you suspect a DNS issues causing this problem, you should change your DNS server to 1.1.1.1 or 8.8.8.8 and see if this still occurs.
I am still having this problem most days, using Chrome Version 89.0.4389.114 (Official Build) (x86_64) on macOS Version 11.3 Beta. I have my DNS set to 8.8.8.8, and 8.8.4.4.
When I have the problem, I am always able to access this site on the same computer using Safari browser.
Been trying all day. Failed about 5 mins ago
Hope this helps
Microsoft Windows [Version 10.0.19042.867]
(c) 2020 Microsoft Corporation. All rights reserved.
C:\Users\graha>tracert Myhumax.org
Tracing route to Myhumax.org [151.236.219.215]
over a maximum of 30 hops:
1 105 ms 1 ms 1 ms 192.168.1.1
2 16 ms 15 ms 11 ms 10.53.34.21
3 29 ms 28 ms 12 ms wolv-core-2b-xe-230-0.network.virginmedia.net [62.252.174.57]
4 * * * Request timed out.
5 * * * Request timed out.
6 43 ms 104 ms 34 ms m686-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.174]
7 53 ms 49 ms 24 ms 213.46.174.118
8 36 ms 25 ms 47 ms linode-ic332557-ldn-b2.ip.twelve99-cust.net [62.115.41.65]
9 * * * Request timed out.
10 19 ms 18 ms 16 ms li574-215.members.linode.com [151.236.219.215]
Trace complete.
C:\Users\graha>
Zero issues with Chrome on Mac iPhone and iPad. Works like a charm.
This is my traceroute:
Microsoft Windows [Version 10.0.19041.867]
(c) 2020 Microsoft Corporation. All rights reserved.
C:\Users\vilgen>tracert myhumax.org
Tracing route to myhumax.org [151.236.219.215]
over a maximum of 30 hops:
1 1 ms 2 ms 2 ms 192.168.0.1
2 * * * Request timed out.
3 14 ms 12 ms 12 ms aztw-core-2b-xe-723-0.network.virginmedia.net [62.252.231.65]
4 * * * Request timed out.
5 * * * Request timed out.
6 17 ms 18 ms 15 ms m686-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.174]
7 15 ms 15 ms 16 ms 213.46.174.118
8 19 ms 22 ms 17 ms linode-ic332557-ldn-b2.ip.twelve99-cust.net [62.115.41.65]
9 * * * Request timed out.
10 21 ms 20 ms 14 ms li574-215.members.linode.com [151.236.219.215]
Trace complete.
C:\Users\vilgen>
Only the second hop seems to be different... What is the 10.53.34.21 IP, I wonder - is it some sort of home router you have?
super-admin - 17 mins ago »
This is my traceroute:
Microsoft Windows [Version 10.0.19041.867]
(c) 2020 Microsoft Corporation. All rights reserved.
C:\Users\vilgen>tracert myhumax.org
Tracing route to myhumax.org [151.236.219.215]
over a maximum of 30 hops:
1 1 ms 2 ms 2 ms 192.168.0.1
2 * * * Request timed out.
3 14 ms 12 ms 12 ms aztw-core-2b-xe-723-0.network.virginmedia.net [62.252.231.65]
4 * * * Request timed out.
5 * * * Request timed out.
6 17 ms 18 ms 15 ms m686-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.174]
7 15 ms 15 ms 16 ms 213.46.174.118
8 19 ms 22 ms 17 ms linode-ic332557-ldn-b2.ip.twelve99-cust.net [62.115.41.65]
9 * * * Request timed out.
10 21 ms 20 ms 14 ms li574-215.members.linode.com [151.236.219.215]
Trace complete.
C:\Users\vilgen>
Only the second hop seems to be different... What is the 10.53.34.21 IP, I wonder - is it some sort of home router you have?
Nope Virgin Broadband router is in Modem mode so WiFi turned off. Wifi and wired connections provided by triband Netgear Nighthawk router.
192.168.0.1 is the netgear Nighthawk. Any other site works fine. I can run tracert for a working site if it helps.
Try now with chrome and let me know if you can reach this website.
brian - 23 hours ago »
super-admin - 1 hour ago »
I am curious to find out whether you still have this problem Graham.
Chrome has been through two zero-day exploit updates of late, so you should be running the latest just for this.
If you suspect a DNS issues causing this problem, you should change your DNS server to 1.1.1.1 or 8.8.8.8 and see if this still occurs.I am still having this problem most days, using Chrome Version 89.0.4389.114 (Official Build) (x86_64) on macOS Version 11.3 Beta. I have my DNS set to 8.8.8.8, and 8.8.4.4.
When I have the problem, I am always able to access this site on the same computer using Safari browser.
Brian, please let me know when you hit this problem.
super-admin - 1 min ago »
brian - 23 hours ago »
super-admin - 1 hour ago »
I am curious to find out whether you still have this problem Graham.
Chrome has been through two zero-day exploit updates of late, so you should be running the latest just for this.
If you suspect a DNS issues causing this problem, you should change your DNS server to 1.1.1.1 or 8.8.8.8 and see if this still occurs.I am still having this problem most days, using Chrome Version 89.0.4389.114 (Official Build) (x86_64) on macOS Version 11.3 Beta. I have my DNS set to 8.8.8.8, and 8.8.4.4.
When I have the problem, I am always able to access this site on the same computer using Safari browser.Brian, please let me know when you hit this problem.
Thanks, it has been okay so far today.
You must log in to post.
