There is a

file in the config.example.jsghost file directory to configure related parameters:

config = {
    // ### Production
    // When running Ghost in the wild, use the production environment.
    // Configure your URL and mail settings here
    production: {
        ......
        },

        server: {
            host: '0.0.0.0',
            port: '2368'
        }
    },

The core of the problem lies in the configuration of the server item. The default is localhost好像，一般主机默认的localhost是和127.0.0.1对应的（你也可以在/etc/hosts修改）。localhost是一个伪造的ip，只能本机访问。0.0.0.0类似通配符*, which can match any IP. See this answer for details.

So you should modify the configuration items of config.example.js and change the address bound to the server to 0.0.0.0.

Finally, I also made a ghost docker image, and also used the proxy configured by nginx. Let's Encrypt is used to encrypt https, you can refer to the following:

• Docker image:qBlog

• my blog

No one answered. I also encountered the same problem. The nginx image I made myself also has an EXPOSE port in the Dockerfile. When running the image, even if the -p parameter is not used, the image service can be accessed through the IP of the host. , and none of them take effect when the -p parameter is specified to open port mapping. Mark it, I’ll look for the answer first