Splunk Enterprise

Unable to connect to license master

joe06031990
Communicator

Hi,

 

I am getting the bellow error:

 

editTracker failed, reason='Unable to connect to license master=https://192.168.0.21:8189 Error connecting: SSL not configured on client'

after running:

sudo ./splunk edit licenser-localslave -master_uri https://192.168.0.21:8189

I have tried removing the SSLpassword from  system/local/server.conf however this has not worked.

Thanks

 

Joe

Labels (3)
Tags (2)
0 Karma
1 Solution

codebuilder
Influencer

Unless you explicitly changed it, you'll want to use 8089 for the management port. You might also want to put the URL in ticks, as below.

sudo ./splunk edit licenser-localslave -master_uri 'https://192.168.0.21:8089'

https://docs.splunk.com/Documentation/Splunk/8.2.1/Admin/LicenserCLIcommands

 

----
An upvote would be appreciated and Accept Solution if it helps!

View solution in original post

codebuilder
Influencer

Unless you explicitly changed it, you'll want to use 8089 for the management port. You might also want to put the URL in ticks, as below.

sudo ./splunk edit licenser-localslave -master_uri 'https://192.168.0.21:8089'

https://docs.splunk.com/Documentation/Splunk/8.2.1/Admin/LicenserCLIcommands

 

----
An upvote would be appreciated and Accept Solution if it helps!

joe06031990
Communicator

Thanks for your help, all working now.

0 Karma

codebuilder
Influencer

Happy to help. Glad you got it working!

----
An upvote would be appreciated and Accept Solution if it helps!
0 Karma
Get Updates on the Splunk Community!

Stay Connected: Your Guide to May Tech Talks, Office Hours, and Webinars!

Take a look below to explore our upcoming Community Office Hours, Tech Talks, and Webinars this month. This ...

They're back! Join the SplunkTrust and MVP at .conf24

With our highly anticipated annual conference, .conf, comes the fez-wearers you can trust! The SplunkTrust, as ...

Enterprise Security Content Update (ESCU) | New Releases

Last month, the Splunk Threat Research Team had two releases of new security content via the Enterprise ...