After upgrade (2.0.2 MAC) Local Doesn't initialize

What version of VirtualBox do we need for this to work?

Unfortunately I don’t have a particular version number to give you but I do know there were some networking problems in the past that have been solved by updating VirtualBox.

OK thx - downloading latest now.

Hi @clay,

I downloaded local 2.0.2 and got stuck on “starting local machine”. Did a “headless start” of vistualbox and Local could successfully start. I then started one of my sites and got “Local Router Error” trying to access the site in browser. I tried another site, tried restart local, tried reset the vm, tried changing web server (btw, got stuck on “provisioning nginx” when switched from Apache to Nginx) and same “Local router error” happened.

Is there anything I can try to fix the local router error?

Thanks for help.

Virtualbox version: 5.1.22 r115126 (Qt5.6.2)
Local log file: local-by-flywheel.log (17.3 KB)

Wanted to jump in and say that I encountered the same issue today. Ended up deleting the virtual machine hoping that it would create a new one and import my sites the way that VVV and Vagrant used to. My sites show up in Local but they all say “Error! Container is missing. You will need to restore this site from a backup or previous export.” Is there any way to easily re-import all of these dead sites?

1 Like

I had this issue. I think it was because I used Pressmatic before, and when I deleted the machine.json file that Clay suggested, it no longer knows to look for pressmatic instead of local-by-flywheel. If you add that file back, it fixed it for me.

Unzip and add to ~/Library/Application Support/Local by Flywheel.

machine.json.zip (203 Bytes)

1 Like

For me, the problem persist!

Going back to 2.0.1 and Waiting next version to solve this issue!

My Local log file shows:

Jun 3, 2017, 2:32 PM PDT - info: [main/docker-machine] Starting “local-by-flywheel”…
Jun 3, 2017, 2:33 PM PDT - info: [main/docker-machine] (local-by-flywheel) Check network to re-create if needed…
Jun 3, 2017, 2:33 PM PDT - info: [main/docker-machine] (local-by-flywheel) Waiting for an IP…
Jun 3, 2017, 2:33 PM PDT - info: [main/docker-machine] Machine “local-by-flywheel” was started.
Jun 3, 2017, 2:33 PM PDT - info: [main/docker-machine] Waiting for SSH to be available…
Jun 3, 2017, 2:33 PM PDT - info: [main/docker-machine] Detecting the provisioner…
Jun 3, 2017, 2:33 PM PDT - info: [main/docker-machine] Started machines may have new IP addresses. You may need to re-run the docker-machine env command.

I was running Local 2.0.0
I created the Local Doesn’t Initialize problem by downloading Local 2.0.2, then installed it by overwriting the older vision just like a lot of Mac Apps do their updates.
The problem is this caused the Local Doesn’t initialize problem.

Restarting the local machine did not solve the problem.
Thinking it may be a Virtual Box dependency problem, I upgraded to Virtual Box 5.1.22. This did not solve the problem.

I reinstalled Local 2.0.1.
Local. 2.0.1 works.
However Local 2.0.1 pestered me about a major upgrade (e.g. Local 2.0.2).
I updated Local within the app.
It restarted
Local 2.0.2 worked!

But on restarting Local 2.0.2, again the Local Doesn’t initialize problem returned. Arggg.

Here is the Log File after restarting Local and getting stuck:

Jun 3, 2017, 3:23 PM PDT - info: [main/index] Existing Pressmatic data does not exist.
Jun 3, 2017, 3:23 PM PDT - info: [main/check-system] Check System: Docker Machine:
{ stdout: ‘Stopped\n’, stderr: ‘’ }
Jun 3, 2017, 3:23 PM PDT - info: [renderer/CheckEnvPage] Check system promise response: [ undefined, ‘machine-halted’ ] machine-halted
Jun 3, 2017, 3:23 PM PDT - info: [main/docker-machine] Checking Boot2Docker.iso hash
Jun 3, 2017, 3:23 PM PDT - info: [main/docker-machine] Running /Applications/Local by Flywheel.app/Contents/Resources/extraResources/virtual-machine/vendor/docker/osx/docker-machine start local-by-flywheel
Jun 3, 2017, 3:23 PM PDT - info: [main/docker-machine] Starting “local-by-flywheel”…
Jun 3, 2017, 3:23 PM PDT - info: [main/docker-machine] (local-by-flywheel) Check network to re-create if needed…
Jun 3, 2017, 3:23 PM PDT - info: [main/docker-machine] (local-by-flywheel) Waiting for an IP…
Jun 3, 2017, 3:24 PM PDT - info: [main/docker-machine] Machine “local-by-flywheel” was started.
Jun 3, 2017, 3:24 PM PDT - info: [main/docker-machine] Waiting for SSH to be available…
Jun 3, 2017, 3:24 PM PDT - info: [main/docker-machine] Detecting the provisioner…
Jun 3, 2017, 3:24 PM PDT - info: [main/docker-machine] Started machines may have new IP addresses. You may need to re-run the docker-machine env command.

