Yep, there it is. Here’s the fixed version – your nesting was all weird.
{
"url": "https://brianfajardo.com",
"server": {
"port": 2368,
"host": "127.0.0.1"
},
"database": {
"client": "mysql",
"connection": {
"host": "localhost",
"user": "canquillo09",
"password": "SOMETHING",
"database": "brianfajardo_OLDprod"
}
},
"mail": {
"transport": "Direct"
},
"logging": {
"path": "content/logs/",
"useLocalTime": true,
"level": "info",
"rotation": {
"enabled": true,
"count": 15,
"period": "1d",
"transports": [
"file",
"stdout"
]
}
},
"process": "systemd",
"paths": {
"contentPath": "/var/www/brianfajardo/content"
}
}
1 Like
Thank you @Cathy_Sarisky and @vikaspotluri123 for your help!
After editing my weird nesting with the fixed version you provided Cathy, I ran into another error but I was able to fix it on my own by reverting the changes I made to the content folder ownership. I set it back to ghost using sudo chmod -R ghost:ghost content. I was running into a systemd error where ghost would not start at all. I hope the tip I left you helped in some way.
Cheers!
So it seems like the whole problem was a messed up config file? Do you have any sense of how it got messed up? I’m curious if this is user error, or a problem with an update script.
And thanks! Much appreciated. :)
1 Like
Yes, it had to have gotten messed up when I was either adding the staff device verification feature JSON code or when adding the email config. I ended up deleting both since I was dealing with too many things at the same time. I felt I should have first tested adding one piece of the feature I want by stopping ghost and making changes, check if config is ok then start ghost again and if config checks then add the other features I want and so on and so forth. I’ll be sure to use the JSON prettifier you shared with me! 