Skip to main content
Solved

Cribl Stream: TLS validation error in Splunk UF source after WG

  • Nov 20, 2026 4:54 PM UTC
  • 7 replies
  • 1 view

This message originated from Cribl Community Slack.
Click here to view the original link.

I have an issue that has me bamboozled (does anyone use that word? anyway....) I created a new WG, let’s call it WG2. I migrated the sources, packs, destinations, routes, pipelines and some other configs from one of the current WGs, let’s call that WG1, using basically export/import JSON. I copied the certs from /opt/cribl/groups/WG1/local/cribl/auth/certs to /opt/cribl/groups/WG2/local/cribl/auth/certs. I did a commit and deploy and saw no problems.... except for the Splunk UF for TLS source. The Splunk UF TLS in WG2 source continually shows red with the error “TLS validation error: check for missing passphrase or incorrect certificate key”. This is strange because it’s the exact same cert and config as in WG1 and there is no passphrase for the key. If I add something the other passphrase field, I get “Is the passphrase correct?” If I disable TLS, the source goes green. If I try a different cert with an encrypted key and make sure the passphrase works, I get the same error. If I try a different cert that also does not have a passphrase, I get the same error. I ssh’d to the leader and compared the .key files for the first cert between the two folders and they are the same and neither are encrypted. I checked the .key file that was pushed to the workers and it matches the ones on the leader. I deleted the source and recreated from scratch, then enabled TLS on the recreated source and I got the same error. I can less the .key file and it does not have the ENCRYPTED KEY header or footer. I checked Workgroup Settings - Security - Certificates but there were no stray text entries in the passphrase there, it looks like it matches what is in the Splunk UF TLS source. Is there anything else I can check/try?

Best answer by dbizon539

What version are you on in Cribl? (also as a side note you can clone worker groups instead of moving things over one at a time)
View original

7 replies

  • Employee
  • Answer
  • Nov 20, 2026 4:54 PM UTC
What version are you on in Cribl? (also as a side note you can clone worker groups instead of moving things over one at a time)

  • Author
  • Participating Frequently
  • Nov 20, 2026 4:54 PM UTC
4.19.2

  • Author
  • Participating Frequently
  • Nov 20, 2026 4:54 PM UTC
:facepalm:

  • Employee
  • Nov 20, 2026 4:54 PM UTC
If you go into the source and put the passphrase in and save it and deploy, does it work?

  • Author
  • Participating Frequently
  • Nov 20, 2026 4:54 PM UTC
brb...

  • Author
  • Participating Frequently
  • Nov 20, 2026 4:54 PM UTC
Cloning the WG worked.

  • Author
  • Participating Frequently
  • Nov 20, 2026 4:54 PM UTC
Just to document what I did in case others are wondering: I cloned the WG, deleted all sources, destinations, routes, and pipelines not needed . Manually added one worker to test and then i saw data being processed correctly.