{record.IP} on cloud host with multinode and loadbalancing...
So at present because of the multinode/loadbalanced setup of my host, all the log entries in the contour admin screens are showing as coming from the same IP, the ip of the external interface on the load balancer.
My host provides a header for the client ip..
In order for this to be correctly logged as the record.IP do I need to add something like this into my custom workflows?
{record.IP} on cloud host with multinode and loadbalancing...
So at present because of the multinode/loadbalanced setup of my host, all the log entries in the contour admin screens are showing as coming from the same IP, the ip of the external interface on the load balancer.
My host provides a header for the client ip..
In order for this to be correctly logged as the record.IP do I need to add something like this into my custom workflows?
Or is there an easier way to override the defaulte REMOTE_ADDR that I presume the ip logger is using?
Thanks for any help
Mike
Comment author was deleted
Nope that would be it
is working on a reply...