Just to close this thread, I decided to let the bridge have port 80 and 
configured apache to listen on port 8000. It's not an elegant solution, but 
everything works. I may revisit it later, after learning more.

I wouldn't have gotten this far without the generous help of the community. 
Thanks to all, and my apologies for sometimes being too ignorant to make 
sense of your advice. Especially to Matthew, I'd like to say that I really 
appreciate your attempts to help me out, and on the occasions when I wasn't 
able to comprehend what you were saying, I hope you didn't feel you had I 
had wasted too much of your time. I'll consult this thread in the future, 
when I hope to be better prepared to understand it.

On Saturday, March 10, 2018 at 3:27:41 PM UTC-5, RobbH wrote:
> Thanks for all the help and patience with my bumbling. I can now report 
> success, as far as the topic of this thread is concerned. I'm currently 
> using Vince's suggestion, Pi-hole for DNS. Once I got a functional bridge, 
> it worked immediately.
> Of course, I've still got some issues to deal with before the new station 
> can go online. DNS is not the issue, so I can start a separate thread if 
> that would be better. I just need to get the Interceptor driver to co-exist 
> with the apache2 server. My situation matches the "most complicated " 
> scenario described in the Interceptor readme file:
> Example 5: weewx is running on host 'pi', which has a web server on port 80
>> to display weewx reports. Configure the driver to listen on port 9999. 
>> Add a
>> reverse proxy to the web server configuration to direct traffic on port 
>> 80 from
>> the device to port 9999. Add a DNS entry so that traffic from the device 
>> is
>> sent to 'pi' instead of the cloud.
> Later in the readme there's an example of a reverse proxy:
>> 2a) Here is an example of an Apache 'reverse proxy' configuration for the
>> Acurite internet bridge. The Apache server sends any requests from the
>> internet bridge to the driver. In the file 
>> /etc/apache2/conf.d/myacurite.conf: 
>> RewriteEngine on
>> RewriteCond %{HTTP_POST} www.myacurite.com
>> RewriteRule ^/weatherstation(.*)$ http://Y.Y.Y.Y/weatherstation$1 
>> <http://y.y.y.y/weatherstation$1>
> I've tried that, but it doesn't seem to do what I need. The driver still 
> reads data as long as it's listening to port 80, but finds nothing when 
> listening on 9999.
> Any advice will be appreciated!
> On Thursday, March 8, 2018 at 11:16:14 AM UTC-5, RobbH wrote:
>> "Supported" makes sense. Thanks for making that distinction, as well as 
>> explaining the change.
>> On Thursday, March 8, 2018 at 11:04:32 AM UTC-5, vince wrote:
>>> On Thursday, March 8, 2018 at 6:39:27 AM UTC-8, RobbH wrote:
>>>> Is dpkg still recommended? I came to my conclusion after reading the 
>>>> docs.
>>>> The latest revision of the installation guide for Debian-based 
>>>> distributions doesn't even mention dpkg.
>>>> http://www.weewx.com/docs/debian.htm
>>> Perhaps 'supported' would be a better term.
>>> The docs were updated to reflect the apt-get method of 
>>> downloading+installing the package in an easier way.   You can always 
>>> download it yourself and install it via dpkg or apt as well, and 
>>> alternately download the tarball and use the original setup.py method.  All 
>>> work fine.

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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to