Unable to SSH with default credentials

[cyberk]

so i figured i'd post in here in case anyone has a solution before I continue to troubleshoot with UDI. Short story, after updates I can no longer ssh in with admin/admin

 

These are the steps I followed
- ssh into Polisy
- run command curl -s https://pkg.isy.io/script/update121.sh | sudo bash sudo shutdown -r now
- reboot Polisy
- run command cat /usr/local/etc/udx.d/static/update13.sh | sudo bash sudo shutdown -r now
- reboot Polisy
- run command sudo pkg update && sudo pkg upgrade
- reboot Polisy
- no longer able to SSH in, admin/admin no longer works. No web page on port 80 or port 3000

[Bumbershoot]

There's nothing that the last commands (sudo pkg update && sudo pkg upgrade) you ran that would bork your Polisy, or everyone who's up to date would find that their Polisy is borked as well.  

Are your automations working?  If you have the UDI Portal, does your Polisy show up as online?  Is one green LED lit on the front of your Polisy?  If the answer to any of these is yes, then make sure that the IP address didn't change on your network.  Otherwise, unplug your Polisy, wait a minute, plug it back in and see if it comes alive normally.  If it doesn't, then file a support ticket with UDI.

BTW, the command: `sudo shutdown -r now` is a reboot command.  No need for the additional reboots.

[Geddy]

@cyberk As @Bumbershoot points out nothing you ran should mess it up. But it could be that if it's in a very early production run there could be a chip issue when attempting the OS update. Also, I don't think any of what you ran would have reset the password to default. But it sounds like your device isn't even on the network. 

Make sure you have checked out the troubleshooting steps in the WIKI for the Polisy User Guide.

During some of the upgrades it can take a while (several minutes) to process. Make sure you are allowing a lot of time before removing power to the device (even then power cycle isn't usually necessary). It's possible it you ran the "shutdown -r now" command and pulled the power too soon interrupting the process it was in. 

If you're not getting web pages and cannot get to the device via SSH then it's not booted properly. Can you tell if the device has reconnected to the network? It could be at a different IP address if you didn't have IP Reservation at the router level. It's preferred to assign the IP at the router DHCP level rather than the device setting in case you change routers in the future the device will auto join and pull an IP address from the new router. 

1 - Make sure you see the device connected to the network from your router. 
2 - if IP changed try new IP to connect
3 - What is the light pattern on the Polisy?
 

If you've opened a ticket with UD they'll get back to you soon. It might take a little longer during the weekend, but you'll get help soon. 

 

[macjeff]

I am basically having this issue but mine i ran updates this AM.  I tried to SSH in tonight and nothing worked but PG3 and everything else worked.

Then I rebooted Polisy using the command in pg2.   Now I cant get in at all.  No SSH, No http, no https. no admin console BUT the IP responds to a ping

I suspect corrupted OS.

I have backups but wanted to know if any quick fix

 

[larryllix]

9 minutes ago, macjeff said:

I am basically having this issue but mine i ran updates this AM.  I tried to SSH in tonight and nothing worked but PG3 and everything else worked.

Then I rebooted Polisy using the command in pg2.   Now I cant get in at all.  No SSH, No http, no https. no admin console BUT the IP responds to a ping

I suspect corrupted OS.

I have backups but wanted to know if any quick fix

 

Sounds like another device may have got onto the IP address and clobbered your comms with polisy. Have you assigned an IP address for it in the DHCP reservation table or manually assigned an IP address inside your polisy?

If this is the problem you may need to assign an IP address in your router for a fixed address and then power cycle your router to force the other device to assume another IP address.

[macjeff]

Just now, larryllix said:

Sounds like another device may have got onto the IP address and clobbered your comms with polisy. Have you assigned an IP address for it in the DHCP reservation table or manually assigned an IP address inside your polisy?

If this is the problem you may need to assign an IP address in your router for a fixed address and then power cycle your router to force the other device to assume another IP address.

I have it above the DHCP range.  Trying that and then will start resetting.  I am going to post outside this topic as was told by others this may be an OS issue

[Bumbershoot]

1 hour ago, macjeff said:

I have it above the DHCP range.  Trying that and then will start resetting.  I am going to post outside this topic as was told by others this may be an OS issue

I think you’ve filled up your disk with the updates.  If you get in, run ‘sudo pkg clean’  which will clear the package cache.  Check your disk space with ‘df - h’ and if you only have 4gb of total space, you have an early Polisy.  UDI needed to reflash the OS on the disk to make much more space available. 

[larryllix]

7 hours ago, Bumbershoot said:

I think you’ve filled up your disk with the updates.  If you get in, run ‘sudo pkg clean’  which will clear the package cache.  Check your disk space with ‘df - h’ and if you only have 4gb of total space, you have an early Polisy.  UDI needed to reflash the OS on the disk to make much more space available. 

Thanks!

2.1G still avail here.

[JBanaszak]

I just updated yesterday and have the same problem.  I can login via the web interface but cannot SSH in via Terminal.  Subscribing....

[macjeff]

55 minutes ago, JBanaszak said:

I just updated yesterday and have the same problem.  I can login via the web interface but cannot SSH in via Terminal.  Subscribing....

Please email support.  AND DONT REBOOT Polisy.  Once you do you will have no access because HTTP stays up until you reboot.  I made the same mistake on TWO polisys.

 

Please post on this thread also.  I think this is all the same issue but this discussion is more about possible out of space.  Thats not the issue the updates caused