Enable HTTPS when running the docker compose

[martyp187]

Is there a specific way that the .crt and .key files are meant to be included when running the docker container?

I had these on the host and mounted them in via a volume, and set the TLS_CERT_FILE: TLS_KEY_FILE: to the file paths.

It seems the moment I set these the container loops on start, and without TLS working, vPilot will not auth to /api/v1/fsd-jwt

Thanks!

[renorris]

Does the program crash with a stacktrace?

[martyp187]

In short I don't know. I am thinking first to debug that the .crt and .key files are being mounted correctly into the container, but I cannot exec or get to a shell in the container to see anything useful. I don't think the image is built with any way to see this?

If there is a hardcoded requirement for loading the certificates to get TLS working, could it be added to the compose example?

[renorris]

I'm going to need some sort of log or stacktrace or example of your compose file.

See https://docs.docker.com/reference/cli/docker/compose/logs/

[renorris]

You can always run basic HTTP on fsd (no TLS) then proxy the webserver upstream using something like nginx, Caddy or similar—delegating the responsibility of TLS to that layer instead.