When a user tries to start Keeper Service mode in the Background, the service doesn't seem to run.
However, it does seem to work in the foreground. Is this a known issue?
Steps to replicate:
-
Access Keeper commander and login (Persistent).
-
Then created a service:
My Vault> service-create
Enter Port No:8080
Enable Ngrok Tunneling? (y/n):n
Enable Cloudflare Tunneling? (y/n):n
Enable TLS Certificate? (y/n):n
Enable Request Queue? (y/n):n
Enable Advanced Security? (y/n):n
Select run mode (foreground/background):background
List of supported commands, Enter comma separated:whoami
Generated API key: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX=
Uploading service_config.json ...
Commander Service starting on http://localhost:8080/api/v1/
Commander Service started with PID: 3876
-
Run service status command and see that the service is stopped:
My Vault> service-status
Current status: Commander Service is Stopped
-
Verify Task manager and look for the PID, there is no service running.
When a user tries to start Keeper Service mode in the Background, the service doesn't seem to run.
However, it does seem to work in the foreground. Is this a known issue?
Steps to replicate:
Access Keeper commander and login (Persistent).
Then created a service:
My Vault> service-create
Enter Port No:8080
Enable Ngrok Tunneling? (y/n):n
Enable Cloudflare Tunneling? (y/n):n
Enable TLS Certificate? (y/n):n
Enable Request Queue? (y/n):n
Enable Advanced Security? (y/n):n
Select run mode (foreground/background):background
List of supported commands, Enter comma separated:whoami
Generated API key: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX=
Uploading service_config.json ...
Commander Service starting on http://localhost:8080/api/v1/
Commander Service started with PID: 3876
Run service status command and see that the service is stopped:
My Vault> service-status
Current status: Commander Service is Stopped
Verify Task manager and look for the PID, there is no service running.