Hopefully there is a fix. It seems Local is highly dependent on 3rd party apps like Docker which somehow aren’t working with this new update.

So I am downgrading to Local 2.0.1. This version seems to work.

Here are the Local 2.0.1 Log File contents. Interestingly, it has some of the same error messages as with Local 2.0.2. But it runs past the error message “Started machines may have new IP addresses. You may need to re-run the docker-machine env command.”

Jun 3, 2017, 3:37 PM PDT - info: [main/index] Existing Pressmatic data does not exist.
Jun 3, 2017, 3:37 PM PDT - info: [main/check-system] Check System: Docker Machine:
{ stdout: ‘Stopped\n’, stderr: ‘’ }
Jun 3, 2017, 3:37 PM PDT - info: [renderer/CheckEnvPage] Check system promise response: [ undefined, ‘machine-halted’ ] machine-halted
Jun 3, 2017, 3:37 PM PDT - info: [main/docker-machine] Checking Boot2Docker.iso hash
Jun 3, 2017, 3:37 PM PDT - info: [main/docker-machine] Running /Applications/Local by Flywheel.app/Contents/Resources/extraResources/virtual-machine/vendor/docker/osx/docker-machine start local-by-flywheel
Jun 3, 2017, 3:37 PM PDT - info: [main/docker-machine] Starting “local-by-flywheel”…
Jun 3, 2017, 3:37 PM PDT - info: [main/docker-machine] (local-by-flywheel) Check network to re-create if needed…
Jun 3, 2017, 3:37 PM PDT - info: [main/docker-machine] (local-by-flywheel) Waiting for an IP…
Jun 3, 2017, 3:37 PM PDT - info: [main/docker-machine] Machine “local-by-flywheel” was started.
Jun 3, 2017, 3:37 PM PDT - info: [main/docker-machine] Waiting for SSH to be available…
Jun 3, 2017, 3:37 PM PDT - info: [main/docker-machine] Detecting the provisioner…
Jun 3, 2017, 3:37 PM PDT - info: [main/docker-machine] Started machines may have new IP addresses. You may need to re-run the docker-machine env command.
Jun 3, 2017, 3:37 PM PDT - info: [main/set-docker-env] Getting Docker Machine env.
Jun 3, 2017, 3:37 PM PDT - info: [main/docker-machine-nfs] NFS Mount Status
{ error: null,
stdout: ‘192.168.75.1:/Users on /Users type nfs (rw,relatime,vers=3,rsize=65536,wsize=65536,namlen=255,acregmin=1,acregmax=1,acdirmin=1,acdirmax=1,hard,nolock,proto=tcp,port=2049,timeo=70,retrans=3,sec=sys,local_lock=all,addr=192.168.75.1)\n’,
stderr: ‘’ }
Jun 3, 2017, 3:37 PM PDT - info: [main/set-docker-env] Received Docker Machine env.
Jun 3, 2017, 3:37 PM PDT - info: [main/docker-machine] checking IP
Jun 3, 2017, 3:37 PM PDT - info: [main/set-docker-env] Getting Docker Machine env.
Jun 3, 2017, 3:37 PM PDT - info: [main/docker-machine] checked IP 192.168.75.100

