Running serversetup again should not try to setup an existing server

[solomon23]

If you run serversetup against an existing server - it should check and not try to setup SSL again. Ref #30

[Hazzard17h]

If you run serversetup against an existing server with root ssl and redirect (setupped from CLI), it warns with "You may have already setup the server! Use caprover login to log into an existing server.", and fails with an error.

[solomon23]

In my case i ran serversetup against an existing server that I never setup with the CLI. The SSL was already setup though and it asked to set it up again.

[Hazzard17h]

Maybe the http -> https redirect is not enabled, otherwise it should warn as I said, even if it is not setupped from the CLI.

[githubsaturn]

I believe there's a way for us to detect the existing installation if "force HTTPS" isn't activated. We can do so by getting the existing root domain of the installation. If the root domain is the default one, we know it's a fresh installation, otherwise it's an existing installation.

[solomon23]

Maybe the http -> https redirect is not enabled, otherwise it should warn as I said, even if it is not setupped from the CLI.

Correct - I never enabled that

[Hazzard17h]

See here
Needs to be tested @solomon23

[solomon23]

@Hazzard17h Confirmed it fixes it

[githubsaturn]

Fixed in #33 and released as 2.1.0