[Windows] Stuck on "Waiting for IP..." when starting Local Machine

I have been talking to a rep but email is messing up. Flywheel will not start. It gets stuck trying to load. I am trying the command I am supposed to enter and it is not working either.

Eric,

Please let the following command run in Cmd.exe for at least 10 minutes before replying back. If it’s still stuck at “Waiting for IP…”, let me know.

C:\Users\Eric\AppData\Local\Programs\local-by-flywheel\resources\extraResources\virtual-machine\vendor\docker\windows\docker-machine.exe start local-by-flywheel 

That command is not working.

Did it get stuck on Waiting for IP…? If so, how long did you let Cmd.exe run that command?

Please help me help you by providing more details.

It says access denied

Eric,

Please provide a screenshot of what you’re seeing.

Again, unless you provide additional details and screenshots I cannot help you.

Ok so, I have done nothing different from earlier, absolutely nothing, but this time when I input the command it ran, however, I have now been waiting 15 minutes and it still says waiting for an IP. Please advise next course of action.

@SentietnRising,

Thanks for the screenshot!

Have you recently installed any type of anti-virus, internet security, VPN, or proxy?

I did recently install Malwarebytes and ran a scan. I keep forgetting to turn it off from start up. However, i closed that and and ran the command again, and same result as before.

@SentietnRising,

Just a heads up, I’m still looking into this.

In the meantime, can you try the following?

  1. Make sure all anti-virus, proxies, VPNs, internet security, etc. are disabled.
  2. Open Cmd.exe
  3. Run the following command. Make sure it finishes before moving to the next step.
C:\Users\Eric\AppData\Local\Programs\local-by-flywheel\resources\extraResources\virtual-machine\vendor\docker\windows\docker-machine.exe kill local-by-flywheel 
  1. Run the following command:
C:\Users\Eric\AppData\Local\Programs\local-by-flywheel\resources\extraResources\virtual-machine\vendor\docker\windows\docker-machine.exe start local-by-flywheel 
  1. Screenshot Cmd.exe like you did before

Any Luck? Do I just need to reformat my computer and reinstall?

I appreciate the screenshots and patience!

Can you run the following command so we can gather more data? I’ve been trying to reproduce the issue in my Windows VM but I’m not having much luck.

Once you run it, please screenshot it like you have been.

"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" showvminfo local-by-flywheel | FIND "NIC"

1 Like

Now we’re getting somewhere! It looks like the NAT network adapter isn’t attached to the virtual machine.

Please try the following:

  1. Open VirtualBox
  2. Right-click on local-by-flywheel and go to Close » Power Off
  3. Go to “Settings” for the local-by-flywheel VM. You can either click the Settings icon or right-click on it and click “Settings…”
  4. Go to Network » Adapter 1 and make sure that “Enable Network Adapter” is checked and that “Attached to:” is “NAT” like the following screenshot.
  5. Once you do that, try running the following command in Cmd.exe. Make sure you give it some time (at least 10 minutes) like before.
C:\Users\Eric\AppData\Local\Programs\local-by-flywheel\resources\extraResources\virtual-machine\vendor\docker\windows\docker-machine.exe start local-by-flywheel

I did what you said, it has been sitting like this for a while.

Anything yet?

Unfortunately not yet.

I will private message you here in the Community in a few minutes to discuss what we can do next.

I am having the same issues. I followed this process. And have the same results as SentietnRising. Clay, please let me know how this was resolved so that I can implement the fix.

Thanks

Roth