Skip to content

Cannot read property 'config' of undefined

Solved Configure
  • 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? Why not buy me a coffee? It's a nice gesture, and a great way to show your appreciation 💗

Related Topics
  • Opening links in nodebb widget

    Solved Configure
    6
    4 Votes
    6 Posts
    296 Views

    A more efficient way of including this would be to not over complicate it and leverage a standard iframe (providing the CSP headers of the remote site permit this) like below

    <iframe src="https://www.classmarker.com/online-test/start/?quiz=gag66aea7922f0a5" width="700" height="800"></iframe>

    This works first time every time on your site as intended.

  • Pulling YouTube videos using RSS

    Configure
    5
    6 Votes
    5 Posts
    122 Views

    The perfect solution and walkthrough Mark, appreciated as always!

  • MogoDB v6 to v7 upgrade

    Solved Configure
    5
    1 Votes
    5 Posts
    491 Views

    @Panda if you used the Ubuntu PPA, I think this only goes as far as 6.x if I recall correctly.

  • How to deploy WordPress.org Developer theme

    Solved Configure
    4
    1 Votes
    4 Posts
    401 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
    7
    2 Votes
    7 Posts
    496 Views

    @phenomlab yes i did.

    i deleted one of plugin then it started to work normally.

  • mongodb replica set

    Configure
    11
    2 Votes
    11 Posts
    517 Views

    @veronikya said in mongodb replica set:

    The host’s local dns resolution is not configured. The problem of the host’s hosts being unable to be resolved in docker has been solved. Surprisingly
    Solution:
    Edit the /etc/resovel.conf file
    Add 127.0.0.53

    One immediate issue I can think of here is that editing resolv.conf directly is no longer supported and not recommended (because the changes do not survive a reboot) - unless you install the resolvconf package?

  • Code block hard to read with light theme

    Solved Configure
    9
    2 Votes
    9 Posts
    376 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.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.

  • KeepSolid VPN Unlimited DEAL

    Configure
    53
    18 Votes
    53 Posts
    4k Views

    @JAC said in KeepSolid VPN Unlimited DEAL:

    although all are going to have their own flaws one way or another,

    Exactly that - none of them are going to suit every individual purpose. You have to read the reviews, decide what functionality you need, and then make a judgement call for yourself (and your own unique needs).

    There is no “wrong or right”, although I would steer clear of those that do not have a no-logs policy for privacy reasons alone.