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...
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.
merlin87Altocumulus
AltocumulusThis 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.
