Hi there,
The Wunderground API seems to have suddenly gone offline for no apparent reason last night around 6 pm, leaving everything offline & on Wunderground there is a dramatic drop to 0 successes & 0 failures.
I have tried regenerating the API & it’s just simply not responding to the website at all.
Anyone had the same problem?
Thanks
Jamie
AFAIK no other problems. Also your data at WU is updated correctly.
The errors are severe and not related to API-key as that would give another error message.
The data is available when requested in the browser with different API-keys
https://api.weather.com/v2/pws/observations/current?stationId=IHERNE120&format=json&units=m&numericPrecision=decimal&apiKey=_here_api_key_
Go to http://kenthcwx.vastserve.com/live/PWS_module_test.php => click button “load files”
The error messages are identical for both WU requests
PWS_load_files.php (374) WU-ccn________: time spent: 0.0255 - invalid CURL TCP connection reset by peer https://api.weather.com/v2/pws/observations/current?stationId=IHERNE120&format=json&units=m&numericPrecision=decimal&apiKey=_API_SETTING_
PWS_load_files.php (374) WU_forecast___: time spent: 0.0176 - invalid CURL TCP connection reset by peer https://api.weather.com/v3/wx/forecast/daily/5day?geocode=51.37,1.11&format=json&units=h&language=en-GB&apiKey=_API_SETTING_
The other API request (earthquakes) is OK, so it is probably not a local server problem.
Using Google with “How do I fix TCP connection reset by peer?” or “What is TCP connection reset by peer” points to a server problem at WU.
Although this takes far longer then normal in these cases.
If this continues you should post a support request at WU and at Vastserve as their servers are unable to communicate.
=== edit 11:35 UTC
Tested the .CSV requests. They also fail with the same error message.
Could be a DNS problem with the WU site also.
There were problems with IP-6 addresses yesterday at WU, It now works OK with IP-6 but not with IP-4 104.82.93.144
Also there is an update from ecowitt (for the GW1000) regarding WU-ip adresses
=== edit 11:45 UTC
You regenerated your WU-API key, was that because you over-used the 1500 calls/day?
If that was caused by over-usage, the counters are reset at midnight (? California time?)
So it should be solved then shortly.
Wim
P.S. As soon as your GW1000/DP1500 arrives these kind of problems can be solved by uploading from the GW1000 directly to your website.
That way there are two sources of similar data, the console=> WU and the GW1000=> your website.
You can then switch between the two anytime there is a problem in less then a few seconds using easyweather.
There are other new problems with this provider with an extra security setting
http://wvdkuil.vastserve.com/pwsWDxx/
http://ewittw8686etaf.vastserve.com/pwsWD/
http://kenthcwx.vastserve.com/live/
PWS_cron_stationcron.php => success files loaded + history recalculated + history saved + no roll-over needed
The station cron tries to read the history => empty array => updates and tries to save no luck.
So the history file seems to be updated but it can not be read as it is prohibited
Warning: unserialize() has been disabled for security reasons in /home/vol1000_8/vastserve.com/vasts_26019732/htdocs/pwsWDxx/PWS_listfile.php on line 75
And serialize/unserialize is already for years the preferred way to store such small arrays on disk!
Or does anyone knows a reason why they are doing this?
Wim
Website seems to be working fine now. GW1000 is coming within the next two weeks so isn’t a huge problem if it continues. Odd how it does it though.
Small problem remains in the history as the low temp values for month/year/alltime are now zero.
Wim
