Bug ID 932461: Certificate update on the SSL profile server for the HTTPS monitor: BIG-IP does not use the updated certificate.

Last Modified: Jul 11, 2024

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

Known Affected Versions:
13.1.3,,,,,,, 13.1.4,, 13.1.5,, 14.0.0,,,,,, 14.0.1,, 14.1.0,,,,,, 14.1.2,,,,,,,,, 14.1.3,, 14.1.4,,,,,,, 14.1.5,,,,,, 15.0.0, 15.0.1,,,,,,,,,, 15.1.1, 15.1.2,, 15.1.3,, 15.1.4,, 15.1.5,, 15.1.6,, 15.1.7, 15.1.8,,, 15.1.9,, 15.1.10,,,, 16.0.0,, 16.0.1,,, 16.1.0, 16.1.1, 16.1.2,,, 16.1.3,,,,,, 16.1.4,,,, 17.1.0,,,, 17.1.1,,,

Opened: Jul 30, 2020

Severity: 3-Major


When you overwrite the certificate that is configured on the SSL profile server and is used with the HTTPS monitor, the BIG-IP system neither uses a client certificate nor continues to use the old certificate. After you update the certificate, the stored certificate is incremented. However, the monitor log indicates that it is using the old certificate.


The monitor tries to use the old certificate or does not present a client certificate after the update.


--Create a pool with an HTTPS pool member. --Create an HTTPS monitor with a certificate and key. --Assign the HTTPS monitor to the HTTPS pool. --Update the certificate through GUI or TMSH.


Use one of the following workarounds: -- Restart bigd: bigstart restart bigd -- Modify the server SSL profile certificate key. Set it to ‘none’, and switch back to the original certificate key name. The bigd utility successfully loads the new certificate file.

Fix Information


Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips