Clubjazz - Honda Jazz & HR-V Forums
Welcome => Site Help & Feedback => Topic started by: VicW on August 30, 2017, 07:38:08 PM
-
I am regularly getting an error message that says ' Site cannot be reached' when trying to connect to Club Jazz.
Is anyone else getting this?
Vic.
-
Not had problems here or by using Google Search.
-
Constantly. You click a thread and it comes up with the error. Go back and try again and it works. I did a screen dump, intending to post the question a couple of days ago, the lost the dump!
I use Windows 10 with Google Chrome as my browser.
-
yeah, get it fairly regularly - just keep trying
-
Yes - I've had this - not often but I do get it. No rhyme nor reason from what I can see.
-
Hi
It most likely a resource issue on the hosting platform
Common reasons are
If shared platform - too many connections
If vps, too much resources used or too many connections
The end result is error 404, page cannot be displayed
I would be surprised if it was dns, but if you think it is, just try pinging website and you should see if it resolves
Another thing to try is website downforall (you'll need to google it for correct URL)
Hope that helps
Many thanks
John
-
The end result is error 404, page cannot be displayed
Thanks for that John, it's a bit beyond me but thanks anyway.
The error message actually says: 'Site cannot be reached' and gives a couple of suggestions as to what to do.
It's annoying rather than a real problem and it effects other people too apparently but Club Jazz is the only site I get the message on.
I use Google Chrome and Windows 10. I'll have to try it on Edge.
Regards, Vic.
-
I use Google Chrome and Windows 10. I'll have to try it on Edge.
The problem is you will have to use Edge all the time. If you get the problem on Chrome, then change to Edge you may think that has solved it. But closing then reopening Chrome can have the same effect.
-
Hi
Many thanks
Sorry I may not have explained too well sorry
Firstly, the issue is not with any particular browser (refreshing a browser could cause the browser to use cache over live if visited usually on the same day)
I suspect it is a too many connections issue (a 404 error maybe scripted to show a customised page)
To explain in more terms that most may understand better I hope
Imagine the browser call to forum/jazzorg is a request to your phone for you get into your car and drive 200 miles, but your on the phone already, so the caller gets a destination unreachable because your on the phone. When you end the call, it then rings
In very simple terms, this is how a hosting platform works, but with say 30,000 phone lines, and each line is autoanswered many times a second. Once all the lines are in use, it gives destination unreachable
We are an ESP and have many shared hosting servers, which are clustered, so each server could handle say 50,000 calls on each, and if you have say 5 servers clustered together, it gives you 250,000 calls total
I hope that makes more sense but please understand, I do know what this site uses, and it is purely a guess as to why it happens (albeit an educated guess without any knowledge of the platform etc)
Many thanks
John
-
Just an 'engaged' signal from the website then, I must admit that when I occasionally get the error if I try again straight away I get the site up, so it is a fleeting thing.
I remember when the clubjazz site had its bandwidth problem a while ago one of the first signs was the site cannot be reached error.
-
Hi culzean
Yes, I think you've got the idea
It may appear fleeting, but this is due to speed of the server handling requests.
So in one thousand of a second (say 146ms), there maybe say 1000 requests, and the very next thousand of a second, after server let's say had handled 850 of those 1000 request previously made, there maybe 600 new request, so within the 2 thousand of a second, 1600 requests made, with 150 requests still outstanding to be performed
This is ongoing but hopefully gives a little insight
I guess it's very like the computer controlling your ABS
Many thanks
John
-
I'll look into this to see what the problem is. It is not browser related though.
We moved severs recently to allow a SSL connection and to increase bandwidth.
-
Well as our IT department has closed off lots of ports on the server I was blaming them what I had the 404 error. but not seen it for the last week or so.
-
I've been getting a lot of this this morning.
(http://i.imgur.com/RPT4eT7.jpg)
-
Hi jocko
Many thanks, that helps a little from my perspective
I think I maybe wrong sorry in my educated guess earlier and it could be a simple case of misconfigured dns (NS to be precise)
A quick check reveals the nameservers are inconsistent to each other, giving different set of NS records
Even if I am wrong again (very possible sorry), the nameservers should be fully resolved
I am not posting any details on here sorry, but if Richard wants to pm me, I'll send him the details, or a live check can be performed
Jocko, there is a simple test which may prove if I'm right in above, by adding an into your computer host file.
I can give the details and how to do this if you want, as you seem to be having this issue.
After a few days (or when past the time frame you would normally see the issue), if you still have not an issue, you can delete the entry
I'm sorry if I should not be posting, and no details have been given but just trying to help a little
Many thanks
John
-
Sounds complicated. Let me know what I have to do and I'll give it a try.
One other thing I didn't add. I use mobile broadband so I present various IP addresses to sites I try to reach.
-
Hi jocko
Many thanks
It sounds complicated but reality is it's very easy
Please could I ask what your computer operating system is (windows 7, 8 or 10), Linux etc
I'll lookup the detail needed and post how to change (simple change by adding a line to host file - copy and paste)
It is very important that this line be deleted after issue is resolved and not left in place, or in future any changes to hosting would mean you may not be able to access this website
I hope that's alright and I would test it myself, if I had the same issue you have here, but sorry, it is only maybe once a fortnight
Many thanks
John
-
Hi
Just incase anyone wants to try my simple test, please find details below
(Please note to remember to delete the entries when the issue is fully resolved)
Locate your host file (note this is named host with no extention)
in windows, it is normally found in the following directory, but you could use search function for host file
C:\Windows\System32\drivers\etc
In linux or Mac it is in different directories, which is flavour dependant
Edit the host file (in windows say using notepad - please note, when using notepad, it normally places .txt at the end. Once you save the file, rename the file to host and not host.txt - you will maybe presented with a warning, so please accept it)
On some windows/systems, it may not allow a host file to be saved in the directory listed above, so save to my documents, then goto C:\Windows\System32\drivers\etc, rename host to host1, and copy and paste the host file from my documents to C:\Windows\System32\drivers\etc
The change that need to be added are as follows:
91.222.9.75 clubjazz.org
so the host file would look similar to this
# Copyright (c) 1993-2009 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host
# localhost name resolution is handled within DNS itself.
# 127.0.0.1 localhost
# ::1 localhost
91.222.9.75 clubjazz.org
All you need to do now is save the file as described above, but please make sure when saving the file, it does not add an extention (usually .txt), if so, please rename to host
Once you have completed these steps, when you open a browser, it will no longer go to an external DNS, so the nameserver issue would no longer be an issue to you. You must though, delete the entry once it has been fully resolved or you still see the same issue.
Lastly, if you have any web browsers already open, please close them all down, then reopen a web browser and goto clubjazz.org (you may notice a very small speed increase or not)
Many thanks but I apologise if I am wrong
John
-
Maybe this is a Chrome issue after all? All the Google results for this problem appear to suggest it being Chrome-specific, unless Chrome is more picky over whatever is triggering it off.
Anyone here experiencing this problem who do not use Chrome?
40x (etc..) errors are easily identifiable, we have our own custom error pages with the Clubjazz logo and a link to the homepage and forum.
We use a shared hosting service which for the uninitiated means several websites use the same server.
-
Hi RichardA
I see it sometimes using tapatalk
You may have more detail then what's shown in the browser but I would advice you have your nameservers corrected.
If a user using chrome would like to run my test (which would mean the nameserver issue would not exist for them), then that would identify quickly if the issue was the NS or not. However, this would only work if it was known how frequently it happened, and the test would then run 1 week past the expected date or end if same issue happened earlier. If you see what I mean
I do have say though, as your shared, you would not have access to the host graph for max overall connections (max is 254, but handle a lot more with workers then 254)
If you would like to pm me an extract of the failure, I maybe able to help more with more detail but I appreciate you most likely do not want to do that, sorry
I hope that helps
Many thanks
John
-
Maybe this is a Chrome issue after all? All the Google results for this problem appear to suggest it being Chrome-specific, unless Chrome is more picky over whatever is triggering it off.
Anyone here experiencing this problem who do not use Chrome?
40x (etc..) errors are easily identifiable, we have our own custom error pages with the Clubjazz logo and a link to the homepage and forum.
We use a shared hosting service which for the uninitiated means several websites use the same server.
I use Waterfox (don't like Googles intrusive policies ), recently updated to latest release - still get it very infrequently, about the same as before update - will try to get screen dump if it happens again.
When it has happened (except for when clubJazz site had the bandwidth problem many weeks ago) I normally get connected on the next (pretty much immediate) try anyway - and it is so infrequent that I certainly would not go to the extent of messing with windows files (IMHO Windows does not need an excuse to play up so I'm not going to poke a stick into a wasp nest LOL)
-
Hi
I understand Culzean, if you were aiming the changes I suggested to host file, but honestly, I would never post to a non technical forum on changes which may cause issues. The changes I proposed would just simply tell your computer where to find clubjazz.org, so it did not have to ask outside of computer, if you see what I mean.
Honestly, changing the lights to me was probably similar to asking for host file changes to you.
However, RichardA could be correct, and I most likely am totally wrong sorry. The reason why I keep posting, is because if the issue is affecting chrome, the browser refresh should still not resolve the issue, and it does affect other browsers.
I hope RichardA does not mind, as the details are public anyway (they have to be for the website to work), and anyone could run checks, but there is very definately an issue on the nameservers (see below).
I understand most would perhaps not know what they were looking at, but in simple terms, when your browser makes a request, it looks to NS/DNS for where to go. Now if you happen to hit the wrong NS/DNS, as the below shows, it has no records, therefore cannot go anywhere and page not found (could be called many things) is presented. However, some browsers would bring up their search page with the failed domain website.
To put it very simply, clubjazz.org Nameservers are shown as
INFO
Name Server (NS) records at the TLD name server a0.org.afilias-nst.info:
ns1.vidahost.com
ns2.vidahost.com
a manual check of the DNS for clubjazz.org using these 2 nameservers shows as failed
> clubjazz.org ns1.vidahost.com
Server: ns1.vidahost.com
Addresses: 2a01:9cc0:0:9::2
91.198.165.131
*** ns1.vidahost.com can't find clubjazz.org: No response from server
> clubjazz.org ns2.vidahost.com
Server: ns2.vidahost.com
Addresses: 2a01:9cc0:0:8::2
91.146.110.188
*** ns2.vidahost.com can't find clubjazz.org: No response from server
> clubjazz.org ns1.footholds.net
Server: ns1.footholds.net
Address: 95.142.155.14
The nameservers with DNS are
Name Servers Found at ns1.vidahost.com for clubjazz.org NOT found at a0.org.afilias-nst.info:
ns2.footholds.net
ns1.footholds.net
a manual check of the DNS for clubjazz.org using these 2 nameservers shows as good
> clubjazz.org ns1.footholds.net
Server: ns1.footholds.net
Address: 95.142.155.14
clubjazz.org internet address = 91.222.9.75
clubjazz.org MX preference = 0, mail exchanger = clubjazz.org
clubjazz.org
primary name server = ns1.footholds.net
responsible mail addr = serveremails.raim.co.uk
serial = 2017052204
refresh = 3600 (1 hour)
retry = 7200 (2 hours)
expire = 1209600 (14 days)
default TTL = 86400 (1 day)
clubjazz.org text =
"v=spf1 +a +mx +ip4:195.62.28.18 ?all"
clubjazz.org nameserver = ns2.footholds.net
clubjazz.org nameserver = ns1.footholds.net
ns1.footholds.net internet address = 95.142.155.14
ns2.footholds.net internet address = 91.198.165.131
> clubjazz.org ns2.footholds.net
Server: ns2.footholds.net
Address: 91.198.165.131
clubjazz.org internet address = 91.222.9.75
clubjazz.org nameserver = ns1.footholds.net
clubjazz.org nameserver = ns2.footholds.net
clubjazz.org MX preference = 0, mail exchanger = clubjazz.org
clubjazz.org text =
"v=spf1 +a +mx +ip4:195.62.28.18 ?all"
clubjazz.org
primary name server = ns1.footholds.net
responsible mail addr = serveremails.raim.co.uk
serial = 2017052204
refresh = 3600 (1 hour)
retry = 7200 (2 hours)
expire = 1209600 (14 days)
default TTL = 86400 (1 day)
ns1.footholds.net internet address = 95.142.155.14
ns2.footholds.net internet address = 91.198.165.131
This is why I posted that the nameservers should be corrected.
RichardA, if you do not fully understand, but wish them to be corrected, you need to open a support ticket with your hosting company, and you could copy and paste this post, simply asking for them to correct the nameservers, which their support should understand when they see my post, test themselves and correct. Once corrected, a new test needs to be carried out after 24 hours to confirm nameservers corrected.
I hope that helps a little, and I think this may stop the browser issue been seen/reported.
Many thanks
John
Name Servers
INFO
Name Server (NS) records at the TLD name server a0.org.afilias-nst.info:
ns1.vidahost.com
ns2.vidahost.com
INFO
The TLD name server a0.org.afilias-nst.info did not send A records (GLUE) for the name servers in the additional section!
INFO
ns1.vidahost.com has the following A Records:
91.198.165.131 (TTL: 14400 seconds), located at United Kingdom
INFO
ns2.vidahost.com has the following A Records:
91.146.110.188 (TTL: 14400 seconds), located at
PASS
All of your name servers have A records.
PASS
All of your name servers are on seperate IP addresses.
PASS
Your name servers are geo distributed. This is the right thing to do to ensure the best availability
PASS
Your name server ns1.vidahost.com is responding to DNS queries.
WARNING
Name Servers Found at a0.org.afilias-nst.info for clubjazz.org NOT found at ns1.vidahost.com:
ns1.vidahost.com
ns2.vidahost.com
WARNING
Name Servers Found at ns1.vidahost.com for clubjazz.org NOT found at a0.org.afilias-nst.info:
ns2.footholds.net
ns1.footholds.net
WARNING
Your name server ns1.vidahost.com is responding with a different set of NS records as compared to the TLD server a0.org.afilias-nst.info!
PASS
Name server ns1.vidahost.com sent A records (GLUE) along with the response for the NS records query for clubjazz.org.
PASS
Your name server ns2.vidahost.com is responding to DNS queries.
WARNING
Name Servers Found at a0.org.afilias-nst.info for clubjazz.org NOT found at ns2.vidahost.com:
ns1.vidahost.com
ns2.vidahost.com
WARNING
Name Servers Found at ns2.vidahost.com for clubjazz.org NOT found at a0.org.afilias-nst.info:
ns1.footholds.net
ns2.footholds.net
WARNING
Your name server ns2.vidahost.com is responding with a different set of NS records as compared to the TLD server a0.org.afilias-nst.info!
PASS
Name server ns2.vidahost.com sent A records (GLUE) along with the response for the NS records query for clubjazz.org.
WARNING
The NS records returned by your name servers are not consistent with either the TLD server a0.org.afilias-nst.info or some of your other name servers. See above. The reason for this could be that you have different name servers at your domain name registrar as compared to your NS records. Even if this could be ok, you should always have the same name servers at your registrar and at your NS records.
PASS
Your name server ns1.vidahost.com is authoritative for the domain name clubjazz.org.
PASS
Your name server ns2.vidahost.com is authoritative for the domain name clubjazz.org.
PASS
The SOA serial is the same at all your name servers.
PASS
None of your name servers seem to allow recursive queries.
Default Server: google-public-dns-a.google.com
Address: 8.8.8.8
> set type=any
> clubjazz.org
Server: google-public-dns-a.google.com
Address: 8.8.8.8
Non-authoritative answer:
clubjazz.org internet address = 91.222.9.75
clubjazz.org nameserver = ns1.footholds.net
clubjazz.org nameserver = ns2.footholds.net
clubjazz.org
primary name server = ns1.footholds.net
responsible mail addr = serveremails.raim.co.uk
serial = 2017052204
refresh = 3600 (1 hour)
retry = 7200 (2 hours)
expire = 1209600 (14 days)
default TTL = 86400 (1 day)
clubjazz.org MX preference = 0, mail exchanger = clubjazz.org
clubjazz.org text =
"v=spf1 +a +mx +ip4:195.62.28.18 ?all"
> clubjazz.org ns1.vidahost.com
Server: ns1.vidahost.com
Addresses: 2a01:9cc0:0:9::2
91.198.165.131
*** ns1.vidahost.com can't find clubjazz.org: No response from server
> clubjazz.org ns2.vidahost.com
Server: ns2.vidahost.com
Addresses: 2a01:9cc0:0:8::2
91.146.110.188
*** ns2.vidahost.com can't find clubjazz.org: No response from server
> clubjazz.org ns1.footholds.net
Server: ns1.footholds.net
Address: 95.142.155.14
clubjazz.org internet address = 91.222.9.75
clubjazz.org MX preference = 0, mail exchanger = clubjazz.org
clubjazz.org
primary name server = ns1.footholds.net
responsible mail addr = serveremails.raim.co.uk
serial = 2017052204
refresh = 3600 (1 hour)
retry = 7200 (2 hours)
expire = 1209600 (14 days)
default TTL = 86400 (1 day)
clubjazz.org text =
"v=spf1 +a +mx +ip4:195.62.28.18 ?all"
clubjazz.org nameserver = ns2.footholds.net
clubjazz.org nameserver = ns1.footholds.net
ns1.footholds.net internet address = 95.142.155.14
ns2.footholds.net internet address = 91.198.165.131
> clubjazz.org ns2.footholds.net
Server: ns2.footholds.net
Address: 91.198.165.131
clubjazz.org internet address = 91.222.9.75
clubjazz.org nameserver = ns1.footholds.net
clubjazz.org nameserver = ns2.footholds.net
clubjazz.org MX preference = 0, mail exchanger = clubjazz.org
clubjazz.org text =
"v=spf1 +a +mx +ip4:195.62.28.18 ?all"
clubjazz.org
primary name server = ns1.footholds.net
responsible mail addr = serveremails.raim.co.uk
serial = 2017052204
refresh = 3600 (1 hour)
retry = 7200 (2 hours)
expire = 1209600 (14 days)
default TTL = 86400 (1 day)
ns1.footholds.net internet address = 95.142.155.14
ns2.footholds.net internet address = 91.198.165.131
> clubjazz.org a0.org.afilias-nst.info
Server: a0.org.afilias-nst.info
Addresses: 2001:500:e::1
199.19.56.1
*** a0.org.afilias-nst.info can't find clubjazz.org: No response from server
-
For what it's worth I get this problem from time to time.
I use Win 10 64bit , IE 11, Edge, and IPv4 Google Name servers!
-
@d2d4j
Thanks, I've put in a support ticket with the host.
I've had an issue using Firefox on Mac a few weeks back but it went away as quickly as it appeared.
I've experienced problems with Tapatalk but it's error messages within the app are very generic and don't give any real information.
-
{TL;dr} ns1.vidahost.com ~bad, ns1.footholds.net ~good
Just to back up what d2d4j says, the temporary outage some experience does look like a temporary DNS failure. Performing a couple of lookups gives conflicting answers of ns1 & ns2.vidahost.com and ns1 & ns2.footholds.net for nameservers, plus reveals a temporary name resolution failure using vidahost.com nameservers that seems to work second time round, but always works first time successfully using ns1 & ns2.footholds.net
Although ns1.vidahost.com = 91.198.165.131 = ns2.footholds.net and ns3.vidahost.com = 95.142.155.14 = ns1.footholds.net it is likely they are balanced and directed over several virtual machines behind these single IP . Resolution via ns1 ns2 ns3 & ns4.vidahost.com nameservers always fails if it has not been asked to resolve clubjazz.org recently, a quick second request works OK but then it seems to forget about clubjazz.org again after another 60 seconds although setting the timeout for name resolution to 6 seconds seems to mostly allow enough time for a valid response. Responses from the footholds.net nameservers seem instant.
I'd suggest the WHOIS record is amended to agree with the nameservers records as ns1 & ns2.footholds.net unless Paragon suggest it should be the other way around.
--
TG
> whois clubjazz.org
Connecting to ORG.whois-servers.net...
Domain ID: D149704362-LROR
Registrar WHOIS Server: whois.paragonnames.net
Name Server: NS1.VIDAHOST.COM
Name Server: NS2.VIDAHOST.COM
> nslookup
> clubjazz.org ns1.vidahost.com
Server: ns1.vidahost.com
Addresses: 2a01:9cc0:0:9::2
91.198.165.131
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to ns1.vidahost.com timed-out
> clubjazz.org ns1.vidahost.com
Server: ns1.vidahost.com
Addresses: 2a01:9cc0:0:9::2
91.198.165.131
clubjazz.org internet address = 91.222.9.75
clubjazz.org nameserver = ns1.footholds.net
clubjazz.org nameserver = ns2.footholds.net
[attachment deleted by admin]
-
Hi
Many thanks RichardA and TG
Ideally, the NS need to be vidahost NS I would have thought, given vidahost are the host
To be honest though, it really does not matter which is used, as long as the TLD and NS match. Both respond equally well from a lookup time and both run powerdns (which will be clustered I think)
If you want to post when NS have been corrected and we can test to confirm
Many thanks
John
-
Thanks for the replies.
Since I posted the original question the error message hasn't appeared again so something has come of the chat.
Vic.
-
Hi vicw
I'm sorry, the changes have not yet been made, or if they have, propagated.
I think most do not realise, your computer retains dns cache, your router retains dns cache, your isp retains cache etc.... even google retains dns cache and whilst TTL may show short, it can be ignored or overriden by some, so it's likely your still using stale dns
The time to confirm if this was the issue would be to allow a full month to go by, once the NS have been corrected, and if you do not see the issue in that time, it is safe to assume it was NS been wrong
I hope that helps a little
Many thanks
John
-
My host have checked the error logs around the time the OP reported the problem and found nothing.
-
Hi RichardA
Many thanks
It is better to have the NS corrected even if this is not the issue
The logs for dns from the 30 August would be old, we certainly do not hold logs from dns/NS due to volume in use, and most platforms are cron for deletion once a certain log file size has been reached in a log folder or time stamp
I am not saying though, vidahost have not checked logs and do not keep logs from 4/5 days ago, so you can only go by what the host states
As I say though, it is better to have NS fully corrected so it can be 100% excluded, as given the descriptions of user issues, cannot find then can, and NS wrong, would indicate NS been the issue
Bet your glad I do this for my job and advice on hosting technical forum (infact I'm a super moderator) but mechanically, I know nothing sorry, so most lose me on mechanical things, like fitting lights or car wiring
Many thanks
John
-
Hi RichardA
Sorry, thinking through the night, I may have misunderstood your last post
If you mean they checked the hosting logs for clubjazz, (which you should be able to see as well from your control panel), then they are correct, no error found.
The reason for no errors is because no errors would be present within the hosting logs, due to the issue most likely been DNS/NS related.
That is why I thought you meant they checked the DNS logs, which thinking again last night, does not make sense not finding an error, as TG and myself both ran manual lookups which failed, so at the very least, these failed lookup should be present in the logs for NS/DNS. That said though, as I stated earlier, these logs become very full very quickly, so they have a tendency to be short lived before been deleted/overwritten
Did you open the support ticket to specifically have the nameservers corrected.
Many thanks and sorry if I am causing confusion
John
-
I opened a support ticket and attached jocko's screen shot and a link to your post ref. DNS config.
They responded by requesting a time & date so they can check the logs, and I gave them the time & date of Vic's original post and his IP address. I know I can check the logs myself and that they may have been overwriten since then, but i assumed they could somthing at their end or suspected something different.
Sent from my GT-S7500 using Tapatalk 2
-
Hi RichardA
Many thanks
I would update or create a new support ticket just for the nameservers to be corrected
A simple test proves they are wrong and could cause the issue been seen/posted
The support people should have realised it's a nameserver issue, or nameservers are wrong, but you cannot guarantee they picked this up. If they had, the nameservers should be showing clear of issues, which they are not sorry. It takes a few seconds to correct then a period of usually 8 hours to fully propagate
I hope that helps
Many thanks
John
-
Oh sorry, you need to include clubjazz.co.uk as well as clubjazz.org for nameservers corrections
Many thanks
John
-
Hi RichardA
Congratulations clubjazz.org now resolves and passes all test for NS/DNS
Please could you also open a ticket to have clubjazz.co.uk for the same nameserver correction.
It would be interesting to see if anyone has same issue as reported earlier to start this thread.
If you do, please could you take a screenshot and post
Many thanks
John
-
I am being plagued by the error message this morning. Windows 10, Google Chrome.
(https://i.imgur.com/2ThMPWm.jpg)
-
Hi jacko
Please could I ask you exactly what URL you used
Was it http://clubjazz.org or https://clubjazz.org
All nameservers are showing correct now so it should not be this causing the issue
Many thanks
John
-
Hi
Sorry, also could you open a command prompt (search command and double click the command.exe)
Then type ping clubjazz.org
It will ping it 4 times and could you post the result
Many thanks
John
-
Hi jacko
Sorry, just tried in chrome from here and no issue, but noticed on computer (picture is bigger then little mobile phone)
Could you click details next time it happens, and post, which may reveal more details over the issue
Many thanks
John
-
Got the error again and ran the Ping test but as soon as the command prompt ran the three tests it just closed the window. Then the Forum returned. Assume the Ping test acted like a refresh.
-
I was barred from entry as well for a few milliseconds, just tried again and no problem
PDF screen grab attached
Using Waterfox
[attachment deleted by admin]
-
Hi
Sorry I'm posting here so as not to disturb RichardA thread
@jacko - the ping test is separate to browser and would not normally autoclose. The actual line I was interested in was the very first line, which shows dns resolution. The test that follows, may fail due to numerous reasons. But thank you for trying ping test.
The nameservers are fully correct and all dns should now be fully propagated- so this can be excluded fully
Tapatalk had a blank screen around 8.30 this morning, but refreshed and it appeared
I myself, given that 3 users, using different access methods (browser and tapatalk) had issue around 8.30am today, would indicate an issue on the server or website, but hopefully something would be logged as it is not dns, so a call to website should have gone through and be logged
I hope that helps a little, and please, I am posting here to keep RichardA thread clean and just explain my thoughts
Many thanks
John
-
Hi John. It certainly auto closes on my set up. I use the command prompt now and again, so I am not unfamiliar with it. Can I add a suffix to the command to stop it closing?
-
Hi jacko
Many thanks
I've not really heard of that before then sorry.
The ping command should not autoclose command prompt
Did you open command prompt first, then type ping command or try to run ping as command itself if you see what I mean. I always open command prompt first then type commands as needed.
As I said though, running the ping was only for the first line, to ensure it resolved clubjazz.org correctly to its IP address
I guess pathping might have been a better choice if needing to see where packet loss etc maybe happening. This is not happening here though, so ping is fine
Many thanks
John
-
Hi John. It certainly auto closes on my set up. I use the command prompt now and again, so I am not unfamiliar with it. Can I add a suffix to the command to stop it closing?
ping clubjazz.org -t keeps going until you kill it i.e. Ctrl-C
--
TG
-
Works a treat. I'll do that next time and take a screen dump.
-
Hi
Sorry, also could you open a command prompt (search command and double click the command.exe)
Then type ping clubjazz.org
It will ping it 4 times and could you post the result
Many thanks
John
For the benefit of Mac users - go to Utilities->Terminal and follow the above.
Hi jacko
Please could I ask you exactly what URL you used
Was it http://clubjazz.org or https://clubjazz.org
All nameservers are showing correct now so it should not be this causing the issue
Many thanks
John
To clarify, is this problem occurring with http or https?
EDIT: Answered my own question, I've just had the problem in Firefox on Mac using https.
I can connect to the FTP server using FileZilla, no error in the root error log.
-
Hi RichardA
Many thanks
This has just happened a minute ago on tapatalk
It happens on both http and https
Do you have any cron jobs running (I don't think it's a cron job but it seems to happen around same timeish)
Many thanks
John
-
Not that I'm aware of but I'll check
(I've just had the problem and edited my previous post accordingly).
-
No cron jobs in operation, scheduled tasks are set to SMF's default of the early hours of the morning.
-
Hi RichardA
A little trick we use sometimes, when it's hard to clarify the exact issue is
Create a simple HTML test page and when it happens next, try to bring up the test page. If displays, it could indicate an issue in smf or php perhaps
The test should be doable because tapatalk outage lasted approx 20 - 40 seconds I think
Many thanks
John
-
Hi RichardA
Sorry a quick thought if you do not mind
You know your external IP address and time of issue
You should be able to look at hosting log and find at least 1 entry corresponding to the website reference, unless the first time stamp of this was when it started to service site correctly
If you cannot find any reference on the timestamp of the outage, I would open a support ticket and give them details of your IP address, exact time of outage and ask why your hosting logs do not show any entries for that particular time interval
Please clearly state when the site started working correctly as a timestamp
This would indicate that your website had not received the request and therefore the issue is out of your control and in the hands of the hosting company
If though, you see reference from your IP address at the outage timestamp, the issue is yours to resolve, and I would look at the smf logs first then, based on timestamp
I hope that helps a little and sorry if you already knew that. I can be a little slow sometimes sorry
Many thanks
John
-
One issue with shared hosting is sometimes you don't have the resources you need to generate a complex page instantly. This forum might be susceptible to this as many regular users click / land on 'Latest' to request https://clubjazz.org/forum/index.php?action=unread (https://clubjazz.org/forum/index.php?action=unread) This is probably the most resource intensive page that SMF has to generate, and can't really be cached whereas https://clubjazz.org/forum/index.php?action=recent (https://clubjazz.org/forum/index.php?action=recent) is probably less intensive and cacheable.
There are a few optimisations that might not be performed yet, such as enabling APC / APCu, disabling the calendar, and changing the avatar upload folder. https://www.fastcomet.com/tutorials/smf/optimize-smf
--
TG
-
Hi TG
Good point, well stated
The only things are, if it were a resource issue, the error message would be different I would expect e.g. Timed out
It is an extremely hard to fully pinpoint or help without more detail, so general advice is given to try to help
Firstly, it needs clarifying if when the issue is seen, are there any website references shown in the hosting logs available (or in hosting error logs - we make both available to clients), on the time stamp of the outage i.e. If error seen at 8.30, do any logs show any requests until say website back up at 8.33. If you see what I mean
If the answer is no requests made during the outage period, this needs a support ticket opening as it is most unlikely due to anything wrong with website
If requests are seen, it is very likely to do with website
It could even be a keep alive issue, but I do not think so
As I said, it's a hard one to work out without details/info but certainly the correction of the nameservers helped, if only by excluding them as the cause.
Many thanks
John
-
Just had the error message again.
(https://i.imgur.com/RPT4eT7.jpg)
Windows 10. Google Chrome. 11-9-2017 20:49.
-
And again this morning. 12-9-2017 10:34.
-
Hi jacko
Many thanks
I hope you don't mind but Richard asked in his earlier post (the new thread he started purely for issues with website), if anyone experiencing issue should post them to his new thread
I am not connected to nor have access to anything with regard to Richard hosting
I am not even sure if Richard will see your post in a timely fashion to be able too look if posting on this thread here
I hope that's alright and sorry if I'm wrong
Many thanks
John
-
Just had the error message again.
(https://i.imgur.com/RPT4eT7.jpg)
Windows 10. Google Chrome. 11-9-2017 20:49.
Modify message
-
And again this morning. 12-9-2017 10:34.
-
I thought I was posting to the second thread. I have forwarded them on.
Thanks, Jocko.
-
Just to clarify, please post anything regarding this problem to this thread. For any other issues please start a new thread in this forum.
The other thread was a reminder to post site help requests in the site help forum, the reason being that I get an email when ever a new thread is started in that forum. This thread was posted elsewhere initially so it got missed for a few days.
I have notifications turned on for this thread so I'll get an email every time a reply is posted.
One issue with shared hosting is sometimes you don't have the resources you need to generate a complex page instantly. This forum might be susceptible to this as many regular users click / land on 'Latest' to request https://clubjazz.org/forum/index.php?action=unread (https://clubjazz.org/forum/index.php?action=unread) This is probably the most resource intensive page that SMF has to generate, and can't really be cached whereas https://clubjazz.org/forum/index.php?action=recent (https://clubjazz.org/forum/index.php?action=recent) is probably less intensive and cacheable.
There are a few optimisations that might not be performed yet, such as enabling APC / APCu, disabling the calendar, and changing the avatar upload folder. https://www.fastcomet.com/tutorials/smf/optimize-smf
--
TG
Some of those SMF optimizations I carried out some years back, I'll go through that page again though in case something new has been added.
By the way, 'Latest' serves up https://clubjazz.org/forum/index.php?action=unread (https://clubjazz.org/forum/index.php?action=unread) if logged in, and https://clubjazz.org/forum/index.php?action=recent (https://clubjazz.org/forum/index.php?action=recent) when not.
-
Host claim it was down to an Apache issue, now fixed.
Sent from my GT-S7500 using Tapatalk 2
-
Hi Richard
Kudos to you and hopefully all fixed
Many thanks
John
-
Dammed Apaches get everywhere. Call in the cavalry.
-
As the original poster I have attempted to follow the flow of the responses but most of it is way over my head. Thanks for all the replies, I hope some of you have got something out of it.
I haven't had the error message for two or three days now.
Vic.
-
Error returned for me at 09:59 today. Problem just seems to be the length of time https//clubjazz.org takes to connect. It eventually connected of its own volition.
-
Hi jacko
Firstly, apologies for my misreading of Richard post over website issue. I did not realise he was keeping this separate from other website issues which may arise, sorry
I think your issue is a different issue to what this thread is about sorry
However, as it's connected to this thread, then it's good you posted here, as it is relevant
The reason why I think it is a different issue, is because it did display the website (ergo not same issue where it would not)
I think this new issue could be one or more of a few things
Your broadband connection
Your computer/browser
Shared hosting platform under strain
Another user on shared hosting using too much drive access
An exception within php code
Waiting time for external parts of website to become https
Pipe congestion
Extra loading on shared platform due to https
There's more, and in fairness, every server does suffer to a degree in these things, but because of the speed at which they work, are very short lived (unless there is an actual unrecoverable issue)
A test shows the website should be usable within 5 seconds and a full load of website in around 8 seconds so your browser never timed out and I'm guessing it probably took around 10 seconds, which gives the impression of the same issue
I could be entirely wrong sorry but the above hopefully may help you understand a little better
Many thanks
John
-
Thanks for that information. Club Jazz is the only site I visit where this happens.
-
16:57 & 16:59 about 3x then 5x "Connection refused" from this IP using https for specific thread then unread posts.
--
TG
-
Hi
I read this yesterday and had a little think overnight
Richard confirmed host corrected issue in Apache however, it may not be the issue causing this
It could also be an update to distro/cPanel/easyapache which has overwritten the change or other code which stops the change (sorry, we do not use cPanel on shared hosting)
I am leaning towards it is not resource running out
The easiest way forward, given that time stamps are been posted, is to look at the logs and see if any requests are shown within say 1 minute (+ or -) of the time stamps posted (due to time differences on different computers)
As posted earlier, same applies, no requests, update support ticket or open new support ticket, if requests are shown, look at website code
Lastly, it could be a blip I suppose, but due to the nature of the issue, in that it is intermittent and no time repeatable i.e. Say happens on the hour or 8am etc... so this could take a little time before it is fully resolved
Many thanks
John
-
Error again this evening. 20:27.
Screen read:
This site can’t be reached
clubjazz.org refused to connect.
Try:
Checking the connection
Checking the proxy and the firewall
ERR_CONNECTION_REFUSED
-
I've updated the support ticket with my host with your information.
-
Just experienced the same again 13:40. No amount of clicking reload or even re selecting the site made any difference. Had to go off somewhere else and when I came back I got in okay.
-
The host can't find anything so we'll just have to monitor it.
-
Hi RichardA
If you would like to, google statuscake monitoring.
They will monitor a website free but every 5 minutes
It's just a thought
Many thanks
John
-
11:33 > 11:34 am = 10+ times in a row "Connection refused"
-
I keep getting it all the time. I just gave up noting it.
-
Probably for the best, I get no entries in my error logs each time it happens so there's nothing I can do about it at my end, and my host has no information to go on.