http://coldfusion.com logo
#box-products
Title
# box-products
b

bhartsfield

05/20/2022, 8:04 PM
Just had my manager buy a service-manager license so I can vet it in dev before buying enough to cover prod. He entered my username when purchasing but this is what I get after logging in and trying to install (which is pretty much the entire installation documentation) Am I missing a step somewhere?
I know NSSM exists but it's not working out so well on these new Windows Server 2019 machines.
b

bdw429s

05/20/2022, 8:07 PM
@bhartsfield What's your forgebox username?
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
b

bhartsfield

05/20/2022, 8:08 PM
sent the name in chat
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
b

bdw429s

05/20/2022, 8:08 PM
Yeah, I'm putting you in now
b

bhartsfield

05/20/2022, 8:08 PM
awesome. thanks
b

bdw429s

05/20/2022, 8:09 PM
I hate that it's manual, but we have a low enough volume we just haven't automated it yet
b

bhartsfield

05/20/2022, 8:09 PM
gotcha. well, if it works out, your volume will pick up all at once, then go back to normal heh
b

bdw429s

05/20/2022, 8:10 PM
Ok you should have an E-mail already at the address associated with that account
b

bhartsfield

05/20/2022, 8:12 PM
Got it. Accepted
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
Copy code
{
    "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
4 Views