# Regenerating Machine Certificates \[Solved for macOS\]

**URL:** <https://community.localwp.com/t/regenerating-machine-certificates-solved-for-macos/10777>\
**Category:** Support\
**Created:** [January 30, 2019, 1:26am UTC](https://community.localwp.com/t/regenerating-machine-certificates-solved-for-macos/10777 "2019-01-30T01:26:43Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![richb-hanover](https://avatars.discourse-cdn.com/v4/letter/r/919ad9/32.png) [@richb-hanover](https://community.localwp.com/u/richb-hanover)\
**Post date:** [February 2, 2019, 10:20pm UTC](https://community.localwp.com/t/regenerating-machine-certificates-solved-for-macos/10777/2 "2019-02-02T22:20:06Z")

</div>

I am delighted to say that the procedure linked below worked for me on my macOS laptop. (Follow the first link below to see the full procedure…)

> **[Regenerating Docker Machine TLS Certificate, checking system won't start](https://community.localwp.com/t/regenerating-docker-machine-tls-certificate-checking-system-wont-start/5235/8)**
>
> Okay, let me know how this works for you: Quit Local if it’s running Open Terminal Run: alias local-docker-machine="/Applications/Local\\ by\\ Flywheel.app/Contents/Resources/extraResources/virtual-machine/vendor/docker/osx/docker-machine" Run...

I have [documented this in my blog](http://richb-hanover.com/local-by-flywheel-wont-start-because-its-regenerating-docker-machine-tls-certificates/) and also added a pointer to the solution into several of the other recent reports in the forum.

@ben.turner @clay - since this appears to happen frequently, could you find a way to:

1. Document the problem and solution more clearly, so that people searching for it can find a definitive answer.
2. Look for a way that Local by Flywheel can detect this situation and correct itself?

Thanks.

---

_[View the full topic](https://community.localwp.com/t/regenerating-machine-certificates-solved-for-macos/10777)._