LiveKit Server Startup Error: Secret Key Length and Redis Connection Issues

[cubxxw]

Hello LiveKit team,

I'm encountering a couple of issues when trying to start the LiveKit server on my environment. Below are the error logs and details regarding the issues:

1. Secret Key Length Error

   • During the startup, the LiveKit server logs an error related to the secret key length being too short. The exact log message is as follows:

     2024-03-17T04:59:09.818Z ERROR livekit config/config.go:668 secret is too short, should be at least 32 characters for security {"apiKey": "apioenimkey"}
     

   • It seems that the validation step for the secret/API key requires it to be at least 32 characters long. However, I'm unsure if this requirement has changed recently or if there's a specific format the key needs to follow.

2. Redis Connection Refused

   • Following the secret key length error, there's also an issue with connecting to Redis. The log indicates that the connection is refused:

     2024-03-17T04:59:09.820Z INFO livekit redis/redis.go:133 connecting to redis {"simple": true, "addr": "172.20.189.167:6379"}
     unable to connect to redis: dial tcp 172.20.189.167:6379: connect: connection refused
     

   • This issue occurs despite the Redis server being up and running, and accessible from other services within the same network.

I would appreciate any guidance or recommendations on resolving these issues. Specifically, I'm looking for:

• Confirmation on the secret/API key length requirement and any format it needs to comply with.
• Suggestions on troubleshooting the Redis connection issue, considering the server is operational and there haven't been recent changes to its configuration or network access rules.

[susanto-tm]

@cubxxw Did you figure out what went wrong in your setup for Redis connection?