Client not connecting, but system running

[srthimsen]

I just installed sprinklers_pi yesterday with brand new hardware. The client has been working fine through testing yesterday. This morning, however, the client is unresponsive.

The log file shows the zones ran this morning, but I'm still unable to access the client interface. I'm able to SSH into the Pi without an issue. I tried restarting the service with the same result.

Log file here: https://drive.google.com/file/d/1uJLkA4PjTlLQ2QHJ13o6KeF8s9OZKRZm/view?usp=drivesdk

[nhorvath]

Try clearing your browser cache, or accessing from a different device. There is nothing unusual in the log file.

On Mon, Jun 25, 2018 at 10:43 AM srthimsen notifications@github.com wrote:

I just installed sprinklers_pi yesterday with brand new hardware. The client has been working fine through testing yesterday. This morning, however, the client is unresponsive.

The log file shows the zones ran this morning, but I'm still unable to access the client interface. I'm able to SSH into the Pi without an issue. I tried restarting the service with the same result.

Log file here:

https://drive.google.com/file/d/1uJLkA4PjTlLQ2QHJ13o6KeF8s9OZKRZm/view?usp=drivesdk

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/rszimm/sprinklers_pi/issues/123, or mute the thread https://github.com/notifications/unsubscribe-auth/AAKE3ILh9Qe_H_SbEatKSFnAPtqSZCEfks5uAPb5gaJpZM4U2SQD .

[srthimsen]

I tried both of those, but with same effect.

I then tried going direct to the IP address vs using name, and that worked... Very odd.

[nhorvath]

use nslookup to make sure your name is resolving correctly.

On Mon, Jun 25, 2018 at 2:58 PM srthimsen notifications@github.com wrote:

I tried both of those, but with same effect.

I then tried going direct to the IP address vs using name, and that worked... Very odd.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/rszimm/sprinklers_pi/issues/123#issuecomment-400059258, or mute the thread https://github.com/notifications/unsubscribe-auth/AAKE3PjxeR_WJD__n1GOo7yUzFTa012yks5uATLUgaJpZM4U2SQD .

[srthimsen]

Thanks for all the help!

This is what nslookup 192.168.2.147 is showing: Server: 192.168.2.1 Address: 192.168.2.1#53 server can't find 147.2.168.192.in-addr.arpa: NXDOMAIN

Not sure why it was working fine last night, then nothing today.

[nhorvath]

what does nslookup say for the name you were using?

On Mon, Jun 25, 2018 at 4:36 PM srthimsen notifications@github.com wrote:

Thanks for all the help!

This is what nslookup 192.168.2.147 is showing: Server: 192.168.2.1 Address: 192.168.2.1#53 server can't find 147.2.168.192.in-addr.arpa: NXDOMAIN

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/rszimm/sprinklers_pi/issues/123#issuecomment-400086825, or mute the thread https://github.com/notifications/unsubscribe-auth/AAKE3EuSYb8athIcp63sqZSyC9ty1INlks5uAUmvgaJpZM4U2SQD .

[srthimsen]

Same thing: server can't find raspberrypi

On Mon, Jun 25, 2018 at 2:17 PM Nick Horvath notifications@github.com wrote:

what does nslookup say for the name you were using?

On Mon, Jun 25, 2018 at 4:36 PM srthimsen notifications@github.com wrote:

Thanks for all the help!

This is what nslookup 192.168.2.147 is showing: Server: 192.168.2.1 Address: 192.168.2.1#53 server can't find 147.2.168.192.in-addr.arpa: NXDOMAIN

— You are receiving this because you commented. Reply to this email directly, view it on GitHub < https://github.com/rszimm/sprinklers_pi/issues/123#issuecomment-400086825 , or mute the thread < https://github.com/notifications/unsubscribe-auth/AAKE3EuSYb8athIcp63sqZSyC9ty1INlks5uAUmvgaJpZM4U2SQD

.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/rszimm/sprinklers_pi/issues/123#issuecomment-400098785, or mute the thread https://github.com/notifications/unsubscribe-auth/AHJcInhXVfON8wUMngdD58UGLVAFdPOCks5uAVN2gaJpZM4U2SQD .

[nhorvath]

relying on your router to provide DNS lookups on the local network is notoriously flaky. you should probably just give your pi a static ip locally and use a free DNS service (or a domain you control if you have one) assigned to the local address.

On Mon, Jun 25, 2018 at 5:20 PM srthimsen notifications@github.com wrote:

Same thing: server can't find raspberrypi

