Hi Hemant,
This sounds like it's most likely a networking/firewall issue rather
than an issue with Vault itself. I think a good first step would be to
try using openssl s_client, netcat, telnet, etc. to attempt a straight
TCP connection to the Vault server endpoint. If you can establish a
successful TCP connection using one of these tools but the Vault CLI
doesn't work, that gives us a good amount of information that we can
use to help figure out what the issue may be.
Can you also please list which version of Vault you're using and what
Docker container?
Thanks,
Jeff
> --
> 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/b132d4c1-cb29-4b08-a5c4-9606f0c9380c%40googlegroups.com.
>
> For more options, visit
https://groups.google.com/d/optout.