Cannot open WebODM

Sorry guys to bother you. I’m kind of a newbie to WebODM. I tried to open today and this is what I’m getting in the console;

Detected OS with VirtualBox support
Initializing console…
Error checking TLS connection: ssh command error:
command : ip addr show
err : exit status 255
output :
Docker is not communicating properly. We’ll attempt to establish communication…
NAME ACTIVE DRIVER STATE URL SWARM DOCKER ERRORS
webodm virtualbox Timeout
WebODM VM exists, attempting to launch it…
Starting “webodm”…
Machine “webodm” is already running.
Could not start virtual machine. Check the console for error messages and attempt to fix the problems manually, then restart this application.

Tried restarting WebODM Manager a couple of times and didn’t work. I’m downloading VirtualBox update as we speak. Should I update Virtual box?

Any help would be appreciated.

Mm, really odd. Did you try restarting your computer and restarting the VirtualBox “webodm” virtual machine manually (by opening the VirtualBox application)?

Also, not sure if it’s an option, but nuking the VM (which will lose your datasets) by using the “Delete VM” button from the maintenance panel could also help get it unstuck.

I tried the Delete VM function and was a no go either.
Here is what the console tells me;

Detected OS with VirtualBox support
Initializing console…
Docker machine “webodm” does not exist. Use “docker-machine ls” to list machines. Use “docker-machine create” to add a new one.
Docker is not communicating properly. We’ll attempt to establish communication…
NAME ACTIVE DRIVER STATE URL SWARM DOCKER ERRORS
WebODM VM does not exist. We’re going to create it now… hang on tight! If this takes more than 10 minutes, please try restarting your computer.
create --driver virtualbox --virtualbox-disk-size “451000” --virtualbox-memory “19584” --virtualbox-cpu-count “4” webodm
Running pre-create checks…
Creating machine…
(webodm) Copying D:\docker-webodm\cache\boot2docker.iso to D:\docker-webodm\machines\webodm\boot2docker.iso…
(webodm) Creating VirtualBox VM…
(webodm) Creating SSH key…
(webodm) Starting the VM…
(webodm) Check network to re-create if needed…
(webodm) Windows might ask for the permission to configure a dhcp server. Sometimes, such confirmation window is minimized in the taskbar.
(webodm) Waiting for an IP…
Error creating machine: Error in driver during machine creation: Too many retries waiting for SSH to be available. Last error: Maximum number of retries (60) exceeded
Uh oh! Check the console. Check that you have enough memory available, disk space, that your firewall is off and that you have restarted your computer. Refer to the troubleshooting section of the installation manual for more information.

I’m not sure what went wrong. I have used WebODM twice since installing it and after a couple of months I am trying to use it again and it’s not working?

Are you on Windows 10 Home by any chance?

Yes

I am experiencing the same issue. Curious to see if there are any ideas…

I’m having the same problem. “Too many retries waiting for SSH to be available. Last error: Maximum number of retries (60) exceeded”

I’ve seen several people having this issue recently (on Windows 10 Home), which makes me think it could be related to a Windows Update.

If you try the following:

  • Press Windows Key, type “Manage optional features” and press Enter.
  • From the panel, search for “OpenSSH Client”, click it and press “Uninstall”.
  • Start WebODM Manager.
  • If you still get the error, press the “Remove VM” button from the maintenance panel.

Does it work then? If it doesn’t please include your operating system version and a copy of the console log.

1 Like

Nailed it! Removed the update, rebooted for good measure, up and running again. Thanks a million, appreciate the help.

1 Like

Nice! @Hoogo did you end up removing the entire update or just the “OpenSSH Client” component?

1 Like

Only the openSSH client

1 Like

Thanks a lot, removing the openSSH client did the trick!
I really appreciate it!

2 Likes

Hi Piero, abusing your time: Are there any instructions on how to start using ODM w/out line commands, only from Windows environment?