Hello Ghost Community, I’ve been trying to set up a self-hosted install of Ghost on a Digital Ocean droplet.
I’ve been trying to run the ghost start command and I’ve been getting the following error
The Error
ghost-mgr@ghost-ubuntu-blog:~$ ghost start
+ sudo systemctl is-active ghost_youbiesroom-com
✔ Checking system Node.js version - found v14.18.1
✔ Ensuring user is not logged in as ghost user
✔ Checking if logged in user is directory owner
✔ Checking current folder permissions
+ sudo systemctl is-active ghost_youbiesroom-com
Instance is currently running
ℹ Validating config [skipped]
✔ Checking folder permissions
✔ Checking file permissions
✔ Checking content folder ownership
✔ Checking memory availability
✔ Checking binary dependencies
✔ Checking systemd unit file
✔ Checking systemd node version - found v14.18.1
+ sudo systemctl start ghost_youbiesroom-com
+ sudo systemctl stop ghost_youbiesroom-com
✖ Starting Ghost: youbiesroom-com
A GhostError occurred.
Message: Ghost was able to start, but errored during boot with: ER_ACCESS_DENIED_ERROR: Access denied for user 'ghost'@'localhost' (using password: YES)
Help: Unknown database error
Suggestion: journalctl -u ghost_youbiesroom-com -n 50
Debug Information:
OS: Ubuntu, v20.04.3 LTS
Node Version: v14.18.1
Ghost Version: 4.21.0
Ghost-CLI Version: 1.18.0
Environment: production
Command: 'ghost start'
Additional log info available in: /home/ghost-mgr/.ghost/logs/ghost-cli-debug-2021-12-14T15_09_14_892Z.log
Try running ghost doctor to check your system for known issues.
You can always refer to https://ghost.org/docs/ghost-cli/ for troubleshooting.
ghost-mgr@ghost-ubuntu-blog:~$
Ghost Doctor Output
ghost-mgr@ghost-ubuntu-blog:~$ ghost doctor
✔ Checking system Node.js version - found v14.18.1
✔ Checking logged in user
✔ Ensuring user is not logged in as ghost user
✔ Checking if logged in user is directory owner
✔ Checking current folder permissions
✔ Checking system compatibility
✔ Checking for a MySQL installation
+ sudo systemctl is-active ghost_youbiesroom-com
+ sudo systemctl reset-failed ghost_youbiesroom-com
✔ Validating config
✔ Checking folder permissions
✔ Checking file permissions
✔ Checking content folder ownership
✔ Checking memory availability
✔ Checking binary dependencies
✔ Checking free space
✔ Checking systemd unit file
✔ Checking systemd node version - found v14.18.1
ghost-mgr@ghost-ubuntu-blog:~$
I think it has something to do with my database not being set up correctly? I didn’t know I had to set it up myself and I have no idea as to how to set it up for the site.
Any help is appreciated. If I missed out on some relevant information, please let me know and I’ll try to provide it. Thanks in advance! :)