Interface binding issue as a result of HA setup - VIP / CARP IP.
Redis had been always set to LAN interface in past.
The reason CLI command - redis-server --port 6379 --daemonize yes - had worked is because its implied loopback interface. In Webui not selecting any redis interface also make it also use loopback and work. I assumed like MGT binding it would mean it would listen on all interfaces 0.0.0.0 , not correct. Just leave it with no interface selected.
With the new HA setup, either VIP itself and/or my LAN INT IP NAT config caused this issue.
I have all downstream traffic flowing through fortigate in transparent mode. I have it using LAN VIP IP downstream, rather than LAN INT real IP of each firewall.
Whichever cause with VIP or my NAT, if Opnsense plugins are only thing to use redis - Don't select an interface and use loopback.
Redis had been always set to LAN interface in past.
The reason CLI command - redis-server --port 6379 --daemonize yes - had worked is because its implied loopback interface. In Webui not selecting any redis interface also make it also use loopback and work. I assumed like MGT binding it would mean it would listen on all interfaces 0.0.0.0 , not correct. Just leave it with no interface selected.
With the new HA setup, either VIP itself and/or my LAN INT IP NAT config caused this issue.
I have all downstream traffic flowing through fortigate in transparent mode. I have it using LAN VIP IP downstream, rather than LAN INT real IP of each firewall.
Whichever cause with VIP or my NAT, if Opnsense plugins are only thing to use redis - Don't select an interface and use loopback.
"