Keeper not starting up
Posted: Thu Mar 02, 2017 2:51 pm
Hey,
I'm installing the cgru package on my workstation (Linux Mint 18.1) but can't get Keeper to start properly.
It works fine on my other machine and server (all running the same OS).
It tries to start and I get a black icon, and eventually the CGRU icon appears but doesn't respond and eventually just disappears again.
Here's the output it spits out in terminal:
CGRU_VERSION 2.2.1 : '/opt/cgru'
Certificate file "/opt/cgru/utilities/keeper/serverhttps.pem" not found, skipping HTTPS serving.
"sni-qt/6952" WARN 15:45:16.231 void StatusNotifierItemFactory::connectToSnw() Invalid interface to SNW_SERVICE
Could not open socket.
192.168.0.142 : [Errno 110] Connection timed out
Listening 50999 port...
It look like it's trying to connect to and old server address from a previous install (2.1.0 I think).
I've tried uninstalling everything and removing the /opt/cgru folder but it still persists when reinstalling.
Which config file should I be looking for to get this fixed? Or is it a completely different issue?
I'm installing the cgru package on my workstation (Linux Mint 18.1) but can't get Keeper to start properly.
It works fine on my other machine and server (all running the same OS).
It tries to start and I get a black icon, and eventually the CGRU icon appears but doesn't respond and eventually just disappears again.
Here's the output it spits out in terminal:
CGRU_VERSION 2.2.1 : '/opt/cgru'
Certificate file "/opt/cgru/utilities/keeper/serverhttps.pem" not found, skipping HTTPS serving.
"sni-qt/6952" WARN 15:45:16.231 void StatusNotifierItemFactory::connectToSnw() Invalid interface to SNW_SERVICE
Could not open socket.
192.168.0.142 : [Errno 110] Connection timed out
Listening 50999 port...
It look like it's trying to connect to and old server address from a previous install (2.1.0 I think).
I've tried uninstalling everything and removing the /opt/cgru folder but it still persists when reinstalling.
Which config file should I be looking for to get this fixed? Or is it a completely different issue?