I think this is expected not to work in general. See these docs, particularly (emphasis mine):
To avoid confusion, it is simplest to use a value which resolves to a single address. It is usually a mistake to use
0.0.0.0as a publish address on hosts with more than one network interface.
If it worked for you in version 6 then that was not by design, but you may have been lucky and got away with it.
That's in addition to what folks have said above: you're using a third-party plugin that mucks around with networking stuff in ways that we do not support or even understand here, but which definitely could explain the fragments of errors you've shared so far. If you can reproduce the problem with the built-in security functionality, after fixing the 0.0.0.0 mistake, then it's more likely we can help.