A new Flexera Community experience is coming on November 25th. Click here for more information.

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Unable to configure beacon in flexera one

Hi Team,

I am unable to configure beacon in flexera one.

The prerequisites all done, i have checked. 

The client is using proxy.

Attached are the screenshot for your reference.

Someone suggest me to add checkcertificate servercertification in registry editor. There is some issues in registry

However, I do not know how to add and where to add in registry.

Kindly help me its very important.

Awaiting your kind responses.

I hope i will get quick responses.

 

 

 

Regards,

Rahul Ranjan

(1) Solution
tjohnson1
By Technical Writer
Technical Writer

The registry keys to disable the certificate checks are 

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ManageSoft Corp\ManageSoft\Common\CheckServerCertificate
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ManageSoft Corp\ManageSoft\Common\CheckCertificateRevocation

You would set both to false. This should be a temporary workaround while you correct the errors regarding the certificate. 

You will want to download and install the ISRG Root X1 certificate (https://letsencrypt.org/certificates/) and the Starfield Services Root Certificate Authority - G2 certificate (https://www.amazontrust.com/repository/to the Trusted Root Certificate store for the local machine. You will also need to make sure that the beacon can reach the following URLs.

I have also seen that sometimes you need to stop and then start (not just restart) the FlexNet Beacon Engine Service to allow the revocation checks to pass after initially failing.

View solution in original post

(1) Reply
tjohnson1
By Technical Writer
Technical Writer

The registry keys to disable the certificate checks are 

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ManageSoft Corp\ManageSoft\Common\CheckServerCertificate
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ManageSoft Corp\ManageSoft\Common\CheckCertificateRevocation

You would set both to false. This should be a temporary workaround while you correct the errors regarding the certificate. 

You will want to download and install the ISRG Root X1 certificate (https://letsencrypt.org/certificates/) and the Starfield Services Root Certificate Authority - G2 certificate (https://www.amazontrust.com/repository/to the Trusted Root Certificate store for the local machine. You will also need to make sure that the beacon can reach the following URLs.

I have also seen that sometimes you need to stop and then start (not just restart) the FlexNet Beacon Engine Service to allow the revocation checks to pass after initially failing.