404 Error in Blog after Installation. Can´t connect to the bootstrap socket

#1

Hello, this is my first post, I hope you can help me with this issue.

After an apparently correct installation of the Ghost 2.16.3 version with Ghost-CLI, when I try to access the url of my new blog, it shows a 404 error page.

During the installation I have omitted the configuration of Nginx and SSL, I have indicated my own database user and my own database already created since i had permissions issues. When checking the database I have seen that the tables have been created correctly by the installer. The configuration of config.production.json is correct as well, coinciding with the url and database data that had been configured.

When I use the ghost start command, it tells me that Ghost is running:

seogea@vultr:/var/www/ghost$ ghost start

  • sudo systemctl is-active ghost_seogea-pro

Ghost is already running! For more information, run:

ghost ls

With ghost ls I get this message where it seems to be all right, but when I try to access the url it always gives me an error 404

seogea@vultr:/var/www/ghost$ ghost ls

  • sudo systemctl is-active ghost_seogea-pro
    ââââââââââââââ¬âââââââââââââââââ¬ââââââââââ¬âââââââââââââââââââââââ¬ââââââââââââ ââââââââââââââ¬âââââââ¬ââââââââââââââââââ
    â Name â Location â Version â Status â URL â Port â Process Manager â
    ââââââââââââââ¼âââââââââââââââââ¼ââââââââââ¼âââââââââââââââââââââââ¼ââââââââââââ ââââââââââââââ¼âââââââ¼ââââââââââââââââââ¤
    â seogea-pro â /var/www/ghost â 2.16.3 â running (production) â https://seogea. pro/blog â 2368 â systemd â
    ââââââââââââââ´âââââââââââââââââ´ââââââââââ´âââââââââââââââââââââââ´ââââââââââââ ââââââââââââââ´âââââââ´ââââââââââââââââââ

And if I stop it with ghost stop and then start it again, I have this result:

seogea@vultr:/var/www/ghost$ ghost stop

  • sudo systemctl is-active ghost_seogea-pro
  • sudo systemctl stop ghost_seogea-pro
    â Stopping Ghost
    seogea@vultr:/var/www/ghost$ ghost start
  • sudo systemctl is-active ghost_seogea-pro
    â 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_seogea-pro
    â Validating config
    â Checking folder permissions
    â Checking file permissions
    â Checking content folder ownership
    â Checking memory availability
  • sudo systemctl start ghost_seogea-pro
    â Starting Ghost
  • sudo systemctl is-enabled ghost_seogea-pro

Your admin interface is located at:

https://seogea.pro/blog/ghost/

But the 404 error in this url remains.

When observing the logs, I can see how there are several errors that are repeated:

{“name”:“Log”,“hostname”:“vultr.seogea”,“pid”:8705,“level”:30,“msg”:"Your blog is now available on https://seogea.pro/blog/ ",“time”:“2019-03-05T16:16:19.744Z”,“v”:0}
{“name”:“Log”,“hostname”:“vultr.seogea”,“pid”:8705,“level”:30,“msg”:"Ctrl+C to shut down ",“time”:“2019-03-05T16:16:19.744Z”,“v”:0}
{“name”:“Log”,“hostname”:“vultr.seogea”,“pid”:8705,“level”:30,“msg”:"Ghost boot 4.135s ",“time”:“2019-03-05T16:16:19.791Z”,“v”:0}
{“name”:“Log”,“hostname”:“vultr.seogea”,“pid”:8705,“level”:30,“msg”:"Bootstrap client was closed. ",“time”:“2019-03-05T16:16:19.792Z”,“v”:0}
{“name”:“Log”,“hostname”:“vultr.seogea”,“pid”:1639,“level”:40,“msg”:"Theme’s file locales/en.json not found. ",“time”:“2019-03-05T16:22:02.715Z”,“v”:0}
{“name”:“Log”,“hostname”:“vultr.seogea”,“pid”:1639,“level”:30,“msg”:"Ghost is running in production… ",“time”:“2019-03-05T16:22:10.353Z”,“v”:0}
{“name”:“Log”,“hostname”:“vultr.seogea”,“pid”:1639,“level”:30,“msg”:"Your blog is now available on https://seogea.pro/blog/ ",“time”:“2019-03-05T16:22:10.355Z”,“v”:0}
{“name”:“Log”,“hostname”:“vultr.seogea”,“pid”:1639,“level”:30,“msg”:"Ctrl+C to shut down ",“time”:“2019-03-05T16:22:10.356Z”,“v”:0}
{“name”:“Log”,“hostname”:“vultr.seogea”,“pid”:1639,“level”:40,“msg”:"Can’t connect to the bootstrap socket (localhost 8000) ECONNREFUSED ",“time”:“2019-03-05T16:22:10.385Z”,“v”:0}
{“name”:“Log”,“hostname”:“vultr.seogea”,“pid”:1639,“level”:40,“msg”:"Tries: 0 ",“time”:“2019-03-05T16:22:10.387Z”,“v”:0}
{“name”:“Log”,“hostname”:“vultr.seogea”,“pid”:1639,“level”:40,“msg”:"Retrying… ",“time”:“2019-03-05T16:22:10.388Z”,“v”:0}
{“name”:“Log”,“hostname”:“vultr.seogea”,“pid”:1639,“level”:40,“msg”:"Can’t connect to the bootstrap socket (localhost 8000) ECONNREFUSED ",“time”:“2019-03-05T16:22:10.540Z”,“v”:0}
{“name”:“Log”,“hostname”:“vultr.seogea”,“pid”:1639,“level”:40,“msg”:"Tries: 1 ",“time”:“2019-03-05T16:22:10.540Z”,“v”:0}
{“name”:“Log”,“hostname”:“vultr.seogea”,“pid”:1639,“level”:40,“msg”:"Retrying… ",“time”:“2019-03-05T16:22:10.540Z”,“v”:0}
{“name”:“Log”,“hostname”:“vultr.seogea”,“pid”:1639,“level”:40,“msg”:"Can’t connect to the bootstrap socket (localhost 8000) ECONNREFUSED ",“time”:“2019-03-05T16:22:10.692Z”,“v”:0}
{“name”:“Log”,“hostname”:“vultr.seogea”,“pid”:1639,“level”:40,“msg”:"Tries: 2 ",“time”:“2019-03-05T16:22:10.692Z”,“v”:0}
{“name”:“Log”,“hostname”:“vultr.seogea”,“pid”:1639,“level”:40,“msg”:"Retrying… ",“time”:“2019-03-05T16:22:10.692Z”,“v”:0}
{“name”:“Log”,“hostname”:“vultr.seogea”,“pid”:1639,“level”:40,“msg”:"Can’t connect to the bootstrap socket (localhost 8000) ECONNREFUSED ",“time”:“2019-03-05T16:22:10.845Z”,“v”:0}
{“name”:“Log”,“hostname”:“vultr.seogea”,“pid”:1639,“level”:30,“msg”:"Ghost boot 46.966s ",“time”:“2019-03-05T16:22:10.846Z”,“v”:0}

