PLEASE HELP! Stuck between Regenerating Docking Machine TLS Certificate and Checking System

Support
1

Hi,

So I had about a month break from building my site. When I tried to open local by flywheel it would not open.

I read through some problems on here and noticed my Virtual Box was out of date. I then updated VB and then right clicked and selected Reset. (VB reset), then I tired to open Local by fly wheel again and nothing. I reset my Mac and still nothing.

I then reset local machine in local by fly wheel which took me to an upgrade page. But while it was trying to upgrade I read that some sites got deleted from doing this, so I cancelled.

Now it is stuck between Regenerating Docking Machine TLS Certificate and Checking System.

Please see below log details:

Aug 9, 2017, 9:30 AM GMT+1 - info: [main/set-docker-env] Going to regen machine certs.
Aug 9, 2017, 9:30 AM GMT+1 - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Aug 9, 2017, 9:31 AM GMT+1 - 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 <ip>: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: '' }
Aug 9, 2017, 9:31 AM GMT+1 - info: [main/set-docker-env] Getting Docker Machine env.
Aug 9, 2017, 9:31 AM GMT+1 - info: [main/set-docker-env] Received Docker Machine env.
Aug 9, 2017, 9:31 AM GMT+1 - warn: [main/set-docker-env] Error checking TLS connection: Error checking and/or regenerating the certs: There was an error validating certificates for host "172.18.0.1:2376": dial tcp 172.18.0.1:2376: getsockopt: connection refused
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.


Aug 9, 2017, 9:31 AM GMT+1 - info: [main/set-docker-env] Going to regen machine certs.
Aug 9, 2017, 9:31 AM GMT+1 - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Aug 9, 2017, 9:31 AM GMT+1 - 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 <ip>: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: '' }
Aug 9, 2017, 9:31 AM GMT+1 - info: [main/set-docker-env] Getting Docker Machine env.
Aug 9, 2017, 9:31 AM GMT+1 - info: [main/set-docker-env] Received Docker Machine env.
Aug 9, 2017, 9:31 AM GMT+1 - warn: [main/set-docker-env] Error checking TLS connection: Error checking and/or regenerating the certs: There was an error validating certificates for host "172.18.0.1:2376": dial tcp 172.18.0.1:2376: getsockopt: connection refused
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.


Aug 9, 2017, 9:31 AM GMT+1 - info: [main/set-docker-env] Going to regen machine certs.
Aug 9, 2017, 9:31 AM GMT+1 - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Aug 9, 2017, 9:31 AM GMT+1 - 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 <ip>: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: '' }
Aug 9, 2017, 9:31 AM GMT+1 - info: [main/set-docker-env] Getting Docker Machine env.
Aug 9, 2017, 9:31 AM GMT+1 - info: [main/set-docker-env] Received Docker Machine env.
Aug 9, 2017, 9:31 AM GMT+1 - warn: [main/set-docker-env] Error checking TLS connection: Error checking and/or regenerating the certs: There was an error validating certificates for host "172.18.0.1:2376": dial tcp 172.18.0.1:2376: getsockopt: connection refused
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.


Aug 9, 2017, 9:31 AM GMT+1 - info: [main/set-docker-env] Going to regen machine certs.
Aug 9, 2017, 9:31 AM GMT+1 - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Aug 9, 2017, 9:31 AM GMT+1 - 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 <ip>: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: '' }
Aug 9, 2017, 9:31 AM GMT+1 - info: [main/set-docker-env] Getting Docker Machine env.
Aug 9, 2017, 9:31 AM GMT+1 - info: [main/set-docker-env] Received Docker Machine env.
Aug 9, 2017, 9:31 AM GMT+1 - info: [renderer/RegenMachineCertsPage] Regenerating Machine Certificates.
Aug 9, 2017, 9:31 AM GMT+1 - warn: [main/set-docker-env] Error checking TLS connection: Error checking and/or regenerating the certs: There was an error validating certificates for host "172.18.0.1:2376": dial tcp 172.18.0.1:2376: getsockopt: connection refused
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.


