Checking System / Regenerating Docker Machine TLS Certificates

This is my second attempt to get Local by Flywheel to work. I tried a week ago and encountered the same issues. Upon startup it will get stuck in a continuous loop of “Checking System / Regenerating Docker Machine TLS Certificates.”

After the first install, I uninstalled it but then I look at all the people using this out there without any issues. I just had to try again. The same exact thing. It works perfectly fine on the first day of install. Now today after computer was shut down last night, it goes back to the dreaded loop.

I’ve copied a few entries from my log file:

Jan 8, 2019, 11:58 AM CST - error: [main/index]
{ message: ‘Cannot read property 'trim' of undefined’,
'TypeError: Cannot read property 'trim' of undefined\n at Function.add (C:\Users\Mike\AppData\Local\Programs\local-by-flywheel\resources\app.asar\main\actions-docker\proxy-manager.js:1:4107)\n at Object.(anonymous function)._0x495449 (C:\Users\Mike\AppData\Local\Programs\local-by-flywheel\resources\app.asar\main\actions-docker\docker-machine.js:1:10589)\n at Array.forEach ()\n at _child_process2.(anonymous function).(anonymous function) (C:\Users\Mike\AppData\Local\Programs\local-by-flywheel\resources\app.asar\main\actions-docker\docker-machine.js:1:10491)\n at ChildProcess.exithandler (child_process.js:294:7)\n at ChildProcess.emit (events.js:182:13)\n at ChildProcess.EventEmitter.emit (domain.js:442:20)\n at maybeClose (internal/child_process.js:961:16)\n at Process.ChildProcess._handle.onexit (internal/child_process.js:248:5)’ }

Jan 8, 2019, 11:58 AM CST - warn: [main/set-docker-env] Error checking TLS connection: Error checking and/or regenerating the certs: There was an error validating certificates for host “”: dial tcp i/o timeout
You can attempt to regenerate them using ‘docker-machine regenerate-certs [name]’.
Be advised that this will trigger a Docker daemon restart which might stop running containers.

Jan 8, 2019, 11:58 AM CST - info: **[renderer/RegenMachineCertsPage] Regenerate machine cert response. **
> { error: null,
> stdout:
> 'Regenerating TLS certificates\nWaiting for SSH to be available…\nDetecting the provisioner…\nCopying certs to the local machine directory…\nCopying certs to the remote machine…\nSetting Docker configuration on the remote daemon…\n\nThis machine has been allocated an IP address, but Docker Machine could not\nreach it successfully.\n\nSSH for the machine should still work, but connecting to exposed ports, such as\nthe Docker daemon port (usually :2376), may not work properly.\n\nYou may need to add the route manually, or use another related workaround.\n\nThis could be due to a VPN, proxy, or host file configuration issue.\n\nYou also might want to clear any VirtualBox host only interfaces you are not using.\n’,
stderr: ‘’ }

I wanted to say that I found a solution in the forums that seemed to work for me on macOS.