lukejacksonn / lukejacksonn/servor

`sudo servor --secure` throws `EACCES: permission denied`

Open
#59 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
1.1k
Forks
68
PR merge metrics
No merged PRs in 30d

Description

I'm trying to [install the certs](https://www.npmjs.com/package/servor#adding-credentials-to-the-trusted-store) so that I won't see the "⚠️ Your connection is not private" screen.

I ran `sudo npm i -g servor` then `sudo servor --secure`, and it threw and error saying

```
(node:4316) UnhandledPromiseRejectionWarning: Error: EACCES: permission denied, uv_cwd
at module.exports (/Users/me/.nvm/versions/node/v10.20.1/lib/node_modules/servor/servor.js:38:58)
at process._tickCallback (internal/process/next_tick.js:68:7)
at Function.Module.runMain (internal/modules/cjs/loader.js:834:11)
at startup (internal/bootstrap/node.js:283:19)
at bootstrapNodeJSCore (internal/bootstrap/node.js:623:3)
(node:4316) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
(node:4316) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
```

I'm on macOS Catalina 10.15.5 (19F96).
`npm -v` 6.14.4
`node -v` v10.20.1
`servor` 4.0.2

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at servor.js:38, where the stack trace reports the EACCES uv_cwd failure, and reproduce `sudo servor --secure` with the reported Node.js 10.20.1, npm 6.14.4, and macOS Catalina versions. Check the secure certificate-installation path described in the issue. Done means the command no longer throws the permission error and the reported secure-server flow works.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, node.js
Domain
cli, security
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.