Keep getting "System stack failed to start" after upgrading from beta8 to beta10

fmitchell

Greetings.

Had my test site working on beta8 with some custom PHP settings. I upgraded to beta10 and the site won't start anymore. I've removed my custom settings from the .indigostack folder to no avail.

Every time I attempt to start the stack, it gives me:

The system stack failed to start. nginx: [emerg] host not found in upstream "cusurgD9" in /Users/fredric/.indigo/stacks/system-stack/nginx_reverse_proxy/conf/sites-enabled/rp.cusurgD9.conf:35

I deleted the stack entirely and created a new one from scratch and get the same message.

I ran the uninstaller from the helper tool and reinstalled, still the same message.

I'm guessing the only option I have is to completely remove and install from scratch?

fmitchell

Removed everything per the uninstall instructions, re-installed and getting "The file dnsmasq doesn't exist."

Indigo

Wow, sorry it's causing you these issues! A few questions/thoughts:

when you removed your custom PHP config from your .indigostack bundle, did Indigo notice and offer to restart the stack?
have you overridden the config for any other services in your stack (eg Nginx)? Is there anything else at all other than config.json in your stack's .indigostack bundle?
when you removed everything, were you referring to https://indigostack.app/docs/how-to/uninstall ? If so, which steps from there did you do?

Regarding the error nginx: [emerg] host not found in upstream "cusurgD9":

this error is actually from the System Stack's Nginx, which starts up after your stack starts
therefore by that point your stack must actually have started — it should be green in the stack list, while Indigo attempts to restart the System Stack. If the System Stack fails to start, your stack will no longer be green. Can you see this sequence of events?

It's the System Stack's nginx which provides the reverse proxy for the "cusurgD9" domain. The error means the System nginx cannot find a server at that domain, which means either your stack isn't serving it, or dnsmasq is not resolving it. Your later mention of Dnsmasq issues makes it sound like the latter might be the case.

Thoughts for fixing the situation:

firstly, uninstalling & reinstalling Indigo is unlikely to fix the cause of this problem; in my experience with these kinds of nginx errors (which I have gotten a variety of during development), rebuilding either the stack or the System Stack should resolve them. That's by design; everything Indigo builds for you is intended to be ephemeral; the stack file(s) are the single source of truth.
have you tried rebuilding the stack and particularly in your case, the System Stack? (right-click them in the stack listing and choose "Rebuild...")

Let me know how you go, and if you still have no luck we can take this issue up a level 🙂 Thanks for persisting!

pronskiy

I had the same error, and what helped is changing the top domain: my-site.local -> my-site.test.

Indigo

Thanks @pronskiy for posting your solution. There's a discussion about .local as a test domain TLD over at https://forums.indigostack.app/d/41-cant-start-apache — I think the general concensus is it's a bad idea to use .local for this purpose (particularly on a Mac).

I actually have an issue in my tracker to either block the creation of .local domains in Indigo, or at the very least put up a dialog explaining the potential problems.