Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Linux client v8 : No activity/timelines running #315

Closed
vramULB opened this issue Apr 11, 2024 · 4 comments
Closed

Linux client v8 : No activity/timelines running #315

vramULB opened this issue Apr 11, 2024 · 4 comments

Comments

@vramULB
Copy link

vramULB commented Apr 11, 2024

Hello !
I'm new using this project and actually I see there is new version 8.0.0
I tried to deploy a client agent in a Ubuntu VM using Ansible but I had some problems running the timeline.
I don't really know why no activity is performed but in the previous version 7 I had no problem with this geckodriver.

Can you please check if I did something wrong?

My configuration :

  • Ubuntu 20.04
  • DotNet: v 8.0.204
  • Firefox: v 124.0.2
  • Geckodriver : v0.34.0-linux64 (put in the same folder than ghosts client folder and I tried also with linux 32b)
  • Ghosts API : 8.0.0.0 (8.0.8.202) from lastest Docker-compose file
  • Ghosts client : 8.0.0 (downloaded from Ghost API /install/client/linux)

Logs from Ghosts API :
image

Logs from linux client:
image

logs/app.logs
image

application.json (I only change the API URL)
image

timeline.json (I add a new activity but with only the default activity BroserFirefox it doesn't work)
image

@sei-dupdyke
Copy link
Contributor

Hmm, i will have to look into this. There was a problem with amd/arm compiles, but this is not that. Standby please.

@sei-dupdyke
Copy link
Contributor

Very sorry, found some blocking bugs that occur when you are not connected to the api. That's my bad. There is a fixed new binary out there for v8. Sorry for the inconvenience.

@vramULB
Copy link
Author

vramULB commented Apr 17, 2024

Hi, thanks for the changes!
What are you talking about when you say that I'm not connected to the API?
I thought I was connected in when I changed the ApiRootUrl to the the VM that contains the API and launched the client. If not, how do I get connected by default?

Otherwise, I downloaded the last linux client release from and now it works better using BrowseFirefox and Command(mkdir).
Thank you

@sei-dupdyke
Copy link
Contributor

Disregard those comments, sorry, you are connected in your logs screen shot. Glad it is working now!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants