- This topic has 53 replies, 9 voices, and was last updated 4 years, 7 months ago by
.
-
Posts
-
This issue continues to be a pain. Happens frequently several times a day. Surely someone can resolve this issue
Currently I have no access to this site on Chrome. As a Chromecast user this browser offers other capabilities not found in Firefox, Also a much easier to read display.
I still have this issue most days, so I thought I would try Chrome Beta to see if this resolves this issue.
I am now running Chrome Version 89.0.4389.40 (Official Build) beta (x86_64) on my Mac.
Not sure whether this will make any difference.
brian – 6 hours ago »
I still have this issue most days, so I thought I would try Chrome Beta to see if this resolves this issue.
I am now running Chrome Version 89.0.4389.40 (Official Build) beta (x86_64) on my Mac.
It is odd; I am running Chrome 88.0.4324.104 (Official Build) (64-bit) on Windows 10 without any problems with this site.
Martin Liddle – 12 hours ago »
brian – 6 hours ago »
I still have this issue most days, so I thought I would try Chrome Beta to see if this resolves this issue.
I am now running Chrome Version 89.0.4389.40 (Official Build) beta (x86_64) on my Mac.
It is odd; I am running Chrome 88.0.4324.104 (Official Build) (64-bit) on Windows 10 without any problems with this site.
It usually happens around midday and always as you push the button to make a post, and persists for a couple of hours or so.
I think it’s a error on one of the dns servers used. Changing to Firefox always loads the site,
Not sure if this helps. It’s not working in Chrome yet I get a response in a cmd window
C:Usersgraha>ping myhumax.org
Pinging myhumax.org [151.236.219.215] with 32 bytes of data:
Reply from 151.236.219.215: bytes=32 time=21ms TTL=56
Reply from 151.236.219.215: bytes=32 time=22ms TTL=56
Reply from 151.236.219.215: bytes=32 time=20ms TTL=56
Reply from 151.236.219.215: bytes=32 time=112ms TTL=56
Ping statistics for 151.236.219.215:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 20ms, Maximum = 112ms, Average = 43ms
C:Usersgraha>
Using whois returns MyHumax.org
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.
super-admin – 7 mins 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 have it now as I post. I have already changed the dns server to both of these without it helping.
It never happens using Microsoft Edge so apart from having to retype a post which is lost. I switch to Edge.
Chrome version
Version 89.0.4389.114 (Official Build) (64-bit)
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:Usersgraha>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:Usersgraha>
Zero issues with Chrome on Mac iPhone and iPad. Works like a charm.
- You must be logged in to reply to this topic.