question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

ghost-cli fails at checking node version

See original GitHub issue

Summary

I’m using Ghost in Github Pages with this tutorial, everything is going fine until a few days ago when I wanted to update the Ghost version ( to Ghost 2, but first needed to be in latest v1 )

Steps to Reproduce

  1. ghost update --v1

Log file

The ghost update --v1 output

Found a development config but not a production config, running in development mode instead
✖ Checking system Node.js version
ℹ Ensuring user is not logged in as ghost user [skipped]
ℹ Checking if logged in user is directory owner [skipped]
✔ Checking current folder permissions
✔ Checking memory availability
One or more errors occurred.

1) SystemError

Message: The path /home/alexarch/ is not readable by other users on the system.
This can cause issues with the CLI, please either make this directory readable by others or install node and Ghost-CLI in another location.

Debug Information:
    OS: linux, v4.18.3-arch1-1-ARCH
    Node Version: v8.9.4
    Ghost-CLI Version: 1.9.1
    Environment: development
    Command: 'ghost update --v1'

Try running ghost doctor to check your system for known issues.

If I run ghost doctor -V

Found a development config but not a production config, running in development mode instead
[15:23:33] Checking system Node.js version [started]
[15:23:33] Checking system Node.js version [failed]
[15:23:33] → The path /home/alexarch/ is not readable by other users on the system.
This can cause issues with the CLI, please either make this directory readable by others or install node and Ghost-CLI in another location.
[15:23:33] Ensuring user is not logged in as ghost user [started]
[15:23:33] Ensuring user is not logged in as ghost user [skipped]
[15:23:33] Checking if logged in user is directory owner [started]
[15:23:33] Checking if logged in user is directory owner [skipped]
[15:23:33] Checking current folder permissions [started]
[15:23:33] Checking current folder permissions [completed]
[15:23:33] Validating config [started]
[15:23:33] Validating config [completed]
[15:23:33] Checking memory availability [started]
[15:23:33] Checking memory availability [completed]
One or more errors occurred.

1) SystemError

Message: The path /home/alexarch/ is not readable by other users on the system.
This can cause issues with the CLI, please either make this directory readable by others or install node and Ghost-CLI in another location.

Debug Information:
    OS: linux, v4.18.3-arch1-1-ARCH
    Node Version: v8.9.4
    Ghost-CLI Version: 1.9.1
    Environment: development
    Command: 'ghost doctor -V'

I can run ghost with ghost run and write and publish without problems with that node version

Technical details

This is automatically output by Ghost-CLI if an error occurs, please copy & paste:

OS: linux, v4.18.3-arch1-1-ARCH
Node Version: v8.9.4
Ghost-CLI Version: 1.9.1
Environment: development

Bug submission checklist

Please fill out this checklist to acknowledge that you followed the requirements to submit a bug report.

  • [ *] Tried to find help in the forum & docs
  • [ *] Checked for existing issues
  • [ *] Attached log file
  • [ *] Provided technical details incl. operating system

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:9 (3 by maintainers)

github_iconTop GitHub Comments

1reaction
vikaspotluri123commented, Feb 6, 2019

@jeremychevallier that definitely seems like a problem! However, this seems to be more of an issue with with nvm rather than the CLI, so you’re more likely to get a helpful response over on the forum 😄

1reaction
acburdinecommented, Aug 21, 2018

@AlexDaciuk took me a minute to figure out what was going on, but I see what the issue is here, and it’s one that I’m working on getting figured out 😄

In the meantime, if you run ghost update --v1 --no-setup-linux-user it should work. It’s definitely a bug though.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Error Ghost invalid version: null - Installation
After updating node to version 14.16.1 and ghost-cli to 1.17.0 Every ghost command like ghost -v, ghost ls, ghost update is giving this...
Read more >
ghost-cli - npm
CLI Tool for installing & updating Ghost. Latest version: 1.23.1, last published: 3 months ago. Start using ghost-cli in your project by ...
Read more >
When I Install ghost with ghost-cli I get error - Stack Overflow
I have a CentOS 7 machine with mysql server and nginx. I installed nodejs with yum install nodejs and ghost- ...
Read more >
Updating Ghost not working - bash: pm2: command not found
I'm trying to update my version of Ghost but get the following error: root@ghost /opt/ghost# su -c "pm2 stop ghost" node bash: pm2:...
Read more >
npm is known not to run on node.js v10.24.1 - You.com
Run into Error: yargs parser supports a minimum Node.js version of 12. I expect to be able to install v1 somehow with the...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found