Bug ID 1597037: Adding a new TLS instance to an existing application (a default TLS instance) fails to flow traffic as expected

Last Modified: Oct 19, 2025

Affected Product(s):
BIG_IP_NEXT(VE/HW) TMOS(all modules)

Fixed In:
20.3.0

Opened: Jun 17, 2024

Severity: 1-Blocking

Symptoms

Traffic flow does not work as expected when a new TLS instance is added to an existing application.

Impact

Traffic flow does not work as expected

Conditions

1. Create default SSL certificate and custom certificate from Central Manager UI. 2. Deploy an https application and validate LTM traffic with default certificate. Edit the application to add new certificate for TLS instance under protocols and profiles. 4. Add the imported certificate (custom cert) using "enable https client side" 5. Save the application with new TLS settings and certificate added. 6. Click on Review and deploy. 7. Validate the changes done on application. 8. If validation is successful. Click on deploy application

Workaround

Suggested Workarounds: 1. Delete the existing cert in the UI and recreate the same certificate (either before or after adding new certificate) and save the application. 2. Use API with multiCerts to true for each certificate block.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips