You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm currently running into issues with v. 1.6.1. The Control panel simply cannot reach my device -- except when I run "prey config gui" and go through the process. After which, the Control panel does connect with my device; however, further attempts to send commands to my device or locate my device fail.
When I run the command "prey config check", prey outputs "Checking installation. Error! Unable to verify keys." This is odd for two reasons: 1) presumably, if the GUI version of config can verify keys, why can't the command line version? 2) the API and device keys are as they always were.
I thought, perhaps, this was a permissions related issue, but prey owns both both the "/etc/prey" and "/etc/prey/prey.conf".
Any suggestions on how to fix this? It's disconcerting to discover that prey had not been protecting my computer for a while.
The text was updated successfully, but these errors were encountered:
Hello all,
I'm currently running into issues with v. 1.6.1. The Control panel simply cannot reach my device -- except when I run "prey config gui" and go through the process. After which, the Control panel does connect with my device; however, further attempts to send commands to my device or locate my device fail.
When I run the command "prey config check", prey outputs "Checking installation. Error! Unable to verify keys." This is odd for two reasons: 1) presumably, if the GUI version of config can verify keys, why can't the command line version? 2) the API and device keys are as they always were.
I thought, perhaps, this was a permissions related issue, but prey owns both both the "/etc/prey" and "/etc/prey/prey.conf".
Any suggestions on how to fix this? It's disconcerting to discover that prey had not been protecting my computer for a while.
The text was updated successfully, but these errors were encountered: