Error just after installing Ghost


I have just finished installing Ghost on a newly created Linode (Nanode). The error shown below appeared at the end of the installation process; however, accessing the url opens the webpage.

  • What’s your URL? This is the easiest way for others to help you

  • What version of Ghost are you using?

$ ghost version
Ghost-CLI version: 1.18.1
Ghost version: 4.25.1 (at /var/www/
  • How was Ghost installed and configured?
    Using the official guide for self-hosting Ghost, as described at " How to install Ghost on Ubuntu"

  • What Node version, database, OS & browser are you using?


$ node -v


mysql -V
mysql  Ver 8.0.27-0ubuntu0.20.04.1 for Linux on x86_64 ((Ubuntu))

OS: Ubuntu 20.04 LTS with no Desktop Environment
Browser on client: Firefox 94.0.2 (64-bit)

  • What errors or information do you see in the console?
☱ Starting Ghost/usr/lib/node_modules/ghost-cli/lib/utils/port-polling.js:68
                    let {message: errMsg} = message.error;

TypeError: Cannot destructure property 'message' of 'message.error' as it is undefined.
    at Server.<anonymous> (/usr/lib/node_modules/ghost-cli/lib/utils/port-polling.js:68:35)
    at Object.onceWrapper (events.js:519:28)
    at Server.emit (events.js:400:28)
    at emitCloseNT (net.js:1677:8)
    at processTicksAndRejections (internal/process/task_queues.js:81:21)
  • What steps could someone else take to reproduce the issue you’re having?
    Follow the exact steps described in the official guide, installing on a Linode “Nanode”.

Is this error going to prevent me from using Ghost?

this error is while updating to 4.25.1 as well. Does not seem to affect functioning till now.

Is this a known bug @Kevin @Kym ? sorry for tagging you, but saw you folks active on some other thread thus.

Hey all! :wave: This is a known bug and is being tracked here. The fix has already been merged into Ghost and it’ll be released soon. If you’re on 4.25.1 and stuck, you can follow the instructions here to rollback. :slightly_smiling_face:

1 Like

This was fixed in v4.26.0 :slightly_smiling_face:

1 Like

I can confirm that, after upgrading to v4.26.1, the error is no longer shown after restarting Ghost.

Thank you for your work.