Topic: Local METAR reports Not loading

[tshattuck]

Hello:
I noticed today my webpage wxmetar.php will not load and it locks both my browsers (Firefox and Internet Explorer). The web page is part of the php scripts from Ken True.
I have not made any recent changes to this page. Please see attached file.

Don't know why I am having this issue. I did not update NWS Alerts in May,2019 as I am not using Leaflet/OpenStreetMaps. I don't know if this may be impacting the wxmetar.phppage. Does anyone know what the issue here is?

Any assistance is appreciated.

[DW7240]

Hey,

Interesting, I've got the same issue, also my site has been very slow, to getting 503 Internal Server error for the last 3 days, I've also done nothing to prompt this error, my site is on a GoDaddy Server, apparently GoDaddy have changed all the Urls to another format, something about parent and child locations, according to the help forum page of their site.

Anybody else with this issue, or with GoDaddy on a go slow to non existent site load (503 error)

Thanks.

Nick. dw7240.com

[tshattuck]

Nick:
My site is also on GoDaddy and I am getting the 503 error also. I checked the metarcache files and they haven't updated in two days.
My file permissions are 644 in the cache folder and the cache folder is 755.

I am glad it's not something I did. Hopefully someone from the forum can tell us how to correct.

Regards,

[tshattuck]

Folks
Check this link:
http://www.gigharborweather.com/wxmetar.php

He is getting error: unable to load KRNT data RC=302 Object Moved

GoDaddy changed something to impact the php files. I believe I have the files in the proper directory. I checked other files my cache directory and they are updating. The metarcache files are the only ones not updating.   

Thanks

[Jasiu]

http://www.gigharborweather.com/check-fetch-times.php?show=versions

Using a lot of old code.  In particular, you need 1.17 of get-metar-conditions-inc.php in order to do https fetches.

You are getting the "object moved" redirect because the old code fetches the http version and won't follow the redirect.

[tshattuck]

Jasiu:
Thanks for the feedback.

I ran again the check-fetch-times.php file and verified I am running Version 1.17 of get-metar-conditions-inc.php.
I noticed the problem so far appears with folks who use GoDaddy as their website host.

Hopefully someone from the forum can shed some light on this issue.

Regards,

[Jasiu]

What's the URL of your site?

[PaulMy]

I am with GoDaddy and my http://www.komokaweather.ca/wxmetar.php is not working

Enjoy,
Paul

[92merc]

I'm on GD also.  Mine loaded in a few seconds.

https://www.bismarckweather.net/wxmetar.php

[Jasiu]

Tom - never mind - it's right there at the bottom of you post. Doh.

[Jasiu]

I was able to get

view-source:http://www.komokaweather.com/komokaweather-ca/wxmetar.php?debug=y

to load after a long wait.  I'm also trying

view-source:http://yourlocalweather-clay-ny.com/wxmetar.php?debug=y

and despite having lunch since I started it, it's still not done.

Anyway, in the former case, the issue is is resolving the NOAA host:

<!-- mtr_conditions using METAR ICAO='CYXU' -->
<!-- curl fetching 'https://tgftp.nws.noaa.gov/data/observations/metar/stations/CYXU.TXT' -->
<!-- curl Error: Could not resolve host: tgftp.nws.noaa.gov -->
<!-- HTTP stats:  RC=0 dest= port=0 (from sce=)
      Times: dns=0.000 conn=0.000 pxfer=0.000 get=0.003 total=0.003 secs -->
<!-- headers returned:

 -->
<!-- mtr_conditions returns RC='' for ICAO/METAR='CYXU' -->

Not sure why it is so painfully slow as the CURL stats are showing a quick (non-) response.

Anyway, you need to talk to your provider (GD?) about why the DNS resolution is failing.

[rlee171]

