Is the rtupdate.wunderground.com address no longer valid?

  • 1
  • Question
  • Updated 2 weeks ago
WU stopped accepting my weather data Wednesday evening (5:04 PM 1/29/2020).  I see today that the response back from WU has changed to HTTP/1.1 404 Not Found Date: Fri, 31 Jan 2020 16:41:42 GMT Content-Type: text/html Transfer-Encoding: chunked Connection: close 92
Has the rapid fire input (rtupdate.wunderground.com) been discontinued?

Photo of joegr

joegr

  • 31 Posts
  • 10 Reply Likes

Posted 3 weeks ago

  • 1
Photo of Brice Ruth

Brice Ruth

  • 5 Posts
  • 0 Reply Likes
It's working for me, over HTTP, I think SSL issues continue to be a problem.
Photo of Paul Hutch

Paul Hutch

  • 20 Posts
  • 7 Reply Likes
HTTPS started working again in the past hour or two for me
Photo of joegr

joegr

  • 31 Posts
  • 10 Reply Likes
I'm currently still getting "Connection Failed"  I am using DNS and not a hard coded IP address.  I will try rebooting the router when I am on site later today.
Photo of joegr

joegr

  • 31 Posts
  • 10 Reply Likes
Yeah, they changed something.  I was using a variation of the common examples for sending data to WU with an Arduino.  I changed libraries and rewrote my data send routine, and it is working again now.
Photo of Leon Shaner

Leon Shaner

  • 12 Posts
  • 0 Reply Likes
Getting 404 Not Found also. This is different than a SSL error.
Photo of Tim Roche

Tim Roche, Official Rep

  • 354 Posts
  • 53 Reply Likes
You can not use a hard coded IP address, you must use weatherstation.wunderground.com or rtupdate.wunderground.com
Photo of joegr

joegr

  • 31 Posts
  • 10 Reply Likes
Mine wasn't hard coded.  That wasn't the problem.  Something changed in the way the Get request is or isn't accepted.  Apparently my implementation, while it worked for years, was not exact enough to work after this change.

Photo of Tim Roche

Tim Roche, Official Rep

  • 354 Posts
  • 53 Reply Likes
sorry misread that

For requests to route properly, the
host header  must be set correctly
path must be correct
request must be sent to either rtupdate... or weatherstation...
Photo of Leon Shaner

Leon Shaner

  • 12 Posts
  • 0 Reply Likes
Tim, rtupdate was working before the certificate debacle. Now it gives a 404 not found. Exactly what needs to be set in the header?
Photo of Leon Shaner

Leon Shaner

  • 12 Posts
  • 0 Reply Likes
It isn't 100% failure rate. Seems more like a LB hitting a bad node, roughly every 1/3rd hit -- recent excerpt:
Feb  3 12:54:34 Wunderground-RF: Failed upload attempt 1: HTTP Error 404: Not Found
Feb  3 13:05:07 Wunderground-RF: Failed upload attempt 1: The read operation timed out
Feb  3 13:05:24 Wunderground-RF: Failed upload attempt 1: [Errno 104] Connection reset by peer
Feb  3 13:05:32 Wunderground-RF: Failed upload attempt 1: <urlopen error [Errno 104] Connection reset by peer>
Feb  3 13:10:41 Wunderground-RF: Failed upload attempt 1: HTTP Error 404: Not Found
Feb  3 13:17:07 Wunderground-RF: Failed upload attempt 1: [Errno 104] Connection reset by peer
Feb  3 13:17:29 Wunderground-RF: Failed upload attempt 1: Remote end closed connection without response
Feb  3 13:17:33 Wunderground-RF: Failed upload attempt 1: HTTP Error 404: Not Found
Feb  3 13:17:39 Wunderground-RF: Failed upload attempt 1: HTTP Error 404: Not Found
Feb  3 13:17:49 Wunderground-RF: Failed upload attempt 1: HTTP Error 404: Not Found
Feb  3 13:18:12 Wunderground-RF: Failed upload attempt 1: HTTP Error 404: Not Found
Feb  3 13:25:17 Wunderground-RF: Failed upload attempt 1: HTTP Error 404: Not Found
Feb  3 13:25:20 Wunderground-RF: Failed upload attempt 1: HTTP Error 404: Not FoundFeb  3 13:25:20 Wunderground-RF: Failed upload attempt 1: HTTP Error 404: Not Found
Feb  3 13:25:21 Wunderground-RF: Failed upload attempt 1: HTTP Error 404: Not Found
Feb  3 13:25:22 Wunderground-RF: Failed upload attempt 1: HTTP Error 404: Not FoundFeb  3 13:26:05 Wunderground-RF: Failed upload attempt 1: HTTP Error 404: Not Found
Feb  3 13:26:16 Wunderground-RF: Failed upload attempt 1: The read operation timed out
Feb  3 13:26:36 Wunderground-RF: Failed upload attempt 1: The read operation timed out
Feb  3 13:26:56 Wunderground-RF: Failed upload attempt 1: <urlopen error [Errno 104] Connection reset by peer>
Feb  3 13:26:59 Wunderground-RF: Failed upload attempt 1: HTTP Error 404: Not Found
(Edited)
Photo of Tim Roche

