Redis Auth/Password Traccar Config Option Question

First off all, hope everyone had a peaceful Christmas. Now back to work with a question concerning correct redis implementation.

Can someone elaborate why traccar returns the following warning even when we set redis config to not require a password.

2025-12-29 11:42:34  WARN: [Tbcf966d4] error - NOAUTH Authentication required. - JedisAccessControlException (... < RedisBroadcastService:72 < BaseBroadcastService:46 < ConnectionManager:293 < *:279 < *:198 < MainEventHandler:72 < ...)

Redis Config:

requirepass ""
masterauth ""

There seems to be no documented password/auth option for traccar configuration. This is our current config (on node 2):

    <!-- Boardcast Configurations -->
    <entry key='broadcast.type'>redis</entry>
    <entry key='broadcast.address'>redis://xxx.xxx.xxx.xxx:26379</entry>
    <entry key='broadcast.secondary'>true</entry>

Suggestions and hints welcome.

Best,
Christian

It looks like your Redis requires auth. I think you can pass user and password through URL like this:

redis://USERNAME:PASSWORD@host...

Thanks Anton.

I added this and then the server refuses to start with an error. When I remove the user/pass then it's fine but the previously mentioned log warn message. The server fails because of password error, however, the combination is actually correct as you can see from my redis user test.

<entry key='broadcast.address'>redis://tcuser:tcpass@xxx.xxx.xxx.xxx:26379</entry>

Error on start:

     Loaded: loaded (/etc/systemd/system/traccar.service; enabled; preset: enabled)
     Active: activating (auto-restart) (Result: exit-code) since Mon 2025-12-29 12:21:40 HKT; 309ms ago
    Process: 1108972 ExecStart=/opt/traccar/jre/bin/java -jar tracker-server.jar conf/traccar.xml (code=exited, status=1/FAILURE)
   Main PID: 1108972 (code=exited, status=1/FAILURE)

Log:

2025-12-29 13:16:51  INFO: Health check enabled with period 480000
2025-12-29 13:16:51 ERROR: Main method error - WRONGPASS invalid username-password pair or user is disabled. - JedisAccessControlException (... < RedisBroadcastService:55 < MainModule:333 < <gener:-1 < *:-1 < ... < ScheduleManager:55 < ...)

The user is added correct with the right credentials and is set to on in redis:

127.0.0.1:6379> ACL GETUSER tcuser
 1) "flags"
 2) 1) "on"
 3) "passwords"
 4) 1) "82b9ed4f4185f2a1fcc06bf1d0fe9b70ad4be97f276e757afe24a2f8c3badd56"
 5) "commands"
 6) "+@all"
 7) "keys"
 8) "~*"
 9) "channels"
10) ""
11) "selectors"
12) (empty array)
127.0.0.1:6379> CONFIG REWRITE
OK
127.0.0.1:6379> EXIT
ubuntu@ip-xxx-xx-x-xxx:~$ redis-cli
127.0.0.1:6379> AUTH tcuser tcpass
OK
127.0.0.1:6379> PING
PONG
127.0.0.1:6379> SET testkey "testvalue"
OK
127.0.0.1:6379> GET testkey
"testvalue"
127.0.0.1:6379> DEL testkey
(integer) 1
127.0.0.1:6379> exit

What am I missing?

Problem solved:

The port was wrong - I used the 26379 Sentinel port instead of the Redis port (6379). So blind - I'll keep testing and revert in case I have any further "blind spots".