I can confirm that the DNS is resolving to my weewx ip. This leads me to
believe that the problem lies with either my nginx configuration or my
weewx interceptor configuration.
I mentioned that the pi that's running weewx is also running owncloud,
exposing ports 80/443 in an nginx webserver. I understand that the
interceptor driver listens on port 80 by default, so, according to its
directions, i set up a reverse proxy to port 9000 (where i configured
interceptor to be listening). I think I failed to mention the reverse proxy.
In any case, I've run interceptor directly on port 9000, then hit the
endpoint from a browser, resulting in the following terminal response
mapped packet: {'usUnits': 16, 'dateTime': 1579808958}
I've also updated my nginx config to stop listening on port 80, and tried
running interceptor again on its default port, with the same respnose as
above.
So...
1. I can resolve rtupdate.wunderground.com to correct weewx ip
2. I can run/listen witth interceptor driver, controlling for ports
3. I can confirm reverse proxying is working as expected
Still can't figure out where my data is! Might have to grab myself a
GW1000, unless someone else has insights that I'm missing.
On Thursday, January 23, 2020 at 12:24:44 PM UTC-6, galfert wrote:
>
> Yes, you are correct. I missed the line where you mentioned changing the
> host file on your DNS server. That should have worked. Test that DNS is
> really being served by using a different system on the network to ping the
> WU server name and see if it resolves to the IP address of the WeeWx system.
>
> Still the GW1000 is a better way. No need for DNS trickery.
>
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/weewx-user/c7c18d68-c5d4-44e8-aaf2-20bc06c1aca6%40googlegroups.com.
