09-13-2021 11:24 AM
I have the integration enabled and configured using the requirements stated in the Marketplace, but when I try to load the dashboard it says I don't have the SSH integration enabled. But I do, and I have a local user and have tested it manually, so I don't think this is credential related. It just looks like the integration is not able to access SSH on localhost. The SSH integration test function passes too.
Has anyone else experienced this with this integration/dashboard?
Jeff
09-13-2021 08:16 PM - edited 09-13-2021 08:18 PM
First make sure the integration works with a test command in the playground, in my testing the test button wasn't always accurate for the RemoteAccess integration (try without a username/password and it'll say success but fail with commands).
This was my test command in the playground:
!ssh cmd=hostname using=localhost
The next thing to check is to make sure you named your instance `localhost`. The automation is hardcoded with that value for the instance name. The test example above also uses `localhost` so if that fails, the instance name could be the cause. See: https://github.com/demisto/content/blob/d4a6fdd9e50a35e5218bcce7e40d87c95c7ff6c0/Packs/ServerLogs/Sc...
If that's all correct, then check the user you're using for the RemoteAccess instance has read access to the log files in the automations. These are their paths (also hardcoded):
/var/log/demisto/server.log
/var/log/demisto/docker.log
Check with an `ls -a $PATH` while on the host.
09-13-2021 11:30 AM
Script failed to run:
Error: [Traceback (most recent call last):
File "<string>", line 4, in <module>
File "<string>", line 82, in executeCommand
File "<string>", line 137, in __do
ValueError: Unsupported Command : ssh , verify you have proper integration enabled to support it (23)
] (2604) (2603)09-13-2021 08:16 PM - edited 09-13-2021 08:18 PM
First make sure the integration works with a test command in the playground, in my testing the test button wasn't always accurate for the RemoteAccess integration (try without a username/password and it'll say success but fail with commands).
This was my test command in the playground:
!ssh cmd=hostname using=localhost
The next thing to check is to make sure you named your instance `localhost`. The automation is hardcoded with that value for the instance name. The test example above also uses `localhost` so if that fails, the instance name could be the cause. See: https://github.com/demisto/content/blob/d4a6fdd9e50a35e5218bcce7e40d87c95c7ff6c0/Packs/ServerLogs/Sc...
If that's all correct, then check the user you're using for the RemoteAccess instance has read access to the log files in the automations. These are their paths (also hardcoded):
/var/log/demisto/server.log
/var/log/demisto/docker.log
Check with an `ls -a $PATH` while on the host.
10-04-2021 12:33 PM
Boom! That was the ticket. Setting the hostname and instance name to localhost resolved this for me.
Thank-you!!
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!
