Redis - Security provider sessions across replicas

Wappler General Need Help
1

I'm sure I'm missing something really obvious but I can't seem to get redis to use Security Provider across a project with multiple replicas.

On a single instance, the login system works perfectly when the 'remember me' button is not ticked - 'logging out' at the session expiry

When I use the same service on a target set with replicas and redis, the login succeeds but it seems to only exist on one replica so page reloads and SC calls fail most of the time (redirecting to the login). Because one replica has the session, reloading the page will sometimes recognise the session.

I have redis enabled on the target:

image
image1429×372 11.6 KB

And redis enabled for SC API:
image

And Sessions are set to use redis:
image

And this is when the remember me on login is empty

Any ideas :pray:

2

This looks correct (your config). I seem to recall a post about the latest version of redis being problematic. Maybe taking that back to a known good version will help.

3

I've set the Redis version to 7.0.x (and tried with all the other versions, available in Wappler, too) - I'm getting this in the Redis Logs:

1:C 13 Dec 2024 14:59:38.976 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 13 Dec 2024 14:59:38.976 # Redis version=7.0.15, bits=64, commit=00000000, modified=0, pid=1, just started
1:C 13 Dec 2024 14:59:38.976 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
1:M 13 Dec 2024 14:59:38.976 * monotonic clock: POSIX clock_gettime
1:M 13 Dec 2024 14:59:38.977 * Running mode=standalone, port=6379.
1:M 13 Dec 2024 14:59:38.977 # Server initialized
1:M 13 Dec 2024 14:59:38.977 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
1:M 13 Dec 2024 14:59:38.981 # Can't handle RDB format version 12
1:M 13 Dec 2024 14:59:38.981 # Fatal error loading the DB: Invalid argument. Exiting.
4

Plenty of disk space? I've had problems before when I hadn't pruned and Redis could not start, although I think the error message I had was more direct about it being disk space.

I wonder if you need to completely destroy everything? Can't handle RDB format version 12 makes me think using the latest version originally, left a format that 7.x can't handle. Just guessing here.

5

Ken guessed right, this is a version issue. Ben, change the Redis version in your target settings to e.g. 6

Or you can delete your Redis data volume somehow to start from scratch

6

I think it's there/nearly there

I tried changing the redis versions - <V7 threw the DB version error but in V7.0.x the session still wasn't being shared. I flushed the DB and it now seems to be behaving better. I'll keep playing to test it further but it is looking promising. Thanks chaps!

1 Like