Apache start problem Under Sonoma (Mac M1) I get httpd error 256

Apache comes built-in to the operating system. There is nothing else you need to install. I've posted some instructions on how to configure it here: Setting up a local web server on macOS 14… - Apple Community

You are actually using Terminal, not Console. Console is a logging tool and it's much worse.

Otherwise, this is a typical Homebrew problem. The only thing unusual about your post is that you straight up mentioned Homebrew right away. Usually I have to pry that information out of people. Any time someone shows up here with some crazy problem no one has ever seen before in Terminal, Homebrew is the cause.

Unfortunately, you will find Homebrew very difficult to remove. It makes significant changes to your command line environment. You will need advanced Terminal skills to correct the damage.

I usually just recommend that people erase the hard drive and reinstall the operating system. When you restore from backup, make sure to NOT restore apps, software, system settings, or "other files". With Homebrew, I'm not even sure you can restore your user accounts and user files. Some of your command line configuration files are stored in the home directory. But once you fix the larger problems, you can at least create a new user account. You can copy the command line config files from that new user account back to your current account and finally undo whatever Homebrew has done.

Good luck!

UweRasche wrote:

I have 2 other Mac. At this Mac Homebrew was never install. There also the internal apache server from OSX.

Apache is not like typical apps. It includes a number of configuration files in /etc/apache2. If these have been modified in any way, then Apache may not run.

I get the following error:

Raschesserver:~ uwerasche$ sudo apachectl configtest

[Sun Nov 19 18:13:01.786866 2023] [so:error] [pid 3930] AH06665: No code signing authority for module at /usr/libexec/apache2/mod_cache_socache.so specified in LoadModule directive.

httpd: Syntax error on line 98 of /private/etc/apache2/httpd.conf: Code signing absent - not loading module at: /usr/libexec/apache2/mod_cache_socache.so

It is no so easy to try the codesign tool. Do you understand me.

You don't need to use the codesign tool at all. You need to correct your Apache configuration. The mod_cache_socache module is not enabled by default. Furthermore, it is not on line 98. You, or some other entity, had made changes to your Apache config file and now it will not work. What those chances are, I can't say. All I can say is that you either have to learn codesign, learn Apache configurations, or rebuild your system using default settings.

My instructions for running Apache always assume default settings. There are 557 lines in /etc/apache2/httpd.conf. Your version might have more. Any line could be changed. That's literally an infinite number of possibilities. You either learn to swim with the defaults and progress slowly, or dive in head-first into the deep end and hope it all works out.

PS: While checking the default settings of mod_cache_socache, I had to setup Apache again in a new Sonoma VM. I discovered a small error in my instructions and corrected it. Setting up Apache in Sonoma should take about 45 seconds.

Uwe Rasche wrote:

I have this problem which the internal Mac apache server too. It is not the problem from Homebrew.

Even when someone never mentions the word, I can tell, just by their description, when it is caused by Homebrew. In your case, the word "homebrew" was in practically every line of your post.

Once you install Homebrew, it corrupts the entire system. Even the built-in Apache isn't going to work anymore.

I get a "permission" error. I try it now with Homebrew, because the files are not in the protection folders.

I don´t know, how I can tell macOs to start it. It has no ".app" attention. I think, this is the problem.

The problem is Homebrew.

PS: Homebrew put all part in one folder. Delete is easy. So the description . I have only extent the $path folder. I do it manual today

If it's easy, then it should be easy to fix. Voila! Problem solved.

I have 2 other Mac. At this Mac Homebrew was never install. There also the internal apache server from OSX.

I get the following error:

Raschesserver:~ uwerasche$ sudo apachectl configtest

[Sun Nov 19 18:13:01.786866 2023] [so:error] [pid 3930] AH06665: No code signing authority for module at /usr/libexec/apache2/mod_cache_socache.so specified in LoadModule directive.

httpd: Syntax error on line 98 of /private/etc/apache2/httpd.conf: Code signing absent - not loading module at: /usr/libexec/apache2/mod_cache_socache.so

It is no so easy to try the codesign tool. Do you understand me.

Barney-15E wrote:

The default mod_cache_socache.so does not generate a code signing issue. Where did you get your version of that module?

It did for me when I first tried it. Then when I went to the Apache site to figure out just what it is supposed to do, the Apache site listed another module dependency that is required. When I enabled that one, then it worked. But I still don't know what that module is used for.

Apparently, it is a "Shared object cache (socache) based storage module for the HTTP caching filter." Woohoo! Party in the house tonight!

The default mod_cache_socache.so does not generate a code signing issue. Where did you get your version of that module?

your note is very well. I find it too

I choose the wrong row

Now the internal apache server is running with ssl certificate. It was a hard weekend for me but it is fine.

Now the internal apache server is running with ssl certificate. It was a hard weekend for me but it is fine.

Glad to hear that.