I couldn’t get debug to work,
You gotta give us more than that. Exactly what did you do to try and enable the debug start? What happened when you tried? Where did you look for output? I can assure you debug starts do work, but we can’t help you unless we know what it is you’re doing.
First I tried adding “debug”:“true” to /app/server.json
wasn’t sure where that output was going
It’s just the console log of the container. Where this output is visible depends on how you’re starting your container.
Then I tried running “box server set debug=true” from the console, it says it was set to true, and I see normal Lucee outout in the container console, but I’m unsure if this actually worked.
I was able to change the cfengine by using “box server set email@example.com+62” from the /app directory and that seems to have worked.
Yes, that would support my suggestion that you had already started another cf engine version in your container.
Editing /app/server.json in a text editor has no effect.
I don’t understand what you mean. What exactly did you edit and what exact effect were you expecting to see? What steps did you take to enact this expected effect?
I edited the server.json, changing the cfengine value, in the mounted /app volume. Then from inside the container console I did “box restart” (which restarts the container?), and any changes I made to /app/server.json has no effect on the restarted server.
I figured if there was a mounted /app volume, server.json, box.json would be priority #1. If I search the container for server.json the only other result is: /usr/local/lib/CommandBox/cfml/modules/commandbox-cfconfig/modules/cfconfig-services/server.json
From the path, I would think that’s an internal CommandBox or cfconfig file, nothing to do with ‘my’ app or server. Am I wrong?
I still get a connection error trying to update extensions or update lucee through the Lucee admin, but with a stack trace this time.
What exact page in the admin were you on and what exact button did you click?
The location & actions are navigate the url to /lucee/admin/server.cfm?action=ext.applications or from the Lucee server admin click Extensions > Applications.
Pick an outdated extension, the mssql driver in my example, select the latest release from the dropdown, then click the “upgrade / downgrade” button.
Then the error appears.