SpaceZorro

Adding RUN mkdir /config/ to the Dockerfile fixes this The config will not persist past container restart though.

``` sftpgo@6b7f0d55fc8c:~$ export SFTPGO_HTTPD__BINDINGS__0__ENABLE_HTTPS=1 sftpgo@6b7f0d55fc8c:~$ export SFTPGO_HTTPD__BINDINGS__0__ADDRESS=sftpgo.foo.com sftpgo@6b7f0d55fc8c:~$ export SFTPGO_HTTPD__BINDINGS__0__PORT=443 sftpgo@6b7f0d55fc8c:~$ sftpgo ping 2025-07-10T00:00:47.289 DBG Health Check URL "https://sftpgo.foo.com:443/healthz" 2025-07-10T00:00:47.442 INF OK ``` if you fix the domain:port to whatever...

You are missing whatever domain name your ssl cert is SFTPGO_HTTPD__BINDINGS__0__ADDRESS=sftpgo.foo.com If you are running behind traefik or something you will have to tweak the port

Are you in docker behind traefik?

Not sure about haproxy but traefik won't expose the service (enable networking) until it is healthy. Here is a healthcheck that exits 0 for the first 60sec (so it's healthy...

We are in the weeds. Your problem is not with sftpgo. If you start a container without reverse proxy's and stuff "ping" works as expected.