Tim Roche, Official Rep

  • 354 Posts
  • 53 Reply Likes
still getting these errors?
Photo of Leon Shaner

Leon Shaner

  • 12 Posts
  • 0 Reply Likes
Yes.  But I may have just found an issue on my end.  The code I am using may be inadvertently trying to rapid-fire against the weatherstation URL, not the rtupdate URL.  I can't spot the reason for it, so I've contacted the development community for the software I am running.

Feb  3 14:49:56 Wunderground-RF: Failed to publish record 2020-02-03 14:49:57 EST (1580759397): Failed upload after 1 tries
Feb  3 14:49:57 Wunderground-RF: Failed upload attempt 1: HTTP Error 404: Not Found
Feb  3 14:49:57 Wunderground-RF: Failed to publish record 2020-02-03 14:49:57 EST (1580759397): Failed upload after 1 tries
Feb  3 14:49:58 Wunderground-RF: Failed upload attempt 1: HTTP Error 404: Not Found
Feb  3 14:49:58 Wunderground-RF: Failed to publish record 2020-02-03 14:49:58 EST (1580759398): Failed upload after 1 tries
Feb  3 14:49:59 Wunderground-RF: Failed upload attempt 1: HTTP Error 404: Not Found
Feb  3 14:49:59 Wunderground-RF: Failed to publish record 2020-02-03 14:49:59 EST (1580759399): Failed upload after 1 tries

After temporarily forcing the URL to rtupdate, the 404's are gone.
Photo of Leon Shaner

Leon Shaner

  • 12 Posts
  • 0 Reply Likes
Actually, I'm still getting 404's even after hard-coding the right rtupdates URL:

Feb  3 15:21:06 Wunderground-RF: Failed to publish record 2020-02-03 15:21:06 EST (1580761266): Failed upload after 1 tries
Feb  3 15:21:06 Wunderground-RF: Failed upload attempt 1: HTTP Error 404: Not Found
Feb  3 15:21:06 Wunderground-RF: Failed to publish record 2020-02-03 15:21:06 EST (1580761266): Failed upload after 1 tries
Feb  3 15:23:10 Wunderground-RF: Failed upload attempt 1: HTTP Error 404: Not Found
Feb  3 15:23:10 Wunderground-RF: Failed to publish record 2020-02-03 15:23:10 EST (1580761390): Failed upload after 1 tries

Photo of Tim Roche

Tim Roche, Official Rep

  • 354 Posts
  • 53 Reply Likes
weatherstation and rapidfire are no longer different so no worries there
Photo of Leon Shaner

Leon Shaner

  • 12 Posts
  • 0 Reply Likes
Still rampant:

Feb 3 20:06:00 Wunderground-RF: Failed to publish record 2020-02-03 20:06:00 EST (1580778360): Failed upload after 1 tries
Feb 3 20:06:02 Wunderground-RF: Failed upload attempt 1: HTTP Error 404: Not Found
Feb 3 20:06:02 Wunderground-RF: Failed to publish record 2020-02-03 20:06:02 EST (1580778362): Failed upload after 1 tries
Feb 3 20:26:10 Wunderground-RF: Failed upload attempt 1: HTTP Error 404: Not Found
Feb 3 20:26:10 Wunderground-RF: Failed to publish record 2020-02-03 20:26:10 EST (1580779570): Failed upload after 1 tries
Feb 3 20:26:11 Wunderground-RF: Failed upload attempt 1: HTTP Error 404: Not Found
Feb 3 20:26:11 Wunderground-RF: Failed to publish record 2020-02-03 20:26:11 EST (1580779571): Failed upload after 1 tries
Feb 3 20:26:14 Wunderground-RF: Failed upload attempt 1: HTTP Error 404: Not Found
Feb 3 20:26:14 Wunderground-RF: Failed to publish record 2020-02-03 20:26:14 EST (1580779574): Failed upload after 1 tries
Feb 3 20:26:14 Wunderground-RF: Failed upload attempt 1: HTTP Error 404: Not Found
Feb 3 20:26:14 Wunderground-RF: Failed to publish record 2020-02-03 20:26:14 EST (1580779574): Failed upload after 1 tries
Photo of Leon Shaner

Leon Shaner

  • 12 Posts
  • 0 Reply Likes
Still broken.
Photo of joegr

joegr

  • 31 Posts
  • 10 Reply Likes
What software are you using?
Photo of Leon Shaner

Leon Shaner

  • 12 Posts
  • 0 Reply Likes