Jun 3, 2017, 3:37 PM PDT - info: [main/set-docker-env] Received Docker Machine env.
Jun 3, 2017, 3:38 PM PDT - info: [main/startSite] Refreshing NFS mounts
Jun 3, 2017, 3:38 PM PDT - info: [main/waitForFile] Waiting for /conf/php/7.0.3/etc/php-fpm.conf 281f0b05922c641e1fe7548e0d31f9105928e46dc587de231c973e58bb3f072a
Jun 3, 2017, 3:38 PM PDT - info: [main/docker-router] updateProxyManager()
Jun 3, 2017, 3:38 PM PDT - info: [main/docker-network-manager] maybeCreateNetwork
Jun 3, 2017, 3:38 PM PDT - info: [main/docker-router] getRouterContainer()
Jun 3, 2017, 3:38 PM PDT - info: [main/docker-router] reconnectNetwork()
Jun 3, 2017, 3:38 PM PDT - info: [main/docker-network-manager] doesNetworkExist
Jun 3, 2017, 3:38 PM PDT - info: [main/docker-router] runContainer()
Jun 3, 2017, 3:38 PM PDT - info: [main/docker-network-manager] Network exists.
Jun 3, 2017, 3:38 PM PDT - info: [main/waitForFile] /conf/php/7.0.3/etc/php-fpm.conf exists
Jun 3, 2017, 3:38 PM PDT - info: [main/docker-network-manager] Connected 281f0b05922c641e1fe7548e0d31f9105928e46dc587de231c973e58bb3f072a.

There is no RESET option because your local-by-flywheel virtual machine is not running.
Start it up then the RESET option will be present.

This was disastrous for me.

Adding the machine.json to the ~/Library/Application Support/Local by Flywheel caused Local 2.0.2 to restart it’s installation process.

During the installation process it got stuck - while using up 12% CPU time.

I quit the installation. Luckily it did so gracefully, including stopping the virtual machine.

I reinstalled Local 2.0.1 by overwriting Local 2.0.2 with it. And Local works again.

I am concerned about Local 2.0.1 since the Log file has a lot of error codes. I don’t know how this will affect the stability of a website I am developing.

Here is the content of the log file:

Jun 3, 2017, 10:57 PM PDT - info: [main/index] Existing Pressmatic data does not exist.
Jun 3, 2017, 10:57 PM PDT - info: [main/check-system] Check System: Docker Machine:
{ stdout: ‘Stopped\n’, stderr: ‘’ }
Jun 3, 2017, 10:57 PM PDT - info: [renderer/CheckEnvPage] Check system promise response: [ undefined, ‘machine-halted’ ] machine-halted
Jun 3, 2017, 10:57 PM PDT - info: [main/docker-machine] Checking Boot2Docker.iso hash
Jun 3, 2017, 10:57 PM PDT - info: [main/docker-machine] Running /Applications/Local by Flywheel.app/Contents/Resources/extraResources/virtual-machine/vendor/docker/osx/docker-machine start local-by-flywheel
Jun 3, 2017, 10:57 PM PDT - info: [main/docker-machine] Starting “local-by-flywheel”…
Jun 3, 2017, 10:57 PM PDT - info: [main/docker-machine] (local-by-flywheel) Check network to re-create if needed…
Jun 3, 2017, 10:57 PM PDT - info: [main/docker-machine] (local-by-flywheel) Waiting for an IP…
Jun 3, 2017, 10:58 PM PDT - info: [main/docker-machine] Machine “local-by-flywheel” was started.
Jun 3, 2017, 10:58 PM PDT - info: [main/docker-machine] Waiting for SSH to be available…
Jun 3, 2017, 10:58 PM PDT - info: [main/docker-machine] Detecting the provisioner…
Jun 3, 2017, 10:58 PM PDT - info: [main/docker-machine] Started machines may have new IP addresses. You may need to re-run the docker-machine env command.
Jun 3, 2017, 10:58 PM PDT - info: [main/docker-machine-nfs] NFS Mount Status
{ error: null,
stdout: ‘192.168.75.1:/Users on /Users type nfs (rw,relatime,vers=3,rsize=65536,wsize=65536,namlen=255,acregmin=1,acregmax=1,acdirmin=1,acdirmax=1,hard,nolock,proto=tcp,port=2049,timeo=70,retrans=3,sec=sys,local_lock=all,addr=192.168.75.1)\n’,
stderr: ‘’ }
Jun 3, 2017, 10:58 PM PDT - info: [main/set-docker-env] Getting Docker Machine env.
Jun 3, 2017, 10:58 PM PDT - info: [main/set-docker-env] Received Docker Machine env.
Jun 3, 2017, 10:58 PM PDT - info: [main/docker-machine] checking IP
Jun 3, 2017, 10:58 PM PDT - info: [main/set-docker-env] Getting Docker Machine env.
Jun 3, 2017, 10:58 PM PDT - info: [main/docker-machine] checked IP 192.168.75.100

