Skip to content

Cannot read property 'config' of undefined

Solved Configure
1 1 629 1
  • I’ve seen plenty of useless error messages over my career in IT, but this one really takes the p…

    After recovering my Ghost blog, I was met with the below error

    sudonix@vps:~/domains/content.sudonix.com/public_html$ ghost start
    ✔ Checking system Node.js version - found v14.18.1
    ℹ 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
    ✖ Starting Ghost: content-sudonix-com
    A GhostError occurred.
    
    Message: Ghost was able to start, but errored during boot with: Cannot read property 'config' of undefined
    
    Debug Information:
        OS: Ubuntu, v20.04.3 LTS
        Node Version: v14.18.1
        Ghost Version: 4.22.4
        Ghost-CLI Version: 1.18.0
        Environment: production
        Command: 'ghost start'
    
    Additional log info available in: /home/sudonix/.ghost/logs/ghost-cli-debug-2021-11-22T11_29_19_297Z.log
    
    Try running ghost doctor to check your system for known issues.
    

    Now let’s be 100% transparent here. This error message means nothing to nobody, isn’t documented anywhere on the Ghost forums, and is as much use as a chocolate fireguard.

    I was ready to throw in the towel and choose another platform, then it suddenly dawned on me that I’m not using the default Casper theme, but Leibling, which of course, is missing. I downloaded this, and extracted it to the themes directory, and lo and behold…

    sudonix@vps:~/domains/content.sudonix.com/public_html$ ghost start
    ✔ Checking system Node.js version - found v14.18.1
    ℹ 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
    ✔ Starting Ghost: content-sudonix-com
    
    ------------------------------------------------------------------------------
    
    Your admin interface is located at:
    
        https://content.sudonix.com/ghost/
    
    sudonix@vps:~/domains/content.sudonix.com/public_html$
    

    Something to bear in mind in case you run across the same issue.

    Shame on 👻 for not being more specific around the true origin of this error.

  • phenomlabundefined phenomlab has marked this topic as solved on

Did this solution help you?
Did you find the suggested solution useful? Support 💗 Sudonix with a coffee
If your organisation needs deeper expertise around infrastructure, security, or technology leadership, learn more about Phenomlab Ltd. Many of the deeper technical guides behind Sudonix are published there.

Related Topics
  • Test of youtube embeds

    Solved Configure nodebb
    14
    11 Votes
    14 Posts
    2k Views
    @phenomlab Perfect!!! Many thanks.
  • Pulling YouTube videos using RSS

    Configure rss youtube rsshub
    5
    7
    6 Votes
    5 Posts
    1k Views
    The perfect solution and walkthrough Mark, appreciated as always!
  • How to deploy WordPress.org Developer theme

    Solved Configure wordpress theme github
    4
    1 Votes
    4 Posts
    1k Views
    @Hari the real issue here is that I don’t think it can be used as a theme for WordPress because of the dependencies it clearly has, including its own Web server. My view here is that this is designed to be a complete development environment outside of the WordPress core.
  • Getting Eror When Started NodeBB

    Solved Configure bug
    7
    1
    2 Votes
    7 Posts
    1k Views
    @phenomlab yes i did. i deleted one of plugin then it started to work normally.
  • Code block hard to read with light theme

    Solved Configure
    9
    1
    2 Votes
    9 Posts
    1k Views
    @Panda I see why - if you check the browser console, there’s an error logged there. This is from one of my VM’s [image: 1690893082873-f796eebd-dfde-4938-8945-b08da51bf509-image.png] There is a decision tree that pulls the value of the editor theme from the saved browser settings on each load, but that fails if the theme has never been changed, and the user has the default (in your case, you are using light mode, so it serves “flatly” by default, but the editor itself is never set and returns null This below code changes that /* If savedTheme is undefined it will return null - based on this, we assume that the user has the default theme selected and never changed it, so we'll need to force that here */ if(!savedTheme) { var savedTheme = "flatly"; } If you reload your browser and test again, it should work properly.
  • Email Server Settings

    Solved Configure mx entry
    25
    10 Votes
    25 Posts
    4k Views
    @Onix said in Email Server Settings: If anyone has long-term experience with self-hosted SMTP + DNS set-ups that remain stable, would be great to hear which configurations worked best. I can help with this
  • Is there any way to disable 'register' on the login page?

    Solved Configure
    8
    3 Votes
    8 Posts
    2k Views
    @qwinter yep, knew it was there somewhere
  • nginx can't start again

    Moved Solved Configure nginx server error
    20
    2 Votes
    20 Posts
    3k Views
    @elhana-fine Yes that will happen of course if you still choose to restart the NGINX service after making a change and the test fails. The test on it’s own will state the error and the line number allowing you to fix that first