search

micronaut-projects / micronaut-core

Micronaut Application Framework
http://micronaut.io
Apache License 2.0
6.07k stars 1.07k forks source link

Micronaut CLI SSL certificate error #2141

Closed zouxiang closed 5 years ago

zouxiang commented 5 years ago

Thanks for reporting an issue for Micronaut, please review the task list below before submitting the issue. Your issue report will be closed if the issue is incomplete and the below tasks not completed.

NOTE: If you are unsure about something and the issue is more of a question a better place to ask questions is on Stack Overflow (http://stackoverflow.com/tags/micronaut) or Gitter (https://gitter.im/micronautfw/). DO NOT use the issue tracker to ask questions.

Task List

Steps to Reproduce

  1. download micronaut binary from official website to local(C:\micronaut-\<release version>)
  2. create an environment variable MICRONAUT_HOME which points to the installation directory i.e. C:\micronaut-\<release version>)
  3. update the PATH environment variable, append %MICRONAUT_HOME%\bin.
  4. running mn in windows command prompt

Expected Behaviour

C:\Users\xizou>mn | Starting interactive mode... | Enter a command name to run. Use TAB for completion:

Actual Behaviour

C:\Users\xizou>mn | Error Error occurred running Micronaut CLI: unable to find valid certification path to requested target (Use --stacktrace to see the full trace)

Environment Information

jameskleeh commented 5 years ago

This doesn't have anything to do with Windows. This is due to some issue local to that machine.

This has been reported several times before:

https://github.com/micronaut-projects/micronaut-core/issues/1115 https://github.com/micronaut-projects/micronaut-core/issues/627 https://github.com/micronaut-projects/micronaut-core/issues/167

jameskleeh commented 5 years ago

If you figure out why this is happening, please let us know so we can add a section in the docs about dealing with this issue.

zouxiang commented 5 years ago

@jameskleeh thanks for your comments, I just tried to run mn again, this time it works, looks like a proxy/firewall issue probably.