Regenerating Docker Machine TLS Certificates

We’re keeping an eye on this issue but there’s no one simple solution at the moment.

As soon as we know more, we’ll let you all know.


In the meantime, please try the following one at a time if you’re running into this:

  1. Go to Help » Restart Local’s Machine
  2. Try restarting your computer.
  3. Temporarily disable all anti-virus, anti-malware, or internet security and try again.

If you run into the issue after trying those steps one at a time, then please reply here with your local-by-flywheel.log file. Here are the instructions on how to retrieve it: How do I retrieve Local's log file?

This works for me on 2.1.2

1 Like

Hello guys,

I started to using local a few weeks ago.
Today, after I restarted the computer, the application has not starting and show this message:

“Local detected invalid docker machine tls certificates and is fixing them now”

And stay trying “regenerating docker machine tls certificates” and not start.

I already find many topics about this, tried but I not founded solution that works for me.
Im working in one project in the last 3 days and I cant lost information.

1 Like

I’m on macOS 10.13.4 and I’m having the same exact problem.

Shutting down the local machine on Virtualbox doesn’t solve a thing.

Any help, please? This is a huge issue for me right now.

@marcoalmeida,

Please provide your log file. Sorry for the trouble!

See “How do I retrieve Local’s log file?” for instructions on how to retrieve the log file.

Here’s a log for the same problem (MacOS 10.3.5)

Jul 11, 2018, 5:42 PM GMT+2 - info: [main/set-docker-env] Going to regen machine certs.
Jul 11, 2018, 5:42 PM GMT+2 - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Jul 11, 2018, 5:42 PM GMT+2 - warn: [main/index] Unhandled Rejection at: Promise Promise {
TypeError: Cannot read property ‘listImages’ of undefined
at _0x420ff5 (/Applications/Local by Flywheel.app/Contents/Resources/app.asar/main/actions-docker/check-for-flywheel-image.js:1:1235)
at Promise ()
at exports.default (/Applications/Local by Flywheel.app/Contents/Resources/app.asar/main/actions-docker/check-for-flywheel-image.js:1:1179)
at _dockerMachineFdv2.default.(anonymous function) (/Applications/Local by Flywheel.app/Contents/Resources/app.asar/main/actions-docker/docker-machine.js:1:6608)
at
at process._tickDomainCallback (internal/process/next_tick.js:135:7) } reason: TypeError: Cannot read property ‘listImages’ of undefined
at _0x420ff5 (/Applications/Local by Flywheel.app/Contents/Resources/app.asar/main/actions-docker/check-for-flywheel-image.js:1:1235)
at Promise ()
at exports.default (/Applications/Local by Flywheel.app/Contents/Resources/app.asar/main/actions-docker/check-for-flywheel-image.js:1:1179)
at _dockerMachineFdv2.default.(anonymous function) (/Applications/Local by Flywheel.app/Contents/Resources/app.asar/main/actions-docker/docker-machine.js:1:6608)
at
at process._tickDomainCallback (internal/process/next_tick.js:135:7)
Jul 11, 2018, 5:42 PM GMT+2 - warn: [main/docker-machine-fdv] Machine IP not available to check NFS mount
Jul 11, 2018, 5:42 PM GMT+2 - info: [main/docker-machine-fdv] unfsd already running
Jul 11, 2018, 5:43 PM GMT+2 - info: [main/index] Existing Pressmatic data does not exist.
Jul 11, 2018, 5:43 PM GMT+2 - info: [main/check-system] Check System: Docker Machine:
{ stdout: ‘Stopped\n’, stderr: ‘’ }
Jul 11, 2018, 5:43 PM GMT+2 - info: [renderer/CheckEnvPage] Check system promise response:
[ undefined, ‘machine-halted’ ]
Jul 11, 2018, 5:43 PM GMT+2 - info: [main/docker-machine] Checking Boot2Docker.iso hash
Jul 11, 2018, 5:43 PM GMT+2 - info: [main/docker-machine] Boot2Docker.iso hash does not match!
Jul 11, 2018, 5:43 PM GMT+2 - info: [main/docker-machine] Copying /Applications/Local by Flywheel.app/Contents/Resources/extraResources/virtual-machine/vendor/docker/boot2docker.iso to /Users/andy/.docker/machine/machines/local-by-flywheel/boot2docker.iso
Jul 11, 2018, 5:44 PM GMT+2 - info: [main/docker-machine] Running /Applications/Local by Flywheel.app/Contents/Resources/extraResources/virtual-machine/vendor/docker/osx/docker-machine start local-by-flywheel
Jul 11, 2018, 5:44 PM GMT+2 - info: [main/docker-machine] Starting “local-by-flywheel”…
Jul 11, 2018, 5:44 PM GMT+2 - info: [main/docker-machine] (local-by-flywheel) Check network to re-create if needed…
Jul 11, 2018, 5:44 PM GMT+2 - info: [main/docker-machine] (local-by-flywheel) Waiting for an IP…
Jul 11, 2018, 5:44 PM GMT+2 - info: [main/docker-machine] Machine “local-by-flywheel” was started.
Jul 11, 2018, 5:44 PM GMT+2 - info: [main/docker-machine] Waiting for SSH to be available…
Jul 11, 2018, 5:44 PM GMT+2 - info: [main/docker-machine] Detecting the provisioner…
Jul 11, 2018, 5:44 PM GMT+2 - info: [main/docker-machine] Started machines may have new IP addresses. You may need to re-run the docker-machine env command.
Jul 11, 2018, 5:44 PM GMT+2 - info: [main/set-docker-env] Getting Docker Machine env.
Jul 11, 2018, 5:44 PM GMT+2 - info: [main/set-docker-env] Received Docker Machine env.
Jul 11, 2018, 5:44 PM GMT+2 - warn: [main/set-docker-env] Error checking TLS connection: Error checking and/or regenerating the certs: There was an error validating certificates for host “192.168.95.100:2376”: x509: certificate has expired or is not yet valid
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.

