The Docker container lacks the [system_default_sect] configuration.

[w905581962]

Hello, I deployed zoffline on a Linux server using Docker. After configuring it, I tried to connect using a Windows client but encountered the error message "The underlying connection was closed". Following the documentation, I accessed the container and found that the configuration option [system_default_sect] was not present in the /etc/ssl/openssl.cnf file. I attempted to manually add the configuration, restarted the container, and attempted to connect again from the Windows client, but the issue persisted. Could you please advise me on what to do next?

My client has added the pme and p12 certificates as well as hosts configurations according to the documentation.

Thank you very much, A fellow rider

[fatsbrown]

I don't think the problem is on the Docker image, I'm using the latest and Zwift can connect without issues.

Try running a local host server on Windows just to rule out a client configuration problem.

Which IP did you configure in the Windows hosts file? The Linux host or the container (e.g. 172.17.0.2)?

[w905581962]

Actually, I used a cloud server as the server for zoffline. I also opened the corresponding port in the security group configuration and tested the port using telnet. Of course, the IP address configured in the hosts file on the Windows client is also the internet address of the cloud server. The Docker container was generated using the docker-compose template without any modifications. So I'm also puzzled.

Here is a screenshot of the Docker container logs when accessed from the client side.

[fatsbrown]

This error usually means the SSL certificate is missing in client's cacert.pem.

You can try doing the change in openssl.cnf on the Linux host.

[oldnapalm]

Closing due to lack of activity.