Windows EnvKey cannot start anymore

[henrywood]

Help !
The Windows UI program can no longer start - The load screen just stays put forever....

The last thing I did in the UI program was to click commit on a change. Upon doing this I got an error saying there was a problem with the update and from that point on I am not able to start Envkey (on Windows) any more ???

I also tried deleting the contents of %APPDATA%\envkey but that did not help...

Please help !

[henrywood]

It works now - probably something at EnvKey - Closing....

[henrywood]

@danenania henrywood here again.
Can you please show the exact steps to use envkey servers create ?

$ envkey servers create

gives
Authentication required. Use envkey sign-in, or envkey accept-invite
So I tried:

$ envkey sign-in

Gives:
No EnvKey accounts are stored on this device.

Try envkey accept-invite

So we try that

$ envkey accept-invite

It then asks me for a token (which I don't have)

In the .envkey I noticed an appId but since I have approx. 20 apps to create server keys for (and 3 environments), I don't think that is the way to go (having to provide 20 appIds / .envkey files ???)

Please help !

[danenania]

Are you running the CLI on a different server/device than the one that you installed the UI on? Or running it within a container or VM?

If that's the case, you would either need to:

• Authorize a new device on the machine where you've already installed the CLI (by clicking the Add + button in the sidebar on the left, then Authorize Device), then accept the invitation on the other machine. You would do this if you want to run the CLI on another development machine separate from the one you created your organization on.

• Create a CLI key (Add + > Create CLI Key) and then pass it through the --cli-envkey parameter to your CLI commands. You would do this if you want to run CLI commands on a server or in a VM/container where installing the UI doesn't make sense.

If you use the --cli-key parameter or set a CLI_ENVKEY environment variable, the CLI runs in 'Auto mode' rather than 'Interactive mode' (more on that here: https://docs-v2.envkey.com/docs/cli-overview#interactive-mode), meaning you have to provide all arguments vs. being prompted for missing arguments in interactive mode. So if you're using a CLI key, the full command would be something like:

envkey servers create my-app production my-server-name --cli-envkey your-cli-key

[henrywood]

I am running on the same machine that runs the Windows UI, but I am running inside WSL2 ?

[danenania]

Ok, EnvKey account info is stored in $HOME/.envkey so if that points to a different location under WSL, you would either need to treat it like a separate device and follow the device authorization flow I described, or else use a CLI key. Another option could be to use git bash or CMD for your shell, where the CLI should also work.

[henrywood]

Thank you - I will look into it tomorrow - It's getting late here !
Sorry for the late reply !

[henrywood]

I now tried servers create
I did:

# envkey --cli-envkey=... seqgenerator development

And I got:
{"ok":false,"error":"Environment not found"}

What am I doing wrong ?

Please help !

[danenania]

Can you paste the full command (except for the --cli-envkey)? The following should work:

envkey --cli-envkey=... servers create seqgenerator development server-name

unless you've removed or changed the name of the development environment? You can use this to check on the environments for that app:

envkey --cli-envkey=... envs seqgenerator

[henrywood]

Hi @danenania
Here are my findings:

# envkey --cli-envkey=... envs seqgenerator

gives:

{"ok":true,"environments":[{"id":"992e83e5-9722-49ee-9ec2-cda05f1818cf","name":"Development","branches":[]},{"id":"e7cb7e61-3879-44b1-a439-cb95f9d8a3ed","name":"Staging","branches":[]},{"id":"7be3d1b9-ed71-4cbf-8efe-f2ea0a121023","name":"Production","branches":[]}]}

So I thought this would work:

# envkey --cli-envkey=... servers create SEQGENERATOR seqgenerator Development

but that gives:

{"ok":false,"error":"Environment not found"}

And it does not matter if I use "Development" or "development"

Sorry for not getting back to you sooner - I was busy today :)

[danenania]

It looks like you have the environment and server name switched. Try:

envkey --cli-envkey=... servers create SEQGENERATOR Development seqgenerator

You can get help for parameters/parameter order with envkey servers create -h

[henrywood]

Thank you - that worked :)

[danenania]

Great!