Jul 11, 2018, 5:44 PM GMT+2 - info: [main/set-docker-env] Going to regen machine certs.
Jul 11, 2018, 5:44 PM GMT+2 - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Jul 11, 2018, 5:44 PM GMT+2 - warn: [main/index] Unhandled Rejection at: Promise Promise {
TypeError: Cannot read property ‘listImages’ of undefined
at _0x420ff5 (/Applications/Local by Flywheel.app/Contents/Resources/app.asar/main/actions-docker/check-for-flywheel-image.js:1:1235)
at Promise ()
at exports.default (/Applications/Local by Flywheel.app/Contents/Resources/app.asar/main/actions-docker/check-for-flywheel-image.js:1:1179)
at _dockerMachineFdv2.default.(anonymous function) (/Applications/Local by Flywheel.app/Contents/Resources/app.asar/main/actions-docker/docker-machine.js:1:6608)
at
at process._tickDomainCallback (internal/process/next_tick.js:135:7) } reason: TypeError: Cannot read property ‘listImages’ of undefined
at _0x420ff5 (/Applications/Local by Flywheel.app/Contents/Resources/app.asar/main/actions-docker/check-for-flywheel-image.js:1:1235)
at Promise ()
at exports.default (/Applications/Local by Flywheel.app/Contents/Resources/app.asar/main/actions-docker/check-for-flywheel-image.js:1:1179)
at _dockerMachineFdv2.default.(anonymous function) (/Applications/Local by Flywheel.app/Contents/Resources/app.asar/main/actions-docker/docker-machine.js:1:6608)
at
at process._tickDomainCallback (internal/process/next_tick.js:135:7)
Jul 11, 2018, 5:44 PM GMT+2 - warn: [main/docker-machine-fdv] Machine IP not available to check NFS mount
Jul 11, 2018, 5:44 PM GMT+2 - info: [main/docker-machine-fdv] unfsd already running
Jul 11, 2018, 5:44 PM GMT+2 - 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’,
stderr: ‘’ }
Jul 11, 2018, 5:44 PM GMT+2 - info: [main/set-docker-env] Getting Docker Machine env.
Jul 11, 2018, 5:44 PM GMT+2 - info: [main/set-docker-env] Received Docker Machine env.
Jul 11, 2018, 5:44 PM GMT+2 - warn: [main/set-docker-env] Error checking TLS connection: Error checking and/or regenerating the certs: There was an error validating certificates for host “192.168.95.100:2376”: x509: certificate has expired or is not yet valid
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.

