Forum Discussion
merlin87
Altocumulus
AltocumulusBIGIP 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 instance.
Error: Unable to retrieve this BIG-IP Next instance's creation manifest: SHARED-00001: Internal server error
So far I have not been able to figure what is causing this error. Gone as rebuilt everything with 20.1 and 20.0 versions and the error is still there, just worded differently between the versions. Instance status show Healthy, i am just unable to move on with creating vlans, ha and such because that error message is preventing edit of instance details
Any ideas? I am still new to working with Next so stumbling through were to find logs and such compare to BIGIP Classic :)
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.
merlin87This 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.
- Nikoolayy1
MVP
Thanks for sharing this! Maybe open a support case if you still have not for more permanent solution in the future.
- merlin87
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.
