Legacy SSL config doesn't respect enable = false
Description
Activity
Francisco Mancardi February 14, 2024 at 8:52 PM
The error I’ve got is
CommandBox:CommandBox> start ./cfg/cf2023.6.no-pkgs.json --console
√ | Starting Server
| √ | Setting site [cf2023.6.no-pkgs] Profile to [development]
| √ | Loading CFConfig into serverException in thread "main" java.lang.RuntimeException: File not found: C:\CommandBox\cfg\ssl\wildcard.dev.local.pem (C:\CommandBox\cfg\ssl\wildcard.dev.local.pem)
at runwar.options.ConfigParser.getFile(ConfigParser.java:491)
at runwar.options.ConfigParser.parseOptions(ConfigParser.java:344)
at runwar.options.ConfigParser.<init>(ConfigParser.java:34)
at runwar.Start.main(Start.java:37)Server's output stream closed. It's been stopped elsewhere.Stopping server...ERROR (6.0.0+00787)Server process returned failing exit code [1]
Francisco Mancardi February 14, 2024 at 7:33 PM
Hi
Thanks for your quick reply.
I’m sorry for not been clear enough. I will try again:
I’m using the same .json file that worked ok with version 5.9.1
and people that have installed 6.0.0 have the issue I’ve described.
I’m posting now the whole config file, maybe something is not compatible with 6.0.0.
Thanks again for your help
Brad Wood February 14, 2024 at 7:11 PM
I just realized your ticket title says “6.0.0”. At first I just saw your reference to “CommandBox 5.x.x” and the wording of the ticket seemed to imply you weren’t aware of any version changes.
Brad Wood February 14, 2024 at 7:03 PM
Can you verify what version of CommandBox you are on? I have just released CommandBox 6.0 last night (blog post pending) which has many changes regarding servers with the new Multi-Site functionality and binding syntax. And while it wasn’t expected for this behavior to change, if we know this is a CommandBox 6 regression, it will be easier to track down.
We have standard server configuration files that we use for development and also for Quality Assurance enviroment. Instead of removing the useless config section like SSL in development environment, we disable it setting enable = false
This has worked ok for any Adobe CF version with CommandBox 5.x.x.
Today I’ve installed for scratch (during a training session) latest CommadBox version, and since now
when trying to start a Adobe CF2023 the server crashed because it wants to read the .pem files.
Similar configuration works ok with Adobe CF2021.
This is the piece of configuration that has problems
This issue is not a blocking one, because we can remove this configuration instead of disabling it.
Best regards