0

I couldn't run the command

bubblewrap init --manifest="https://mydomain/manifest.json"

I got error

cli ERROR unable to get local issuer certificate

I tried to set false "strict-ssl" also tried to configure

npm config set cafile "file/-path.crt"

but unable to fix this error.

James Z
  • 12,209
  • 10
  • 24
  • 44
VigneshK
  • 753
  • 1
  • 10
  • 28

1 Answers1

-1

The error message you're encountering suggests an issue with the SSL certificate verification when trying to fetch the manifest from the specified URL. This error can occur if the SSL certificate on the server hosting the manifest is not recognized or trusted by your local machine.

Here are a few possible solutions you can try:

Disable strict SSL checking (temporary solution):

npm config set strict-ssl false

By setting strict-ssl to false, you disable strict SSL checking for all npm packages. This approach should only be used temporarily and is not recommended for production environments.

Specify the certificate authority file (.crt) explicitly (recommended solution):

npm config set cafile "path/to/certificate.crt"

Replace "path/to/certificate.crt" with the actual file path of your trusted certificate authority (CA) certificate. This will instruct npm to use the specified certificate for SSL verification.

Use a local file for testing (alternative solution): If you're running a local development server and have a local copy of the manifest file, you can try providing a local file path instead of an HTTPS URL:

bubblewrap init --manifest="path/to/manifest.json"

Replace "path/to/manifest.json" with the actual file path on your local machine.

It's important to note that the exact solution may vary depending on your specific setup and configuration. If none of the above solutions work, you might need to investigate further or seek assistance from the server administrator or the SSL certificate provider to ensure the SSL certificate is correctly installed and trusted.

k0nanvarvar
  • 25
  • 1
  • Was this generated by [ChatGPT](https://meta.stackoverflow.com/questions/421831/temporary-policy-chatgpt-is-banned?cb=1)? – Peter Mortensen Jun 05 '23 at 09:47
  • As @PeterMortensen mentioned, this answer, along with all 8 of your answers (so far), appears likely to have been written (entirely or partially) by AI (e.g., ChatGPT). Please be aware that [posting of AI-generated content is banned here](//meta.stackoverflow.com/q/421831). If you used an AI tool to assist with any answer, I would encourage you to delete it. – NotTheDr01ds Jun 05 '23 at 23:17
  • **Readers should review this answer carefully and critically, as AI-generated information often contains fundamental errors and misinformation.** If you observe quality issues and/or have reason to believe that this answer was generated by AI, please leave feedback accordingly. The moderation team can use your help to identify quality issues. – NotTheDr01ds Jun 05 '23 at 23:17
  • This answer looks like it was generated by an AI (like ChatGPT), not by an actual human being. You should be aware that [posting AI-generated output is officially **BANNED** on Stack Overflow](https://meta.stackoverflow.com/q/421831). If this answer was indeed generated by an AI, then I strongly suggest you delete it before you get yourself into even bigger trouble: **WE TAKE PLAGIARISM SERIOUSLY HERE.** Please read: [Why posting GPT and ChatGPT generated answers is not currently acceptable](https://stackoverflow.com/help/gpt-policy). – tchrist Jul 03 '23 at 21:42