Troubleshooting asset enrollment issues: no node key found

Troubleshooting asset enrollment issues: no node key found

Issue


Asset enrollment failing with following error


W0620 14:24:50.646996 2959106944 tls_enroll.cpp:68] Failed enrollment request to https://<cust>.uptycs.io/agent/enroll (No node key returned from TLS enroll plugin) retrying...

W0620 14:24:54.721276 2959106944 system.cpp:305] Host identifier: <Host ID> 

W0620 14:24:54.723307 2959106944 system.cpp:305] Host identifier: <Host ID>

I0620 14:24:54.724246 2959106944 tls.cpp:242] TLS/HTTPS POST request to URI: https://<cust>.uptycs.io/agent/enroll 

I0620 14:24:54.724304 2959106944 tls.cpp:244] Content size: 1332

E0620 14:24:55.913533 2959106944 init.cpp:590] Cannot activate tls config plugin: No node key, TLS config failed. 


Root cause / Resolution


If the same asset was enrolled on a different tenant, and if the asset was not deleted on the earlier tenant before being registered on the new tenant, it would result in this issue. Deleting the asset from old tenant would resolve this issue.

    • Related Articles

    • OSquery enrollment issues - Fresh installation

      Below are a few guidelines to troubleshoot osquery communication issues.  Upon osquery fresh installation if you are not seeing the  asset online in uptycs portal, please follow below steps.  1)Asset Group Access: Check the asset group of the ...

    • Query failed: Cannot get size of unbound VARCHAR

      Error Query failed (#xxxxxxxx_xxxxxx_xxxxx_xxxxx): Cannot get size of unbound VARCHAR Solution Cast the column as a varchar e.g. cast(indicator as varchar(50))

    • Enable verbose level logging and Core Dump Creation in OSQuery Sensor

      To Collect additional Verbose level logs and Enable TLS level Core dump and OSsquery Dump, below flags should be set in osquery.flags file. This configuration should be used only during Debug and Troubleshooting session, once its completed, these ...