Mkcert doesn't exist.

Olle

Hi,

First things first, I am loving this idea. The only thing is: I am not really getting it to work on my system.
I was using dnsmasq and my own certificates, and so I might not have the cleanest start.

I have been mucking about installing and removing Indigo, but there seems to be a problem now:

Indigo could no start successfully
The following error occurred during Indigo's startup: The file "mkcert" doesn't exist.

I get that there's something missing but where? I checked the ~/.indigo/ssl and there's no mkcert there. Should it?

Indigo

Hi @Olle! Thanks for your post — I'm keen for Indigo to work well even for those with other infrastructure already in place on their Mac, so I'm very open to ideas about how Indigo might make this work easier in your setup.

Indigo installs its own copy of Dnsmasq, in the System Stack. That can be found at ~/.indigo/stacks/system-stack/dnsmasq. You can get there like so:

To get things back to a working state, could you try rebuilding the System stack? To do this, right-click the "System" stack and select "Rebuild...":

So long as your other install(s) of Dnsmasq are not running (quit them in Activity Monitor if need be), Indigo should be able to launch its own copy and be happy 🙂 Dnsmasq uses port 53 and so there's no way that I'm aware of to run two instances unfortunately.

Let me know how you go!

Indigo

Oh man, I am not concentrating this morning! I've written the above thinking you had issues with Dnsmasq, sorry 🙈

The System Stack also contains mkcert, but doesn't show it in the UI as it doesn't "start up" but rather does one thing when the System Stack launches and that's it. You can find it in a similar path to that mentioned above for Dnsmasq.

The error "The file "mkcert" doesn't exist." will hopefully go away once you rebuild the System Stack as per the above instructions. Either way you can check if it does actually exist at ~/.indigo/stacks/system-stack/mkcert/bin/mkcert.

On a separate-but-related matter, I have some concerns about the trusted certificate (in your Keychain) when you've already used Mkcert previously. Did you observe any problems on that front?

Olle

Thank you for your quick response! I was away for some time so, sorry for my late one. ;-)

The thing is: as soon as I start IndigoStack I get this error and the app closes again. So rebuilding the System stack is not possible. I did try to remove the app and reinstall it. (https://indigostack.app/docs/how-to/uninstall/). In this process I did not remove any certificates, since the one I generated myself some time ago

The reinstall did not magically make the mkcert appear. The helper installs, the error pops up and the app stops as soon as I OK the error..

After the new installation there is no /usr/local/indigo folder and the ~/.indigo/stacks/system-stack folder contains no "mkcert" folder at all.

What I did now is: making a symlink from mkcert in my /usr/local/bin to ~/.indigo/stacks/system-stack/mkcert/bin ..
This did something good, the "mkcert" error is gone. So maybe the existence of the /usr/local/bin/mkcert was an issue?

Only now I get the same error for dnsmasq:
The following error occurred during Indigo's startup: The file "dnsmasq" doesn't exist.
I tried to reinstall my dnsmasq via brew, stop the service and symlink it too, but that does not seem to work.

Indigo

Thanks for the followup. Would you be happy to send me your Indigo logs by email (support@indigostack.app)? You're seeing some pretty crazy behaviour!

As per https://indigostack.app/docs/help/faq/#q-where-does-indigo-install-its-services the two log files are:

App logs: stored at ~/Library/Logs/com.marmaladesoul.Indigo
Helper logs: stored at /var/log/com.marmaladesoul.IndigoHelper/IndigoHelper.log

Indigo

I've traced the code prior to the error you gave in your first post, and here's what I think may have happened:

you did at some point get the system stack running, and a stack of your own was able to start (I hope I am right on this as the rest depends on it having happened this way)
Indigo stores a list of previously-started stacks in the macOS user defaults system, which is cached and only reliably resets on a restart of your Mac, so the (optional) sudo defaults delete com.marmaladesoul.Indigo uninstallation instruction won't take full effect immediately.
you also likely removed the System Stack as part of your attempts at a clean start (much appreciated by the way! 🙂 )
when the freshly-installed Indigo was started, it saw that there were previously-started stacks at some point (due to the app's cached user defaults), and as such inferred that the system stack would not need its "prepare" phase (which is where it clones fresh services into ~/.indigo/stacks/system-stack/), including dnsmasq and mkcert.

This latter logic is a bit of an oversight/assumption on my behalf, so I'll code what I believe to be a fix for this issue, and let you know on this thread how it goes.

If you get a chance, the logs are still of interest as they should prove my theory one way or another. Thanks again for your efforts getting to the bottom of this issue.

Olle

Indigo
I cannot remember exactly but the scenario you think I did sure sounds like me. ;-)

The 4th point you mentioned sounds like the problem I run into. Something like this was my gut feeling too.

The logs are on their way. Thank you for your help!

Indigo

This issue should be resolved in beta 11 which has just been released.

Olle

You totally fixed it. Thank you so much. ;-)

Indigo

Awesome, thanks for the feedback!