'EACCES: permission denied, open '/opt/bitnami/ghost/.ghost-cli''

  • What’s your URL? Not applicable. Encountered an issue during installation.

  • What version of Ghost are you using? 5.60

  • How was Ghost installed and configured?
    AWS Lightsail, v5.60

  • What Node version, database, OS & browser are you using?
    OS: Debian GNU/Linux, v11
    Node Version: v16.20.2
    Ghost Version: 5.60.0
    Ghost-CLI Version: 1.24.2
    Environment: production

I have made several attempts to install Ghost on AWS via Lightsail/Bitnami image and each has failed. I decided to try again with 5.60 and I encountered another failure.

In this case, Ghost initially appears to install correctly. I am able to get to my site’s home page, as well as the admin panel.

However every ghost doctor and ghost restart failed with:
Message: ‘EACCES: permission denied, open ‘/opt/bitnami/ghost/.ghost-cli’’

and ghost ls returned “no instances found” (there is indeed one) and some commands, like ghost restart now fail with A CliError occurred:

Debug Information:
    OS: Debian GNU/Linux, v11
    Node Version: v16.20.2
    Ghost Version: 5.60.0
    Ghost-CLI Version: 1.24.2
    Environment: production
    Command: 'ghost restart'
Message: An unexpected error occurred while stopping Ghost.
Stack: Error: An unexpected error occurred while stopping Ghost.
    at /opt/bitnami/ghost/versions/5.60.0/node_modules/ghost-cli/lib/utils/
local-process.js:124:39
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async LocalProcess.restart (/opt/bitnami/ghost/versions/5.60.0/node_
modules/ghost-cli/lib/process-manager.js:34:9)
    at async Instance.restart (/opt/bitnami/ghost/versions/5.60.0/node_modu
les/ghost-cli/lib/instance.js:353:9)

Original Error Message:
Message: 
    Error: Killing process 1554 failed: kill: (1554): Operation not permitt
ed
        at Array.map (<anonymous>)
        at fkill (/opt/bitnami/ghost/versions/5.60.0/node_modules/fkill/ind
ex.js:12:9)
        at processTicksAndRejections (node:internal/process/task_queues:96:
5)
        at async LocalProcess.restart (/opt/bitnami/ghost/versions/5.60.0/n
ode_modules/ghost-cli/lib/process-manager.js:34:9)
        at async Instance.restart (/opt/bitnami/ghost/versions/5.60.0/node_
modules/ghost-cli/lib/instance.js:353:9)
Stack: AggregateError: 
    Error: Killing process 1554 failed: kill: (1554): Operation not permitt
ed
        at Array.map (<anonymous>)
        at fkill (/opt/bitnami/ghost/versions/5.60.0/node_modules/fkill/ind
ex.js:152:9)
        at processTicksAndRejections (node:internal/process/task_queues:96:
5)
        at async LocalProcess.restart (/opt/bitnami/ghost/versions/5.60.0/n
ode_modules/ghost-cli/lib/process-manager.js:34:9)
        at async Instance.restart (/opt/bitnami/ghost/versions/5.60.0/node_
modules/ghost-cli/lib/instance.js:353:9)
    at fkill (/opt/bitnami/ghost/versions/5.60.0/node_modules/fkill/index.j
s:152:9)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async LocalProcess.restart (/opt/bitnami/ghost/versions/5.60.0/node_
modules/ghost-cli/lib/process-manager.js:34:9)
    at async Instance.restart (/opt/bitnami/ghost/versions/5.60.0/node_modu
les/ghost-cli/lib/instance.js:353:9)

Looking closer, ghost-cli was not marked executable. In the directory that Bitnami installer drops configuration and the CLI tool, I notice that .ghostpid and .ghost-cli are read-only. I can guess what ghostpid is, and I granted execute permissions to ghost-cli (which appears to address the issue), but I still appear to have problems with others and suspect because of my changes that the ghost user no longer is authorized to modify that process. Can anyone help me understand what is wrong with ghost-cli?

Thanks.

If you are getting a permission error on ‘/opt/bitnami/ghost/.ghost-cli, the first things I would check are

whoami

To confirm your current user

And

ls -l /opt/bitnami/ghost/.ghost-cli

To confirm who owns that file and what the perms on it are.