Getting an error message when trying to start a stack.
The process /Users/sparkktv/.indigo/stacks/8BE6DF/apache_AF7F/bin/httpd ran with PID 8371 and returned exit code 6 but one of the following was expected: "0". The stdErr contained: no output.. The stdOut contained: no output..

This seems to affect other apps also like Mamp, because I thought it was a localized app issue because I was getting an unable to start apache with Mamp also, then found your app, thought I'd give it a try.
Which btw, your app will be my new go to if this gets fixed because I like the setup and how easy it was. Way better app.
Hopefully this can be fixed.

Hey @sparkktv — wow, you're quick! 😆 Thanks for the bug report and research. We'll be working on Sequoia compatibility as its beta program progresses. Experience suggests it's not worth doing that too soon as so much can change; indeed the exit code 6 issue may well be a new macOS bug that will go away in a later beta release. Either way, the intention is definitely to have ongoing support for future macOS versions.

Literally same! Encountered the bug with Mamp, tried Mamp pro but there’s no MySQL 8 support out of the box, tried Laravel Herd but I need Apache. I was looking for alternatives and had never heard of your app before. Thanks Sequoia I guess ahah. Once this is resolved I’ll definitely switch over!

    Just curious — are you guys running Sequoia on your main Mac already, doing real work?

      Indigo Yes, everything is working and it's very stable for a beta 1 (except anything that needs apache - minus MAMP Pro which I explain below)

      davidwebca MAMP Pro is working with apache, it's the only one and we think we have figured out why. So MAMP Pro when you install it (I tried the 14 day trial) asks for permissions to run in background. Then MAMP Pro shows up under the new system settings - Login Items & Extensions - Allow In The Background.
      When you uninstall MAMP Pro and only use the free Mamp version, those Mamp permissions disappear. Indigo and Xampp also do not show up in those permissions. And someone pointed out on reddit that Homebrew is also having the same apache issue. Now in the Beta 1 release notes there are 2 reasons this may happen, one the now greater SIP settings or the new Application Support restrictions. And here is the funny part because I'm using Mamp free version still and NGINX is working but I had to turn off all URL rewriting and friendly URLs in my Joomla localhost in order to get it to play friendly with NGINX over apache.

            @Indigo Not to get into detail but Apple has 3 beta programs, Developer, Appleseed and Public. Right now it's only Developer and Appleseed and one of those requires you to run the betas on your main devices. And it's not developer. But I didn't say anything, lol. And that is how it is...

            sparkktv someone pointed out on reddit that Homebrew is also having the same apache issue

            Was that here perchance? If somewhere else, could you point me to it? I'm keen to monitor any conversations around this topic.

              Yes I had to install Sequoia early for work! It's not like I don't have other machines to work with so it's not a big deal, nothing urgent and can also dev locally with nginx which runs fine, but I'm glad it brought me to Indigo. I like to keep up-to-date with all the different local server solutions because I had never found one that scratched all my itches - having Apache to debug htaccess and other custom Apache stuff locally, among others - but y'all flew under the radar so much, I'm surprised you've been around in beta for so long without me noticing!

              And tbf, Apache seems to be the only thing buggy right now in Sequoia, everything else is super stable and no other app has failed on me - except Safari that has some rendering issues in some websites, but that's also to be expected.

              Sparkktv might be onto something about the permissions to run in the background because I can confirm that Mamp Pro does work over here too and having that "running in the background" permission in the settings is the only thing that's different I can notice.

              11 days later

              Quick update just to mention that I updated to Sequoia beta 2 + updated Indigo to RC9 and Apache is working again. 🥳

                davidwebca Yes homebrew, Mamp, Indigo, XAMPP all seem to work again in Beta 2. So it seems it was indeed a bug in Beta 1.
                From what Apple said it was a dyld bug in beta 1.

                  Powered by: FreeFlarum.
                  (remove this footer)