[Bug] start-server.sh fails to start a tls-secured server

[mdcarlson]

What are you really trying to do?

I am working through the tls-simple samples in order to better understand changes that are required to adapt the other Java samples to run on Temporal Cloud.

Describe the bug

I am following the instructions for the tsl-simple sample. I generated new certs with the indicated script and then executed the 'start-server.sh' script to start a tls-secured local server which uses docker-compose.

The server fails to start which results in a connection refused error when attempting the temporal cli commands in the instructions.

Error Log
start-temporal-tls.log

Minimal Reproduction

1. Execute generate-test-certs.sh
2. Execute start-server.sh
3. Server fails to start with multiple errors (see attached error log)

Environment/Versions

• OS and processor: M3 Mac with Mac OS Sonoma 14.4.1
• Temporal Version: temporal version 0.11.0 (server 1.22.4) (ui 2.21.3)
• Are you using Docker or Kubernetes or building Temporal from source? Docker-compose from provided yml file in samples-server/tls/tls-simple

Additional context

The default docker-compose example works correctly on this laptop.

[mdcarlson]

In further testing with other yml files in the docker-compose example folder, I noticed that while the docker-compose-cass-es.yml file worked, the docker-compose-cass.yml failed with similar errors to the ones seen in the start-server.sh script linked above.

I did attempt to further isolate the problem using the docker-compose-tls.yml sample but that also failed with a different error.

[jmbarzee]

Thank you for submitting this issue. This should be fixed with #109.