This message was deleted.

I always enable default profiles when I want to use custom profiles. But got a simmilar issue at a customer running 13.0 with a profile used to enable ocsp stapling. default profiles also not enabled at that cusomer.

it does seem once you enable the default ssl profile it binds the default frontend/backend ssl profiles to all the ssl entities

yes, correct, you need to create custom profiles for anything you changed on any service or vserver

thanks i will have to test it sounds risky enabling the default ssl profile if its going to overwrite any exisiting ssl profiles i got bound to ssl entities. i can then obviously create some more custom ssl profiles once i enable it and bind those but might require some planning

Definitely create a new profile using the default as a base instead of directly using the default profiles.