3 months ago
i created a lanyard service via the template
the first error i got was no redis tag existed for the redis image, which i updated to a tag that was as close to the one in the template
now lanyard keeps crashing and because i cannot see the template and all the variable are inferred i am completely at a loss as to how to fix this.
1 Replies
3 months ago
Right now the main problem is that the service is just “crashing” without you being able to see why. The Redis tag mismatch was one issue, but there’s almost certainly a second one in the logs.
I’d suggest:
Open the lanyard service → Deployments → click the latest failed deploy and copy the last 30–50 lines of logs.
Do the same for the Redis service and confirm it’s actually running and listening (no auth errors, no “unsupported Redis version” messages).
In lanyard’s Variables, make sure the Redis connection matches the docs:
REDIS_HOST set to your Redis service host (or REDIS_URL if the template uses that).
Any password/port variables filled from the Redis service (for example REDISHOST, REDISPORT, REDISPASSWORD style).
Then post the exact crash log line here (or in the thread) once the error message is visible, it will be possible to say whether it’s a Redis auth/version problem, a missing env var (like BOT_TOKEN), or something else in the template.