Thanks for the information, unfortunately I think my bridge may be in an
unrecoverable state. I tried as you suggested and set the interceptor to
respond with both firmware version 224 and 126 (one at a time) and I could
see the desired responses when browsing to it on my computer with responses
looking like {"success":1, "checkversion":"126"} and {"localtime":"%H:%M:%S",
"checkversion":"224"}so it appears the interceptor is working as designed.
But the data captured in the interceptor logs is the same as was originally
pasted in my first post. However I just tried browsing to my acurite
smart hub (which I didn't know you could do) and this is the status shown
with attached screenshot. Please let me know if you've seen this before or
if you know if it's recoverable. I really appreciate you taking the time
to help. Thanks
[image: Screen Shot 2019-04-06 at 7.14.44 PM.png]
On Sat, Apr 6, 2019 at 10:04 AM mwall <[email protected]> wrote:
> On Saturday, April 6, 2019 at 11:15:14 AM UTC-4, Jamie Borget wrote:
>>
>> And when trying to use the methods mentioned in the article you mentioned
>> my Apache logs all show a 404 when trying to post to /messages/. Any help
>> would be greatly appreciated.
>>
>
> if you must run apache on port 80 on the pi, then you must make apache
> reverse proxy any request for /messages/ to the port that the interceptor
> is listening on
>
> if you don't mind running your web server on a different port, then run
> the interceptor on port 80 and your web server on port 8080 or 8000 or
> whatever.
>
> another option is to run nginx listening on port 80, with reverse proxy
> for /messages/ to the port the interceptor is running on, and reverse proxy
> for everything else to whatever port apache is running on. (i tend to use
> a configuration like this for servers that are public-facing, since it
> provides better control and security when you run multiple web services
> such as influx or grafana or php-stuff-on-apache)
>
> m
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/0e2E3F7EG7Y/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> [email protected].
> For more options, visit https://groups.google.com/d/optout.
>
--
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].
For more options, visit https://groups.google.com/d/optout.