Jul 11, 2018, 5:44 PM GMT+2 - info: [main/set-docker-env] Going to regen machine certs.
Jul 11, 2018, 5:44 PM GMT+2 - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Jul 11, 2018, 5:44 PM GMT+2 - 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’,
stderr: ‘’ }
Jul 11, 2018, 5:44 PM GMT+2 - info: [main/set-docker-env] Getting Docker Machine env.
Jul 11, 2018, 5:44 PM GMT+2 - info: [main/set-docker-env] Received Docker Machine env.
Jul 11, 2018, 5:44 PM GMT+2 - warn: [main/set-docker-env] Error checking TLS connection: Error checking and/or regenerating the certs: There was an error validating certificates for host “192.168.95.100:2376”: x509: certificate has expired or is not yet valid
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.

Jul 11, 2018, 5:44 PM GMT+2 - info: [main/set-docker-env] Going to regen machine certs.
Jul 11, 2018, 5:44 PM GMT+2 - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Jul 11, 2018, 5:44 PM GMT+2 - 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’,
stderr: ‘’ }
Jul 11, 2018, 5:44 PM GMT+2 - info: [main/set-docker-env] Getting Docker Machine env.
Jul 11, 2018, 5:44 PM GMT+2 - info: [main/set-docker-env] Received Docker Machine env.
Jul 11, 2018, 5:44 PM GMT+2 - warn: [main/set-docker-env] Error checking TLS connection: Error checking and/or regenerating the certs: There was an error validating certificates for host “192.168.95.100:2376”: x509: certificate has expired or is not yet valid
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.

Jul 11, 2018, 5:44 PM GMT+2 - info: [main/set-docker-env] Going to regen machine certs.
Jul 11, 2018, 5:44 PM GMT+2 - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Jul 11, 2018, 5:44 PM GMT+2 - 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’,
stderr: ‘’ }
Jul 11, 2018, 5:44 PM GMT+2 - info: [main/set-docker-env] Getting Docker Machine env.
Jul 11, 2018, 5:44 PM GMT+2 - info: [main/set-docker-env] Received Docker Machine env.
Jul 11, 2018, 5:44 PM GMT+2 - warn: [main/set-docker-env] Error checking TLS connection: Error checking and/or regenerating the certs: There was an error validating certificates for host “192.168.95.100:2376”: x509: certificate has expired or is not yet valid
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.

Jul 11, 2018, 5:44 PM GMT+2 - info: [main/set-docker-env] Going to regen machine certs.
Jul 11, 2018, 5:44 PM GMT+2 - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Jul 11, 2018, 5:45 PM GMT+2 - 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’,
stderr: ‘’ }
Jul 11, 2018, 5:45 PM GMT+2 - info: [main/set-docker-env] Getting Docker Machine env.
Jul 11, 2018, 5:45 PM GMT+2 - info: [main/set-docker-env] Received Docker Machine env.
Jul 11, 2018, 5:45 PM GMT+2 - warn: [main/set-docker-env] Error checking TLS connection: Error checking and/or regenerating the certs: There was an error validating certificates for host “192.168.95.100:2376”: x509: certificate has expired or is not yet valid
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.

Jul 11, 2018, 5:45 PM GMT+2 - info: [main/set-docker-env] Going to regen machine certs.
Jul 11, 2018, 5:45 PM GMT+2 - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Jul 11, 2018, 5:45 PM GMT+2 - 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’,
stderr: ‘’ }
Jul 11, 2018, 5:45 PM GMT+2 - info: [main/set-docker-env] Getting Docker Machine env.
Jul 11, 2018, 5:45 PM GMT+2 - info: [main/set-docker-env] Received Docker Machine env.
Jul 11, 2018, 5:45 PM GMT+2 - warn: [main/set-docker-env] Error checking TLS connection: Error checking and/or regenerating the certs: There was an error validating certificates for host “192.168.95.100:2376”: x509: certificate has expired or is not yet valid
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.

