The exact process depends on which context, and how you created the certs in Cribl.For example, in this case I'm in the Leader node context. I created the cert object within cribl. I could very easily navigate to the location on disk and replace the files:

for worker group context, a similar path exists. Swap out the file, commit, deploy.

yes, this is exactly what we did in our DEV environment.

the Private Key file was generated using a script.

the Certificate file was gotten from our CA.

we simply updated the paths.

but for some reason, the process was not the same.

you can replace directly on the FS, then restart the Leader

we got a spinning wheel.

what is FS?

at this point, we are merely trying to get back to the original state. so, any advice on how we can point the TLS settings to the original Private Key and Certificate files would be great.

file system

the config screen can point to anywhere on your system, or to a cribl managed areaif you simply replace the files with the originals & restart, you will be in good shape

i've got about 15 mins if you want to jump on a zoom

yes.

let's jump on a call.

who do i send an e-mail to?

https://cribl.zoom.us/j/83811872421

Regarding the original question .. are you looking for something like this?https://docs.cribl.io/stream/destinations-splunk-lb/#ssl|https://docs.cribl.io/stream/destinations-splunk-lb/#ssl