"serversetup" CLI command fails if https is already enabled and forced about caprover-cli

[githubsaturn]

The doc clearly mentions this as you said it yourself:

You can either do this by visiting HTTP://IP_ADDRESS_OF_SERVER:3000 in your browser, or the recommended way which is the command line tool

The same issue can happen if you call serversetup , setup your server, and then call serversetup again. So I don't see this as an issue. If you set up the server via web dashboard, you won't be stuck in any bad state, you can simply use login to log in to an already set up server.

[githubsaturn]

I just reopned this issue as I realized you wanted a graceful failure - which totally makes sense.

[otlet]

I have this same problem, someone have idea what to do (without removing HTTPS?)

[githubsaturn]

@otlet
If you have an existing server, you shouldn't use serversetup. Instead, you should simply use captainduckduck login to log in to an existing server.

[githubsaturn]

Done in v1.1.0

To update:

npm i -g caprover

or

sudo npm i -g caprover