Aug 9, 2017, 9:31 AM GMT+1 - info: [main/set-docker-env] Going to regen machine certs.
2

Richard,

Sorry for the trouble!

Can you please try the following?

  1. Quit Local if it’s open
  2. Open VirtualBox
  3. Right-click on “local-by-flywheel” and go to Close » Power Off
  4. Re-open Local
1 Like
3

Hi Richard,
Thank you for this explanation which works fine…
I recover my websites…

I try to create a third website wherethe internet connexion was not good.
Do you think it is the source of this pb?

On W7 x64 4 Mo RAM…

Thank you for your time and this amazing application.

4

Hi again,

In fact, this comes from with a recent (small) issue :slight_smile:

When I want to close W7,
W7 says he has a “he has still an open connection”.
I am obliged to force the power off of W7

(Not this issue at the beginning)

Thank you for a feedback.

Best regards, José.

5

Hi Clay,

So I closed Local went to V Box and tried to right click on Local by fly wheel and go to close > Power Off.

Unfortunately, this was dimmed out. I’m guessing it should be dimmed out anyway as Local was not running since I closed it.

Update: Currently just sitting at Starting Local Machine

Here is a copy of my local log:

Aug 9, 2017, 5:32 PM GMT+1 - info: [main/docker-machine-nfs] Mounting Boot2Docker volumes Attempt number:  1
Aug 9, 2017, 5:33 PM GMT+1 - info: [main/index] All Local sites are stopped. Shutting down VM.
Aug 9, 2017, 5:33 PM GMT+1 - info: [main/index] Existing Pressmatic data does not exist.
Aug 9, 2017, 5:33 PM GMT+1 - info: [main/set-docker-env] Getting Docker Machine env.
Aug 9, 2017, 5:33 PM GMT+1 - info: [main/set-docker-env] Received Docker Machine env.
Aug 9, 2017, 6:08 PM GMT+1 - info: [main/index] All Local sites are stopped. Shutting down VM.
Aug 11, 2017, 1:00 AM GMT+1 - info: [main/index] Existing Pressmatic data does not exist.
Aug 11, 2017, 1:00 AM GMT+1 - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Stopped\n', stderr: '' }
Aug 11, 2017, 1:00 AM GMT+1 - info: [renderer/CheckEnvPage] Check system promise response: [ undefined, 'machine-halted' ] machine-halted
Aug 11, 2017, 1:00 AM GMT+1 - info: [main/docker-machine] Checking Boot2Docker.iso hash
Aug 11, 2017, 1:00 AM GMT+1 - info: [main/docker-machine] Running  /Applications/Local by Flywheel.app/Contents/Resources/extraResources/virtual-machine/vendor/docker/osx/docker-machine start local-by-flywheel
Aug 11, 2017, 1:00 AM GMT+1 - info: [main/docker-machine] Starting "local-by-flywheel"...
Aug 11, 2017, 1:00 AM GMT+1 - info: [main/docker-machine] (local-by-flywheel) Check network to re-create if needed...
Aug 11, 2017, 1:00 AM GMT+1 - info: [main/docker-machine] (local-by-flywheel) Waiting for an IP...
Aug 11, 2017, 1:01 AM GMT+1 - info: [main/index] All Local sites are stopped. Shutting down VM.
Aug 11, 2017, 2:00 AM GMT+1 - info: [main/index] Existing Pressmatic data does not exist.
Aug 11, 2017, 2:01 AM GMT+1 - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Stopped\n', stderr: '' }
Aug 11, 2017, 2:01 AM GMT+1 - info: [renderer/CheckEnvPage] Check system promise response: [ undefined, 'machine-halted' ] machine-halted
Aug 11, 2017, 2:01 AM GMT+1 - info: [main/docker-machine] Checking Boot2Docker.iso hash
Aug 11, 2017, 2:02 AM GMT+1 - info: [main/docker-machine] Running  /Applications/Local by Flywheel.app/Contents/Resources/extraResources/virtual-machine/vendor/docker/osx/docker-machine start local-by-flywheel
Aug 11, 2017, 2:02 AM GMT+1 - info: [main/docker-machine] Starting "local-by-flywheel"...
Aug 11, 2017, 2:03 AM GMT+1 - info: [main/docker-machine] (local-by-flywheel) Check network to re-create if needed...
Aug 11, 2017, 2:03 AM GMT+1 - info: [main/docker-machine] (local-by-flywheel) Waiting for an IP...
Aug 11, 2017, 2:06 AM GMT+1 - info: [main/docker-machine] Machine "local-by-flywheel" was started.
Aug 11, 2017, 2:06 AM GMT+1 - info: [main/docker-machine] Waiting for SSH to be available...
Aug 11, 2017, 2:06 AM GMT+1 - info: [main/docker-machine] Detecting the provisioner...
Aug 11, 2017, 2:06 AM GMT+1 - info: [main/docker-machine] Started machines may have new IP addresses. You may need to re-run the `docker-machine env` command.
Aug 11, 2017, 2:06 AM GMT+1 - info: [main/set-docker-env] Getting Docker Machine env.
Aug 11, 2017, 2:06 AM GMT+1 - info: [main/set-docker-env] Received Docker Machine env.
Aug 11, 2017, 2:06 AM GMT+1 - info: [main/docker-machine-nfs] NFS Mount Status 
{ error: null,
  stdout: 'tmpfs on / type tmpfs (rw,relatime,size=917692k)\nproc on /proc type proc (rw,relatime)\nsysfs on /sys type sysfs (rw,relatime)\ndevpts on /dev/pts type devpts (rw,relatime,mode=600,ptmxmode=000)\ntmpfs on /dev/shm type tmpfs (rw,relatime)\nfusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)\n/dev/sda1 on /mnt/sda1 type ext4 (rw,relatime,data=ordered)\ncgroup on /sys/fs/cgroup type tmpfs (rw,relatime,mode=755)\ncgroup on /sys/fs/cgroup/cpuset type cgroup (rw,relatime,cpuset)\ncgroup on /sys/fs/cgroup/cpu type cgroup (rw,relatime,cpu)\ncgroup on /sys/fs/cgroup/cpuacct type cgroup (rw,relatime,cpuacct)\ncgroup on /sys/fs/cgroup/blkio type cgroup (rw,relatime,blkio)\ncgroup on /sys/fs/cgroup/memory type cgroup (rw,relatime,memory)\ncgroup on /sys/fs/cgroup/devices type cgroup (rw,relatime,devices)\ncgroup on /sys/fs/cgroup/freezer type cgroup (rw,relatime,freezer)\ncgroup on /sys/fs/cgroup/net_cls type cgroup (rw,relatime,net_cls)\ncgroup on /sys/fs/cgroup/perf_event type cgroup (rw,relatime,perf_event)\ncgroup on /sys/fs/cgroup/net_prio type cgroup (rw,relatime,net_prio)\ncgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,relatime,hugetlb)\ncgroup on /sys/fs/cgroup/pids type cgroup (rw,relatime,pids)\n/dev/sda1 on /mnt/sda1/var/lib/docker/aufs type ext4 (rw,relatime,data=ordered)\n',
  stderr: '',
  hasUsers: null }
Aug 11, 2017, 2:06 AM GMT+1 - info: [main/docker-machine-nfs] Enabling Docker Machine NFS
Aug 11, 2017, 2:06 AM GMT+1 - info: [main/docker-machine-nfs] Docker Machine NFS Result Configuring /etc/exports on macOS
The nfsd service is already enabled.

Aug 11, 2017, 2:06 AM GMT+1 - info: [main/docker-machine-nfs] Mounting Boot2Docker volumes Attempt number:  1
6

Hi Richard,

How long did you let it stay on the “Starting Machine” page before sending the log?

7

I had this issue and I updated virtualbox and it fixed itself

1 Like