• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Question Domains proxied via Cloudflare - Logs showing Cloudflare IPs rather than client IP

Alban Staehli

Regular Pleskian
Server operating system version
AlmaLinux 8.10 (Cerulean Leopard)
Plesk version and microupdate number
Plesk Obsidian 18.0.70 Update #2
Hi,

I've a couple of domains proxied via Cloudflare. Using the Cloudflare DNS extension to sync these domains NS entries with Cloudflare.
While these are proxied from Cloudflare to the Plesk server, the Nginx and Apache logs show the IP addresses from Cloudflare proxies, rather than the client IP address.

Would you know what has to be done at the Plesk level to enable the use of the Real IP address rather than the Cloudflare one within Apache / Nginx logs for these specific vhosts that are proxied?

I thought this would be handled throught the cloudflare DNS extension, but obviously it's not the case.

Thank you.
 
Back
Top