-
Notifications
You must be signed in to change notification settings - Fork 30
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
cuckoo unable to bind resultserver #8
Comments
Hello @securecars66 . please check ".cuckoo/conf/cuckoo.conf" file for more information please read the README.md file |
Thanks. I did that and it appears it still doesn't start correctly. The IP 192.168.56.1 is not the IP. |
I traced that exact error location at the code(cuckoo\core\resultserver.py). It is printing your error among with the IP as configured in cuckoo.conf. If there's still an error, then try searching the string '192.168.56.1' in cuckoo's directory so we will know where this configuration is coming from. |
We are closing this issue, if the error reoccurs then please open a new issue. |
Hi guys! |
Thanks for creating an issue! But first: did you read our community guidelines?
https://cuckoo.sh/docs/introduction/community.html
My issue is:
unable to start cuckoo because of error
My Cuckoo version and operating system are:
Distributor ID:Ubuntu
Description:Ubuntu 18.04.2 LTS
Release:18.04
Codename:bionic
This can be reproduced by:
trying to start cuckoo in AWS on ubuntu after following these instructions
The log, error, files etc can be found at:
ERROR I GET:
CuckooCriticalError: Unable to bind ResultServer on 192.168.56.1:2042 [Errno 99] Cannot a
ssign requested address. This usually happens when you start Cuckoo without bringing up the virtual interface associated with the Re
sultServer IP address. Please refer to https://cuckoo.sh/docs/faq/#troubles-problem for more information.
Please help
The text was updated successfully, but these errors were encountered: