Skip to content

docs: mention allow-insecure troubleshooting #2747

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
zaidazmi wants to merge 1 commit into from
Closed

docs: mention allow-insecure troubleshooting #2747

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -301,6 +301,10 @@ aem up

Either approach will make Node.js trust the server certificate and `aem up` should work.

If you need a temporary workaround while you obtain the CA certificate, you can run
`aem up --allow-insecure` to skip certificate verification for server requests. Use
this only as a last resort because it disables TLS certificate validation.

## `npm install` fails with `File exists: /opt/homebrew/bin/hlx`

If you try to install `@adobe/aem-cli`:
Expand All @@ -321,4 +325,3 @@ To solve, first uninstall the old version, then install again with the new name:
npm uninstall -g @adobe/helix-cli
npm install -g @adobe/aem-cli
```