-
Notifications
You must be signed in to change notification settings - Fork 383
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
Couldn't connect to vSphere host #2003
Comments
hello, sorry we only officially support KVM, you will need to search the solution or wait till someone fix that for you. if you find solution and you want to help to others, you are more than welcome to make PR fix for this |
Set the logging to debug and try to add HTTP logging? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
About accounts on capesandbox.com
This is open source and you are getting free support so be friendly!
Prerequisites
Please answer the following questions for yourself before submitting an issue.
Expected Behavior
Use Cape V2 with Vsphere, the host and analysis VM on Vsphere
Current Behavior
Hello,
I'm writing about an issue I encountered while setting up Cape for usage with vSphere to manage analysis VMs and the host VM. Initially, I successfully tested Cape with VirtualBox, but later modified my configuration file to use vSphere without SSL certification (using a homemade certificate).
I've verified that my configuration is correct by separately testing the vSphere API with curl to ensure the parameters I provided were accurate. However, currently Cape is unable to connect to vSphere. The error message I received was:
[root] CRITICAL: CuckooCriticalError: Couldn't connect to vSphere host: [Errno 110] Connection timed out
To further diagnose the issue, I added a traceback to identify the source of the error, and encountered the following:
I'm confident that the parameters I've provided to connect to the vSphere host are correct. Additionally, my VM hosting CAPEv2 is capable of pinging vSphere and using the API with Curl.
The text was updated successfully, but these errors were encountered: