Skip to main content
wog_ch
wog_ch
Participating Frequently
January 9, 2025
Question

Mac Sonoma (M1) and CF2023 connector issues regarding unsigned mod_jk.so

  • January 9, 2025
  • 2 replies
  • 546 views

Hi all

I have issues setting up the apache connector in CF2023 with Mac Sonoma (14.6). After executing wsconfig and setting up the sites, I get a config error.

 

[Thu Jan 09 10:54:05.757783 2025] [so:error] [pid 4178] AH06665: No code signing authority for module at /private/etc/apache2/mod_jk.so specified in LoadModule directive.
httpd: Syntax error on line 560 of /private/etc/apache2/httpd.conf: Syntax error on line 4 of /private/etc/apache2/mod_jk.conf: Code signing absent - not loading module at: /private/etc/apache2/mod_jk.so

 

Has anyone experienced the same? I tried it with the embedded CF Update 5 and the newest Update 12 which neither of them worked.

 

Thanks

    2 replies

    BKBK
    Community Expert
    BKBKCommunity Expert
    Community Expert
    January 10, 2025

    Ask ChatGPT, and see what it says. For example, I have attached ChatGPT 4o mini's answer to the question:

    quote

    I am running ColdFusion 2023 on Mac Sonoma. What does the following error mean, and how can I solve it?
    [so:error] [pid 4178] AH06665: No code signing authority for module at /private/etc/apache2/mod_jk.so specified in LoadModule directive. httpd: Syntax error on line 560 of /private/etc/apache2/httpd.conf: Syntax error on line 4 of /private/etc/apache2/mod_jk.conf: Code signing absent - not loading module at: /private/etc/apache2/mod_jk.so

     

    wog_ch
    wog_chAuthor
    Participating Frequently
    January 10, 2025

    I know that you can sign it with a self signed certifiacte, as stated in ChatGPT's answer. 

    It's just kinda odd to me that the mod_jk.so module in CF2018 is correctly signed with Adobe's Code Signing so I wanted to rule out if this is a general issue in this release. But, I figure from the answer it's not and as Charlie said, it seems to differ. 

    BKBK
    Community Expert
    BKBKCommunity Expert
    Community Expert
    January 10, 2025

    You mention CF2018, but this was a known issue even in ColdFusion 2021, which came later.  For example, go to the ColdFusion (2021 release) Update 2 notes, and scroll down to point 2. of the "Known Issues".

     

    Hoping it will help, I am repeating a suggestion I gave two years ago: you should request  a hot-fix from ColdFusion Support (cfsup[at]adobe.com). 

    Charlie Arehart
    Community Expert
    Charlie ArehartCommunity Expert
    Community Expert
    January 9, 2025

    There have been complaints of that problem for years with different cf and MacOS versions. More important, the problem has seemed something affecting even people not using cf.

     

    Sometimes Adobe has done something to address it, sometimes they've noted that Apple did something to fix it. Other times people have shared workarounds.

     

    Unless someone else offers a specific answer for you, I'd propose you do a Google search this (including the quotes):

     

    "No code signing authority for module at * specified in LoadModule directive"

     

    to consider the context and perhaps some of the workarounds. 

     

    Check out also this tracker ticket AND see ALL the comments (don't stop at the first few whiney ones) :

    https://tracker.adobe.com/#/view/CF-4203359

     

    If you or anyone identifies a solution that works, let us know. 

    /Charlie (troubleshooter, carehart. org)
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices