Forum Discussion

merlin87's avatar
merlin87
Icon for Altocumulus rankAltocumulus
Oct 02, 2024

BIGIP Next - SHARED-00001: Internal server error

In the process of setting up a BIGIP Next Lab on 20.2. After getting the CM and two Instances deployed and the  two instances pulled into CM. I get this error when trying to look at details of either...
BIGIPNEXT
kvm
next
  • merlin87's avatar
    merlin87
    Oct 21, 2024

    This ended up being resolved by using the ip address of the instance instead of the FQDN when pulling the instanced into CM. Appearently even after running the setup script locally on the instance where it asks for the hostname, the device certificate is still only generated for the mgt ip address. So after you add the instance to CM and try to get to the edit panels which uses the the "onboarding" path to the instance API call, TLS ends up being broken as all the API calls from CM are using the FQDN which the device certificate in that situation does not match.

merlin87's avatar
merlin87
Icon for Altocumulus rankAltocumulus
Oct 10, 2024

Digging into this more using Postman with barrier token calling the manifest path (/api/device/v1/inventory/xxxxxxxxx/onboarding-manifest), seem to be getting a TLS error. But that did not show up when the instance was originally added only when you try and edit the details of the instance.