Jul 11, 2018, 5:45 PM GMT+2 - info: [main/set-docker-env] Going to regen machine certs.
Jul 11, 2018, 5:45 PM GMT+2 - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Jul 11, 2018, 5:45 PM GMT+2 - 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’,
stderr: ‘’ }
Jul 11, 2018, 5:45 PM GMT+2 - info: [main/set-docker-env] Getting Docker Machine env.
Jul 11, 2018, 5:45 PM GMT+2 - info: [main/set-docker-env] Received Docker Machine env.
Jul 11, 2018, 5:45 PM GMT+2 - warn: [main/set-docker-env] Error checking TLS connection: Error checking and/or regenerating the certs: There was an error validating certificates for host “192.168.95.100:2376”: x509: certificate has expired or is not yet valid
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.

Jul 11, 2018, 5:45 PM GMT+2 - info: [main/set-docker-env] Going to regen machine certs.
Jul 11, 2018, 5:45 PM GMT+2 - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Jul 11, 2018, 5:45 PM GMT+2 - 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’,
stderr: ‘’ }
Jul 11, 2018, 5:45 PM GMT+2 - info: [main/set-docker-env] Getting Docker Machine env.
Jul 11, 2018, 5:45 PM GMT+2 - info: [main/set-docker-env] Received Docker Machine env.
Jul 11, 2018, 5:45 PM GMT+2 - warn: [main/set-docker-env] Error checking TLS connection: Error checking and/or regenerating the certs: There was an error validating certificates for host “192.168.95.100:2376”: x509: certificate has expired or is not yet valid
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.

Jul 11, 2018, 5:45 PM GMT+2 - info: [main/set-docker-env] Going to regen machine certs.
Jul 11, 2018, 5:45 PM GMT+2 - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Jul 11, 2018, 5:45 PM GMT+2 - 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’,
stderr: ‘’ }
Jul 11, 2018, 5:45 PM GMT+2 - info: [main/set-docker-env] Getting Docker Machine env.
Jul 11, 2018, 5:45 PM GMT+2 - info: [main/set-docker-env] Received Docker Machine env.
Jul 11, 2018, 5:45 PM GMT+2 - warn: [main/set-docker-env] Error checking TLS connection: Error checking and/or regenerating the certs: There was an error validating certificates for host “192.168.95.100:2376”: x509: certificate has expired or is not yet valid
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.

Jul 11, 2018, 5:45 PM GMT+2 - info: [main/set-docker-env] Going to regen machine certs.
Jul 11, 2018, 5:45 PM GMT+2 - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Jul 11, 2018, 5:45 PM GMT+2 - 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’,
stderr: ‘’ }
Jul 11, 2018, 5:45 PM GMT+2 - info: [main/set-docker-env] Getting Docker Machine env.
Jul 11, 2018, 5:45 PM GMT+2 - info: [main/set-docker-env] Received Docker Machine env.
Jul 11, 2018, 5:45 PM GMT+2 - warn: [main/set-docker-env] Error checking TLS connection: Error checking and/or regenerating the certs: There was an error validating certificates for host “192.168.95.100:2376”: x509: certificate has expired or is not yet valid
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.

Jul 11, 2018, 5:45 PM GMT+2 - info: [main/set-docker-env] Going to regen machine certs.
Jul 11, 2018, 5:45 PM GMT+2 - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Jul 11, 2018, 5:45 PM GMT+2 - 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’,
stderr: ‘’ }
Jul 11, 2018, 5:45 PM GMT+2 - info: [main/set-docker-env] Getting Docker Machine env.
Jul 11, 2018, 5:45 PM GMT+2 - info: [main/set-docker-env] Received Docker Machine env.
Jul 11, 2018, 5:45 PM GMT+2 - warn: [main/set-docker-env] Error checking TLS connection: Error checking and/or regenerating the certs: There was an error validating certificates for host “192.168.95.100:2376”: x509: certificate has expired or is not yet valid
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.

Jul 11, 2018, 5:45 PM GMT+2 - info: [main/set-docker-env] Going to regen machine certs.
Jul 11, 2018, 5:45 PM GMT+2 - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.