Cannot SSH or communicate with Pi

[thompson 1]

So after months of flawless operation I noticed I couldn't ssh to my Pi about 2 weeks ago. Activity & networking lights were running, everything appeared okay. So I just hard restarted it and she came back, but a few days later it happened again.

 

I run it headless with a few daemons running (transmission, openvpn, samba, ftp, etc).

 

Here's the message I get when I try to ssh to the Pi using connectbot on my androids:

 

connecting to 192.168.192.100:1773 via ssh

Connection Lost

Failed to connect to 192.168.192.100/192.168.192.100 (port 1773): connect failed: EHOSTUNREACH (No route to host)

 

But now even powering it off doesn't bring back connectivity, it just immediately goes to that. I tried reformatting the SD card on a whim, as well as trying a more robust power supply (neither of which seemed to have any positive effect). I've also ran apt-get update, upgrade & dist-upgrade just to see and it also had no effect.

 

I have a suspicion that openvpn or part of transmission is to blame, but last time I was able to gain access I killed both & it still ended up error'ing minutes later. I did make some changes to IPTables to allow external access while still channeling other traffic through the vpn and also suspect this is part of it (the "failed to connect to 192.168.192.100/192.168.192.100 (port 1773)" doesn't seem like my internal ip should be there twice).

 

Any help is greatly appreciated as I'm a bit lost atm, I do know it's driving me crazy.

[Joshmccullough 0]

When you run an ifconfig command, does the ip address match what you're typing in? My Pi rest due to a power outage along with my diet, and the address changed so I gave it a static address and that fixed the problem.

[5ft24 1]

Bad WiFi dongle

 

Sent from my SM-G900V using Tapatalk

[thompson 1]

I set it up for static ip awhile back, and it's hardwired (wasn't quite convinced wifi had the same speed as wired).

[1pi2many 2]

A couple of things to try

 

1. That the LAN ip is correct. Try ping instead of ssh, look in your router attached devices and see if the

pi is still at 192.168.192.100.

 

2. Add a display/kbd to it, login and run ifconfig

 

3. Download a new raspbian on another sd card, use it to boot and see if the pi hardware is working.

It could be that your sd card is toast.