Bug ID 643459: Unable to login to BIG-IP Configuration Utility when BIG-IP is behind a Reverse proxy

Last Modified: Sep 13, 2023

Affected Product(s):
BIG-IP TMOS(all modules)

Known Affected Versions:
11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 11.6.0, 11.6.1, 11.6.2, 11.6.3,,,,, 11.6.4, 11.6.5,, 12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2, 12.1.0, 12.1.1, 12.1.2, 12.1.3,,,,,,,, 12.1.4,, 12.1.5,, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1

Fixed In:

Opened: Feb 06, 2017

Severity: 3-Major

Related Article: K81809012


When a BIG-IP management interface is accessed through a Reverse Proxy, you are not able to log in to the Configuration Utility. Instead you will see a login error, as the Reverse Proxy IP/hostname is in the Referer header instead of that of the BIG-IP.


You are unable to login to the Configuration Utility.


You are accessing the BIG-IP Configuration Utility through a Reverse Proxy.


Configure their Reverse Proxy to place the IP address of the BIG-IP in the Referer header.

Fix Information


Behavior Change

Customers who are utilizing the BIG-IP Configuration Utility behind a reverse proxy that does not transparently set the Referer header will be unable log in. Prior to the change, there were no restrictions on logging in.

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips