I know NSSM exists but it's not working out so well on these new Windows Server 2019 machines.

We have a manual step to associate you with permissions to install the private package

Edgardo probably just hasn't gotten a chance to reach out to you yet

Ok. It said that if the user name is entered during purchase, you don't need to wait or contact support to have them tied together

now it's installing 🙂

Thanks for the quick help

So I thought the issue I was seeing was with Windows Server 2019 because I THOUGHT it was the only real difference between it and a server with no problems. It turns out the difference causing the issue was actually that on one server, the web.http.port is in server.json directly and the other server has ${WEB_HTTP_PORT} in server.json and that value is set in .env. When the port is in the .env file, using a service wrapper (whether it is created with NSSM or cb service manager), the port comes up random every time so it seems to not be loading .env first. Those .env vars ARE in the server scope of the app once the server starts. Reproduce it... .env

WEB_HTTP_PORT=8081

server.json

{
    "name":"app1",
    "app":{
        "cfengine":"lucee-light@5.3.8+206"
    }"web":{
        "host":"0.0.0.0",
        "http":{
            "port":${WEB_HTTP_PORT}
        }
    }
}

• start the server with the start command... everything is fine and the port is 8081 • run

server service create

from the app root • Use the windows service manager to restart the service (or powershell

restart-service app1

) • Server comes up on a random port each time