Jun 3, 2017, 10:58 PM PDT - info: [main/set-docker-env] Received Docker Machine env.
Jun 3, 2017, 10:58 PM PDT - info: [main/startSite] Refreshing NFS mounts
Jun 3, 2017, 10:58 PM PDT - info: [main/waitForFile] Waiting for /conf/php/7.0.3/etc/php-fpm.conf 281f0b05922c641e1fe7548e0d31f9105928e46dc587de231c973e58bb3f072a
Jun 3, 2017, 10:58 PM PDT - info: [main/docker-router] updateProxyManager()
Jun 3, 2017, 10:58 PM PDT - info: [main/docker-network-manager] maybeCreateNetwork
Jun 3, 2017, 10:58 PM PDT - info: [main/docker-router] getRouterContainer()
Jun 3, 2017, 10:58 PM PDT - info: [main/docker-router] reconnectNetwork()
Jun 3, 2017, 10:58 PM PDT - info: [main/docker-network-manager] doesNetworkExist
Jun 3, 2017, 10:58 PM PDT - info: [main/docker-router] runContainer()
Jun 3, 2017, 10:58 PM PDT - info: [main/docker-network-manager] Network exists.
Jun 3, 2017, 10:58 PM PDT - info: [main/waitForFile] /conf/php/7.0.3/etc/php-fpm.conf exists

I’m having this issue as well, from a new install of 2.02 (not updating).

-I tried updating VirtualBox to Version 5.1.22 r115126 (Qt5.6.2);
-I’ve clicked ‘Reset’ while running and tried re-opening local.
-I’ve tried doing a headless start after quitting Local multiple times [does it matter how you Power Off vs Shut Down the local-by-flywheel in VirtualBox between headless starts? I’ve tried both ways…]

It can’t get past ‘checking system’, and from the Log file, every launch attempt it throws these 3 messages:
Jun 5, 2017, 7:46 AM GMT+9 - info: [main/set-docker-env] Getting Docker Machine env.
Jun 5, 2017, 7:46 AM GMT+9 - info: [main/set-docker-env] Received Docker Machine env.
Jun 5, 2017, 7:49 AM GMT+9 - info: [main/index] Existing Pressmatic data does not exist.

I’m fairly sure I shouldn’t have had any existing Pressmatic data, as I wasn’t a prior user. Any suggestions about this?

I saw @zackkatz 's suggestion about adding back some machine.json file but got scared off by the reply that doing so was disastrous for someone else.

Or, it seems like using version 2.01 is working… where can I download that? And do I have to do anything special to uninstall 2.02 or do anything to VirtualBox if I switch Local versions?

local-by-flywheel.log (26.7 KB)

Thanks!

Agreed with the above. I’m seeing exactly the same problems and I have only just started using Flywheel Local. I was not previously a Pressmatic user.

If anyone is having this issue please update to 2.0.3:

https://local.getflywheel.com/community/t/local-by-flywheel-2-0-3-macos-only/1721

Awesome! Was finally able to launch Flywheel with this 2.03. Didn’t have to do any of the headless start or anything. Just double clicked. Thank you!

1 Like

Good morning Clay! I’ve tried updating Local by Flywheel, updating Virtual Box, and deleting the incomplete installation of a new site, which seemed to cause this destruction; and I still do not have my site back. I’m getting a different message this time, though. I’m getting a Problem loading page error, “Unable to connect. Firefox can’t establish a connection to the server at cfecommerce.dev.”

I think I replied to the wrong comment thread. I spent hours in the forum yesterday trying to find a solution that will get my site back up and running. Monday, I tried adding a new site. It took several hours and never completed. I gave up and shut my computer down. Next morning, I got a Local Router Error when I tried to open the site I’ve been working on for weeks. I tried all the solutions I mentioned in my previous reply and now I’m getting a Problem Loading Page error message.

@marianco expressed concern about all the error codes in the log affecting the integrity of the website he is building. What is your feeling about this?