Forum Discussion
BIGIP Next - SHARED-00001: Internal server error
- 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.
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.
Thanks for sharing this! Maybe open a support case if you still have not for more permanent solution in the future.
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com