On Mon, Jun 25, 2018 at 2:17 PM Nick Horvath notifications@github.com wrote:

what does nslookup say for the name you were using?

On Mon, Jun 25, 2018 at 4:36 PM srthimsen notifications@github.com wrote:

Thanks for all the help!

This is what nslookup 192.168.2.147 is showing: Server: 192.168.2.1 Address: 192.168.2.1#53 server can't find 147.2.168.192.in-addr.arpa: NXDOMAIN

— You are receiving this because you commented. Reply to this email directly, view it on GitHub <

https://github.com/rszimm/sprinklers_pi/issues/123#issuecomment-400086825

, or mute the thread <

https://github.com/notifications/unsubscribe-auth/AAKE3EuSYb8athIcp63sqZSyC9ty1INlks5uAUmvgaJpZM4U2SQD

.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub < https://github.com/rszimm/sprinklers_pi/issues/123#issuecomment-400098785 , or mute the thread < https://github.com/notifications/unsubscribe-auth/AHJcInhXVfON8wUMngdD58UGLVAFdPOCks5uAVN2gaJpZM4U2SQD

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/rszimm/sprinklers_pi/issues/123#issuecomment-400099433, or mute the thread https://github.com/notifications/unsubscribe-auth/AAKE3K3qsvdDlUjndSHEYZTaa2vzhRNMks5uAVQOgaJpZM4U2SQD .

[srthimsen]

I do have my router pointing to OpenDNS, but you're saying it's better to also assign the OpenDNS info directly to the RPi static IP address?

On Mon, Jun 25, 2018 at 3:29 PM Nick Horvath notifications@github.com wrote:

relying on your router to provide DNS lookups on the local network is notoriously flaky. you should probably just give your pi a static ip locally and use a free DNS service (or a domain you control if you have one) assigned to the local address.

On Mon, Jun 25, 2018 at 5:20 PM srthimsen notifications@github.com wrote:

Same thing: server can't find raspberrypi

On Mon, Jun 25, 2018 at 2:17 PM Nick Horvath notifications@github.com wrote:

what does nslookup say for the name you were using?

On Mon, Jun 25, 2018 at 4:36 PM srthimsen notifications@github.com wrote:

Thanks for all the help!

This is what nslookup 192.168.2.147 is showing: Server: 192.168.2.1 Address: 192.168.2.1#53 server can't find 147.2.168.192.in-addr.arpa: NXDOMAIN

— You are receiving this because you commented. Reply to this email directly, view it on GitHub <

https://github.com/rszimm/sprinklers_pi/issues/123#issuecomment-400086825

, or mute the thread <

https://github.com/notifications/unsubscribe-auth/AAKE3EuSYb8athIcp63sqZSyC9ty1INlks5uAUmvgaJpZM4U2SQD

.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <

https://github.com/rszimm/sprinklers_pi/issues/123#issuecomment-400098785

, or mute the thread <

https://github.com/notifications/unsubscribe-auth/AHJcInhXVfON8wUMngdD58UGLVAFdPOCks5uAVN2gaJpZM4U2SQD

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub < https://github.com/rszimm/sprinklers_pi/issues/123#issuecomment-400099433 , or mute the thread < https://github.com/notifications/unsubscribe-auth/AAKE3K3qsvdDlUjndSHEYZTaa2vzhRNMks5uAVQOgaJpZM4U2SQD

.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/rszimm/sprinklers_pi/issues/123#issuecomment-400116224, or mute the thread https://github.com/notifications/unsubscribe-auth/AHJcIlAYZ3KPj5jUXdN8cpElGwPpSmJfks5uAWRLgaJpZM4U2SQD .

[srthimsen]

I think I may have figured it out.

I used an old WN3000RP wifi range extender (Goodwill find!) to get wifi down to where my RPi is located. I remember that when I first got the extender, mobile devices (android phones and my iPad) weren't able to connect to it directly.

Mobile devices were what I was using to test this AM, since I was away from home. At home, my desktop is able to connect to raspberrypi:8080 without issues.

I'm closing this since it's obviously not a software issue, it's something strange going on my wifi range extender, in that it appears to not be passing traffic through to mobile devices correctly??

Thanks @nhorvath for taking the time to provide input and direction!

[srthimsen]

As a follow up for whomever might find this with a similar issue, I was able to reposition my wifi extender to a spot so I could run an Ethernet cable from the extender directly to the Pi, then turned off WiFi on the Pi. I'm able to connect using hostname again on all devices.

Weird.