Question on Post Not Found Error and Post published Schedule function

Hello,

The Ghost log usually has this error and I don’t know what is wrong with my website. The address of the website is https://lientam.fi/ and my version is 2.31.1, it is a Digital Ocean container.

The post schedule function doesn’t work also. Maybe two problems have some common?

I hope that someone shows me what I should do to fix this error and also the post published schedule function. Thank you very much.

Hi there, oh dear that doesn’t seem right. Do you mind sharing your configuration file? Censoring any sensitive information :slightly_smiling_face:

Hi, here is the configuration for Production. Basically, everytime I send a get request to a post, the error appear. (But the post is also returned after the error)
{
“url”: “https://lientam.fi”,
“server”: {
“port”: 2368,
“host”: “127.0.0.1”
},
“database”: {
“client”: “mysql”,
“connection”: {
“host”: “localhost”,
“user”: “”,
“password”: “”,
“database”: “”
}
},
“mail”: {
“transport”: “SMTP”,
“options”: {
“service”: “Mailgun”,
“host”: “smtp.eu.mailgun.org”,
“auth”: {
“user”: “”,
“pass”: “”
}
},
“from”: “’”
},
“logging”: {
“transports”: [
“file”,
“stdout”
]
},
“process”: “systemd”,
“paths”: {
“contentPath”: “/var/www/ghost/content”
},
“bootstrap-socket”: {
“port”: 8000,
“host”: “localhost”
}
}

Thanks for sharing those. I’ve spoken with the team and they think it could be a number of things:

  1. Cached API requests
  2. Something blocking Ghost from making network requests to itself
  3. Using a load balancer to run multiple Ghost instances

Do any of these ring a bell? I’m wondering if you have some sort of caching set up that’s affecting API requests as well as files?

Thank you very much. The only cached system I know is Cloudflare but I tried to disable it and the problem is still there. This is only ghost instances I have:
$ ps aux | grep ghost

ghost 6265 0.0 2.4 945720 24288 ? Ssl Sep30 0:00 ghost run
ghost 6298 0.0 23.7 1510584 239256 ? Sl Sep30 4:10 /usr/bin/node c urrent/index.js
root 6672 0.0 0.4 63972 4176 pts/0 S 18:14 0:00 sudo -i -u ghos t-mgr
ghost-m+ 6673 0.0 0.5 23208 5204 pts/0 S 18:14 0:00 -bash
ghost-m+ 6900 0.0 0.3 37792 3244 pts/0 R+ 18:29 0:00 ps aux
ghost-m+ 6901 0.0 0.1 14856 1036 pts/0 S+ 18:29 0:00 grep --color=au to ghost

The second issue is possible. Can you suggest me a way to debug it?

I normally debug this sort of stuff by running the site locally. That to me seems like the easiest way to isolate a Ghost install.