Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
0

I am getting failure from the ColdFusion 2023 AutoLockdown Tool, about server requirements

Explorer ,
Mar 08, 2025 Mar 08, 2025

Here is the log file - The RDP is not enabled but the error says it is and it is a Production install with security: --- Any Thoughts on getting this lockdown tool to workScreenshot 2025-03-08 224252.png?
2025-03-08 22:31:41 INFO - Path:C:\ColdFusion2023\lockdown\cfusion
2025-03-08 22:31:41 INFO - LINE_DEBUGGER_ENABLED -> false
2025-03-08 22:31:41 INFO - developer_enabled -> false
2025-03-08 22:31:41 INFO - REMOTE_INSPECTION_ENABLED -> false
2025-03-08 22:31:41 INFO - ajax_enabled -> false
2025-03-08 22:31:41 INFO - robust_enabled -> false
2025-03-08 22:31:41 INFO - FLASHFORMCOMPILEERRORS -> false
2025-03-08 22:31:41 INFO - enabled -> false
2025-03-08 22:31:41 INFO - Remote admin component is enabled. Server is not production profile. Please delete the AdminServlet.war from jetty to disable it and try again!
2025-03-08 22:31:43 INFO - ColdFusion is running

156
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Explorer , Mar 09, 2025 Mar 09, 2025

To get the lockdown tool to work I did as the log file said... - "Remote admin component is enabled. Server is not production profile. Please delete the AdminServlet.war from jetty to disable it and try again."

i deleted the AdminServlet.war file. 

Once i installed the tool, the permissions on the other website (.net) on the server were completely hosed, even though i did not select it as one of the sites. And, the install of ColdFusion Admin was not accessible and neither were any websites runnin

...
Translate
Explorer ,
Mar 08, 2025 Mar 08, 2025

I got it... thanks

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Mar 09, 2025 Mar 09, 2025

Hi @LarryRamp , glad to hear that you solved it. Could you please share your solution with the rest of the forum? It will certainly help someone somewhere.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Mar 09, 2025 Mar 09, 2025

While we await his reply, I'll note that the error log does say it was NOT running the production profile, as Larry proposed. It will be interesting to hear which it was.

 

BTW, Larry, the "remote admin" referred to is not about "RDP" but about an option offered during the CF install process (on its "servlets" page, along with solr and pdfg), which if enabled get implemented in the cf add-on service (the "jetty" mentioned there). It's a feature which primarily allows start/stop of cf from CFBuilder, so not desired or needed in the prod profile. Not critical to know, but just thought you or future readers might appreciate the clarification. 

/Charlie (troubleshooter, carehart.org)
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Mar 09, 2025 Mar 09, 2025

To get the lockdown tool to work I did as the log file said... - "Remote admin component is enabled. Server is not production profile. Please delete the AdminServlet.war from jetty to disable it and try again."

i deleted the AdminServlet.war file. 

Once i installed the tool, the permissions on the other website (.net) on the server were completely hosed, even though i did not select it as one of the sites. And, the install of ColdFusion Admin was not accessible and neither were any websites running CF. I did select IIS when the i went thru the lockdown tool install... at this point i was thinking ... restart CF web service? The tool turned all the CF services off, when i trued to start the CF web service, if would not start. Fortunately i took a full backup prior to installing the lockdown tool.  I did a restore of the server and called it a night.
Today i will attempt this process again.  Any thoughts or insights?

 

 

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Mar 09, 2025 Mar 09, 2025
LATEST

Thanks for sharing that, @LarryRamp .

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Resources