Newbie - Windows issue with "Starting the Dev Server"

[philwil...@gmail.com]

Everyone:

I have been looking at Vault for a couple of days and finally started to jump in and play with the dev server.  I downloaded the Windows 64-bit zip and set the Path in my Windows 7 box.  I opened up a terminal window and entered "vault server -dev" just like the instructions say to do.  I get the same output as the example with a bunch of log statements at the bottom of the output.  I am no longer able to type into the command window to enter the export/set commands that are needed.

Even if I open up another command window and set the VAULT_ADDR the vault status command gives me: "Error checking seal status: Get /v1/sys/seal-status: unsupported protocol scheme".  I did not expect this to work but I tried it anyway.  Have I done anything wrong?

Thanks

Phil Willemann

P.S.  The demo I am following is at: https://vaultproject.io/intro/getting-started/dev-server.html

[Armon Dadgar]

Hey Phil,

The “vault server" command is long running and takes over the shell once you are running it.

You will most likely need to use another shell to interact with Vault, or find a way to run it in the

background.

The “unsupported protocol scheme” error is likely coming from using HTTP to talk to an HTTPS

endpoint or visa vera. Alternatively, the VAULT_ADDR could be incorrectly specified and neither

scheme is being used.

Hope that helps!

Best Regards,

Armon Dadgar

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/hashicorp/vault/issues
IRC: #vault-tool on Freenode
---
You received this message because you are subscribed to the Google Groups "Vault" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vault-tool+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vault-tool/a3a1754e-f0c2-427c-8863-f42f1a305cc8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[russell....@sas.com]

Hey Armon,

I just ran into the same issue and googling "Error checking seal status" brought me to this topic.  May I suggest this be fixed to ease the startup pain of other newbies?  The fix would comprise of changing the text output when the dev server is cranked up (which is one of the first things a newbie would do).  Instead of 

   export VAULT_ADDR='http://127.0.0.1:8200'

change it to

    set VAULT_ADDR=http://127.0.0.1:8200

on Windows.  After all this is a windows exe being run so hopefully the environment variable setting command can tailored to the environment.  If it is not possible to make it Windows specific, it's best to show both the Unix version and the Windows version.  One could argue that issuing the "export" would fail on Windows and the newbie would then fix it.  When my "export" failed, I ONLY changed "export" to "set" and promptly got "Error checking seal status" and then googled to find this issue. 

I REMOVED the single quotes to have "vault status" produce the expected result.  Since this is quite literally the third command issued fixing this would make the newbie startup experience smoother.

Thanks,

Russell

On Thursday, July 2, 2015 at 7:59:49 PM UTC-4, Armon Dadgar wrote:

Hey Phil,

The “vault server" command is long running and takes over the shell once you are running it.

You will most likely need to use another shell to interact with Vault, or find a way to run it in the

background.

The “unsupported protocol scheme” error is likely coming from using HTTP to talk to an HTTPS

endpoint or visa vera. Alternatively, the VAULT_ADDR could be incorrectly specified and neither

scheme is being used.

Hope that helps!

Best Regards,

Armon Dadgar

[Armon Dadgar]

Hey Russell,

Thanks for the feedback! We have an open ticket with these suggestions here:

https://github.com/hashicorp/vault/issues/435

I’ve added your recommendations to the ticket as well. We will try to update all that for our next release!

Best Regards,

Armon Dadgar

To view this discussion on the web visit https://groups.google.com/d/msgid/vault-tool/e0da932a-1ddc-4b4c-ab2e-5df6018a1e5d%40googlegroups.com.