-
-
Notifications
You must be signed in to change notification settings - Fork 994
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
Can't access Velociraptor #903
Comments
[*] Verifying that Velociraptor is reachable... Could someone have a look at the logger vm ? I tried to redownload it but the issue persisted |
velociraptor-v0.7.0 100%[===================>] 52.43M 4.29MB/s in 12s |
It's not being managed anymore. :\ not sure where you are running it on. Logger isn't loading splunk or velociraptor either for me right now. I re-ran ansible playbook and got guacamole to load correctly. You may want to re-provision the host. Got splunk up. Otherwise, we probably need to look in the logger_bootstrap.sh for something that's wrong/old. And I found it I installed in manually, but, I think if you look at this log in the bootstrap script, the wildcards in the wrong place. Its in the wrong place in the Velociraptor documents too. Unless I am messed up? logger: dpkg: error: cannot access archive 'velociraptor_*_server.deb': No such file or directory It should be like 'velociraptor_server_*_amd64.deb' https://docs.velociraptor.app/docs/deployment/self-signed/ Yes, the cert is expired. There are instructions at https://docs.velociraptor.app/docs/deployment/troubleshooting/ Attached is a new server.config. Remove the .txt extension and place is in your DetectionLab/Vagrant/resources/velociraptor path Attached is an updated logger_bootstrap.sh. Remove the .txt extension and place it in DetectionLab/Vagrant path |
Get a Connection Refused error when trying to get into Velociraptor portal. No problem getting into Splunk or Fleet. I'm using http://:9999
The text was updated successfully, but these errors were encountered: