Skip to content
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.

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

Local Ghost Installation Permission Issue #1809

Closed
4 tasks done
ManaSiWibi opened this issue Nov 21, 2023 · 1 comment
Closed
4 tasks done

Local Ghost Installation Permission Issue #1809

ManaSiWibi opened this issue Nov 21, 2023 · 1 comment
Labels

Comments

@ManaSiWibi
Copy link

ManaSiWibi commented Nov 21, 2023

Summary

ghost start gives permission error. I just posting this in case it's a ghost-related issue, I'm not quite sure if it's my environment that is causing the problem.

Related issue: #1606

Steps to Reproduce

  1. ghost install local
  2. ghost stop
  3. ghost start

Note: starting using ghost restart able to make ghost run. I installed node via nvm.

Log file

✖ Checking system Node.js version - found v18.18.2
ℹ Ensuring user is not logged in as ghost user [skipped]
ℹ Checking if logged in user is directory owner [skipped]
✔ Checking current folder permissions
✔ Validating config
✔ Checking memory availability
✔ Checking binary dependencies
One or more errors occurred.

1) SystemError

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

Technical details

Debug Information:
    OS: Fedora Linux, v39
    Node Version: v18.18.2
    Ghost Version: 5.74.0
    Ghost-CLI Version: 1.25.3
    Environment: development
    Command: 'ghost start'

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
Copy link

Our bot has automatically marked this issue as stale because there has not been any activity here in some time. The issue will be closed soon if there are no further updates, however we ask that you do not post comments to keep the issue open if you are not actively working on a PR. We keep the issue list minimal so we can keep focus on the most pressing issues. Closed issues can always be reopened if a new contributor is found. Thank you for understanding 🙂

@github-actions github-actions bot added the Stale label Mar 20, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant