Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the ad-inserter domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/vhosts/blog.webeats.it/httpdocs/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the cookie-law-info domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/vhosts/blog.webeats.it/httpdocs/wp-includes/functions.php on line 6114
IP reale utente con nginx in reverse proxy con Apache - Blog WebEats

Guida passo-passo su come impostare il passaggio dell’IP del visitatore con Apache 2.4 quando nginx è in modalità reverse proxy.

Apache 2.4 ha il modulo remoteip nativo e rpaf non è più supportato.

Quindi facendo queste piccole modifiche su Ubuntu 14.04 è possibile risolvere il problema del forwarding dell’IP del visitatore quando si usa nginx in modalità reverse proxy.

Rimuoviamo rpaf
# apt-get remove libapache2-mod-rpaf

creiamo il file remoteip.conf
# pico /etc/apache2/mods-available/remoteip.conf

Incolliamo all’interno questo codice
RemoteIPHeader X-Real-IP
RemoteIPInternalProxy 127.0.0.1
RemoteIPInternalProxy xxx.xxx.185.66 // server ip

Nel caso avessimo più indirizzi IP sul nostro server è possibile impostarne più di uno aggiungendoli a RemoteIPInternalProxy
RemoteIPInternalProxy xxx.xxx.102.13 xxx.xxx.102.14 xxx.xxx.102.15

Attiviamo il modulo remoteip nativo in Apache 2.4 e riavviamolo
a2enmod remoteip
service apache2 restart