Just spent 30 minutes on the phone with GD tech support and they offered no help whatsoever. Although unfortunately I do not have the skill level to go toe to toe with the comedian I was talking to. I referenced the suggestion made by Jasiu that the DNS  resolution is failing. I was able to get him to do do a view-source and showed him the "<!-- curl Error: Could not resolve host: tgftp.nws.noaa.gov --> He insisted that the problem is with our "custom" scripts and not with them. I am up to date on my scripts:  https://www.hsnpar.com/check-fetch-times.php?show=versions  I see that gigharborweather & komokaweather are still having issues as I am sure others are. Anyone having any luck?

[Jasiu]

As a check to make sure this is the problem and to maybe help convince tech support people, you could just plug the IP address into the code.  This is NOT a permanent solution, however.

To do that, look for this code in get-metar-conditions-inc.php:

Code: [Select]

  if (isset($icao) and strlen($icao) == 4) {
    $Debug.= "<!-- mtr_conditions using METAR ICAO='$icao' -->\n";
    $host = 'tgftp.nws.noaa.gov';
    $path = '/data/observations/metar/stations/';
    $metarURL = 'https://' . $host . $path . $icao . '.TXT';
    $html = '';
    $raw = '';

Change the assignment of $host to:

Code: [Select]

// $host = 'tgftp.nws.noaa.gov';
$host = '140.90.101.79';

[rlee171]

Jasiu...   didn't work, however the page loaded quickly, it was taking 60 - 90 secs before.

[Jasiu]

Crud...

<!-- curl fetching 'https://140.90.101.79/data/observations/metar/stations/KHOT.TXT' -->
<!-- curl Error: SSL: no alternative certificate subject name matches target host name '140.90.101.79' -->
<!-- HTTP stats:  RC=0 dest=140.90.101.79 port=443 (from sce=50.62.176.52)
      Times: dns=0.000 conn=0.056 pxfer=0.000 get=0.196 total=0.196 secs -->

Dang security is too secure.

 ---

It doesn't look like GoDaddy publishes the names/addresses of its DNS servers publicly but you should be able to find them.  Here's the help page:

https://ca.godaddy.com/help/find-my-godaddy-nameservers-12318

I assume you want to go to the cPanel shared hosting link on that page and then follow the instructions to get to the NS (nameservers) section.

The reason I'm asking is if I know their servers' IP addresses, then I can do a query directly to their servers and see what they are returning.

[rlee171]

Ok, the "warden" has dinner on the table....  I'll check it in a few.  btw, thanks for giving us a hand with this.

[Jasiu]

Dinner is important!! 

[rlee171]

23.229.178.136

[Jasiu]

OK I think I was barking up a wrong tree here because that is the authoritative DNS nameserver for your domain, not where the server is getting its search results. I'm two times zones ahead of you and getting tired. And DNS always gives me a headache. Can pick up on this in the morning if someone else (who knows more) doesn't figure it out.

[rlee171]

Absolutely....   Thanks

[rlee171]

For those of us using Ken's "standard" template for our home page this problem is not just the Metar Reports page not displaying correctly, it delays the home page from loading in a timely manner (actually a very long time, if at all) I assume it is because it is using our "local" metar info for the text description of the current conditions displayed just above the temperature, currently displaying on my site as: unable to load KHOT data RC= where it would normally display "Cloudy" or whatever the metar report is at the time. However after making the change to the IP address (for testing, see Jasiu's post above), my site at least loads at it's normal speed, a second or two. I don't know if it is just those of us using GoDaddy for hosting, but so far those of us posting about this problem do have that in common and it hit us all at the same time. I have noticed several sites having this problem, although I have also noticed there are a few loading normally. Odd.

[92merc]

I'm using the Saratoga templates and GD. Still working fine here.

[rlee171]

I guess that removes GoDaddy as the potential culprit. Anyone have any suggestions for those of us that still have broken sites??

[AWL]

I guess that removes GoDaddy as the potential culprit. Anyone have any suggestions for those of us that still have broken sites??

Don't think I would rule Go Daddy out yet. Wonder if the sites that aren't working are all on the same GoDaddy server?

[rlee171]

I have spoken to them twice and they insist it is not their servers.