Can’t connect to the bootstrap socket (localhost 8000) ECONNREFUSED

And

Theme’s file locales/en.json not found.

But I do not know how to solve the 404 error problem in the blog url configured in the installation.

When I launch ghost doctor with the app stopped:

seogea@vultr:/var/www/ghost$ ghost stop

  • sudo systemctl is-active ghost_seogea-pro
  • sudo systemctl stop ghost_seogea-pro
    â Stopping Ghost
    seogea@vultr:/var/www/ghost$ ghost doctor
    â Checking system Node.js version
    â 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 operating system compatibility
    â Checking for a MySQL installation
  • sudo systemctl is-active ghost_seogea-pro
    â Validating config
    â Checking folder permissions
    â Checking file permissions
    â Checking content folder ownership
    â Checking memory availability

I hope you can help me. Thank you!

#2

The 404 error you’re getting is not Ghost’s 404 error, which means you haven’t configured your reverse proxy properly

#3

Usually only occurs if you execute ghost run.

#4

OK @vikaspotluri123, now I am figure out how I can configure the reverse proxy manually in apache to get it working.

But when I run the ghost run command i get this error:

seogea@vultr:/var/www/ghost$ ghost run
The ghost run command is used by the configured Ghost process manager and for debugging. If you’re not running this to debug something, you should run ghost start instead.

  • sudo node current/index.js
    [2019-03-05 19:26:19] WARN Theme’s file locales/en.json not found.
    [2019-03-05 19:26:19] ERROR

NAME: InternalServerError
MESSAGE: (EADDRINUSE) Cannot start Ghost.

level:normal

“Port 2368 is already in use by another program.”
“Is another Ghost instance already running?”
InternalServerError: (EADDRINUSE) Cannot start Ghost.
at new GhostError (/var/www/ghost/versions/2.16.3/core/server/lib/common/errors.js:10:26)
at Server. (/var/www/ghost/versions/2.16.3/core/server/ghost-server.js:79:30)
at emitOne (events.js:116:13)
at Server.emit (events.js:211:7)
at emitErrorNT (net.js:1380:8)
at _combinedTickCallback (internal/process/next_tick.js:139:11)
at process._tickCallback (internal/process/next_tick.js:181:9)

seogea@vultr:/var/www/ghost$ ghost start

  • sudo systemctl is-active ghost_seogea-pro

Ghost is already running! For more information, run:

ghost ls

So I don´t know how to proceed now…

#5

The error shows that Ghost is already running, meaning you don’t need to do anything with your Ghost installation. Now you need to focus on figuring out how to make sure requests to /blog are proxied to 127.0.0.1:2368

#6

Hello! Apologies for the delay, I’ve been somewhat busy.

Just inform you that I have finally managed to configure the reverse proxy in apache. Now I have the active blog in the public url:

Thank you very much for your help

1 Like
closed #7

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.