Redis ElastiCache connection

get-help
1

Hi team, I can’t connect to my elasticache from the lua code (I can connect to my local Redis instance easy):

local redis = require ‘redis’
local conn = redis.open { node = ‘redis://xxx.use2.cache.amazonaws.com’ }
print(conn:query(‘INCRBY’, ‘sent_emails:tenant:’ .. tenant, 1))
print(conn:query(‘INCRBY’, ‘sent_emails:domain:’ .. domain, 1))

Just a regular timeout error:

504 Gateway Time-out

504 Gateway Time-out

I can connect from cli the same machine, no networking or firewall issues:
redis-cli -c -h xxx.use2.cache.amazonaws.com --tls -p 6379

3

You probably want to use rediss:// as the protocol scheme if you want TLS

4

@free-spirited-yorksh I think this is not supported, kumo fails with:

caused by: building redis client RedisConnKey { node: Single(“rediss://xxx.use2.cache.amazonaws.com”), read_from_replicas: false, username: None, password: None, pool_size: None, connect_timeout: None }: can’t connect with TLS, the feature is not enabled

5

Ah, it’s not enabled by default, weird! redis: enable tls support · KumoCorp/kumomta@efddb5b · GitHub turns it on, should be available from our package repos in about an hour

6

@free-spirited-yorksh this is crazy! Thank you so much!!!

7

Sorry @free-spirited-yorksh is that in dev build? I have stable version installed from dnf, how can I get the update?

8

remove the kumomta package and install the kumomta-dev package instead

9

Yeah, I did that, thought any other options. But looks like same issue still with rediss

10

What does kumod --version say?

11

kumod 2024.08.26-3d4a5d21

12

that’s the build before the one with tls enabled. I’d suggest running sudo dnf clean all then sudo dnf update kumomta-dev

13

@free-spirited-yorksh fixed! Thank you again!

14

Hi, I stumbled across this issue using the current docker image that still embeds the 2024.06.10-84e84b89 version. No issue with the kumomta-dev image running 2024.09.20-40938a9c.
Is there a delay in the releases of stable docker images?
https://github.com/kumocorp/kumomta/pkgs/container/kumomta

15

look’s like the latest tag didn’t get updated to point to the later build. You can directly use the latest-arm64 or latest-amd64 as a workaround for the time being

16

That’s it, thanks Wez