Hi,
I have deployed FortiWeb in HA mode using the following template:
https://github.com/fortinetsolutions/Azure-Templates/tree/master/FortiWeb/FortiWeb-VariableHA-2-NIC
It's working all fine except in web server logs it's showing ForitWeb internal IP, not Client Public IP. I have tried enabling the option from Server Policy, but after enabling that I can't connect to the WebServer. Is the issue related to Azure Load Balancer which is doing the NAT? Wondering anyone deployed FortiWeb in Azure and can share something.
Thanks
Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
Hi,
If you are enabling the client real IP option in the server policy, then you need to set FortiWeb as the default gateway on the backend server. Instead, you could configure FortiWeb to include X‑Forwarded-For in the HTTP header before traffic is generated to the backend server. for more information and configuration, please refer the following link:
The backend server needs to be configured to read the content in X-forwarded-for header for logging.
I hope this helps.
Regards,
Deepak
Hi,
Pls enable X-Forwarded For on server side and also enable on WAF end you will get Real IP in server logs.
Thanks.
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1516 | |
1013 | |
749 | |
443 | |
209 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.