Welcome Eric, from your last email it seems you are trying to ping "openwisp2.mydomain.com" which is, as indicated in the documentation (many times), an example domain which is meant to be substituted with the hostname you are really using.
"Substitute openwisp2.mydomain.com with your production server's hostname." What is the address you were trying to reach? You can find that in the ansible inventory file (in the tutorial we call this "hosts"), if you have doubts post the contents of this file here. Please read more carefully the documentation available at https://github.com/openwisp/ansible-openwisp2, it contains all the information you need to make it work. If you have further questions or there's some passage you don't understand, please don't hesitate to ask specific questions, that will help us to understand how to improve the docs. Federico On Sat, Oct 6, 2018 at 2:07 PM Eric Van Dam <[email protected]> wrote: > Hi Ajay, > > Thanks for you reply. The Raspberry Pi is definitely reachable. I am able > to ping the hostname: > > C:\>ping openwisp2.mydomain.com > > Pinging openwisp2.mydomain.com [192.168.1.10] with 32 bytes of data: > Reply from 192.168.1.10: bytes=32 time<1ms TTL=64 > Reply from 192.168.1.10: bytes=32 time<1ms TTL=64 > Reply from 192.168.1.10: bytes=32 time<1ms TTL=64 > Reply from 192.168.1.10: bytes=32 time<1ms TTL=64 > > Ping statistics for 192.168.1.10: > Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), > Approximate round trip times in milli-seconds: > Minimum = 0ms, Maximum = 0ms, Average = 0ms > > > When I try to open 'openwisp2.mydomain.com/admin' I get your standard > 'unable to connect' error. It's the same whether I use http or https. > > In Chrome: > > This site can’t be reached > openwisp2.mydomain.com refused to connect. > Go to http://mydomain.com/ > Search Google for openwisp2 mydomain com admin > ERR_CONNECTION_REFUSED > > > In Firefox: > > Unable to connect > > Firefox can’t establish a connection to the server at > openwisp2.mydomain.com. > > The site could be temporarily unavailable or too busy. Try again in a > few moments. > If you are unable to load any pages, check your computer’s network > connection. > If your computer or network is protected by a firewall or proxy, make > sure that Firefox is permitted to access the Web. > > > Does anyone know the location of any log files I could look at to > troubleshoot? > > E > > On Saturday, October 6, 2018 at 4:11:46 AM UTC-4, Ajay Tripathi wrote: >> >> Hi Eric, >> >> NOTE: i've never installed openwisp on Raspberry Pi, if there is any >> extra step for it someone else will be able to help. (Please wait for that) >> >> Yes, it looks like playbook ran successfully and you should be able to >> access it. >> Can you please share what error you are getting while trying to access >> that page? >> >> Without knowing the error all that comes to my mind: >> 1. To access openwisp you need to go to `openwisp2.mydomain.com/admin` >> <http://openwisp2.mydomain.com/admin> (please note: `/admin` here) >> 2. Check if your Raspberry Pi is connected and you are able to ping that >> domain. >> >> Cordially, >> Ajay Tripathi >> > -- > You received this message because you are subscribed to the Google Groups > "OpenWISP" 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. > -- You received this message because you are subscribed to the Google Groups "OpenWISP" 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.