Mine is weewx. It doesn't matter, though. I can simulate the 404's with curl. 404 has a very specific meaning, "not found." The traffic is either going to the wrong node or it's the right node, but it's misconfigured / has a bad code deployment, missing the endpoint, etc.
Photo of Bruce Brownlee

Bruce Brownlee

  • 4 Posts
  • 3 Reply Likes
Mine is "timing out".  I raised timeout and most go through, however they are taking 65 seconds on average.
Photo of Leon Shaner

Leon Shaner

  • 12 Posts
  • 0 Reply Likes
Yes, I had to increase timeouts early last year when the site started degrading, before.
Photo of Jason Curtiss

Jason Curtiss

  • 2 Posts
  • 0 Reply Likes
I'm using Weewx and am having issues as well.  Initially I was getting the SSL errors and now seeing the errors below.  After restarting it will up load for a bit then stop displaying this error.

restx: Wunderground-RF: Thread exiting. Reason: hostname 'rtupdate.wunderground.com' doesn't match either of '*.prod-pws-ng-546567-997b58a668d15d562a6bed58ea7c5f9e-0000.us-south.containers.appdomain.cloud', 'prod-pws-ng-546567-997b58a668d15d562a6bed58ea7c5f9e-0000.us-south.containers.appdomain.cloud', 'prod-pws-ng-546567.us-south.containers.appdomain.cloud'
Photo of Leon Shaner

Leon Shaner

  • 12 Posts
  • 0 Reply Likes
Still getting 104 "Connection reset by peer", occasionally, too:

Feb 4 11:31:58 Wunderground-RF: Failed to publish record 2020-02-04 11:31:58 EST (1580833918): Failed upload after 1 tries
Feb 4 11:35:10 Wunderground-RF: Failed upload attempt 1: [Errno 104] Connection reset by peer
Feb 4 11:35:10 Wunderground-RF: Failed to publish record 2020-02-04 11:35:10 EST (1580834110): Failed upload after 1 tries
Feb 4 11:35:14 Wunderground-RF: Failed upload attempt 1: HTTP Error 404: Not Found
Photo of Bruce Brownlee

Bruce Brownlee

  • 4 Posts
  • 3 Reply Likes
Weird thing tho, I am using python 'Requests' library.  That update takes 65 seconds.  I have tried other methods (CURL, other python libs) with same results.
When I paste the URL into a browser (Chrome), the update happens immediately...
I am thinking it is either a cookies or headers issue...
(Edited)
Photo of Leon Shaner

Leon Shaner

  • 12 Posts
  • 0 Reply Likes
FWIW, I haven't seen any 404's since around these times from last night:

Feb  4 20:43:52 Wunderground-RF: Failed to publish record 2020-02-04 20:43:53 EST (1580867033): Failed upload after 1 triesFeb  4 20:43:52 Wunderground-RF: Failed upload attempt 1: HTTP Error 404: Not Found
Feb  4 20:43:52 Wunderground-RF: Failed to publish record 2020-02-04 20:43:53 EST (1580867033): Failed upload after 1 tries
Feb  4 20:49:10 Wunderground-RF: Failed upload attempt 1: <urlopen error _ssl.c:1039: The handshake operation timed out>
Feb  4 20:49:10 Wunderground-RF: Failed to publish record 2020-02-04 20:48:49 EST (1580867329): Failed upload after 1 tries
Feb  4 20:49:45 Wunderground-RF: Failed upload attempt 1: <urlopen error timed out>
Feb  4 20:49:45 Wunderground-RF: Failed to publish record 2020-02-04 20:49:15 EST (1580867355): Failed upload after 1 tries
Feb  4 20:50:19 Wunderground-RF: Failed upload attempt 1: <urlopen error timed out>
Feb  4 20:50:19 Wunderground-RF: Failed to publish record 2020-02-04 20:49:49 EST (1580867389): Failed upload after 1 tries
Feb  4 21:04:41 Wunderground-RF: Failed upload attempt 1: <urlopen error [Errno 104] Connection reset by peer>
Feb  4 21:04:41 Wunderground-RF: Failed to publish record 2020-02-04 21:04:41 EST (1580868281): Failed upload after 1 tries

(Edited)
Photo of Jason Curtiss

Jason Curtiss

  • 2 Posts
  • 0 Reply Likes
Mine has been working without any errors since last night (2/4/20) around 7p.  Fingers are crossed!
Photo of Bruce Brownlee

Bruce Brownlee

  • 4 Posts
  • 3 Reply Likes
It was (I think) an issue with their load balancing or DNS config.  Tim asked for my output from CURL, which I had never really looked at.  There were 3 IP addresses that resolved to weatherstation.wunderground.com (rtupdate is a CN).  The CURL output showed that the first two were not responding and took 30 seconds each to time out.  The third responded and completed the action immediately.  
My 65 second update time has since gone to less than 1 sec.