Forum Discussion

mx9's avatar
mx9
Icon for Nimbostratus rankNimbostratus
Nov 08, 2024

DEVICE-0202 Error while adding rSeries as a provider in CM

Hi all,

we just got out rSeries Hardware and I am now trying to add it as a provider to out Central Manager instance.
Unfortunately I am always getting the following error Code when trying to connect it to CM.

DEVICE-0202: BIG-IP Next instance internal server error: Certificate validation failed with error: provider 1234-app123-zz.net.world.aa:8888: DEVICE-0202: BIG-IP Next instance internal server error: SSL certificate is unusable: BIG-IP Next 1234-app123-zz.net.world.aa has an unknown or unusable device certificate; explicit trust is not possible. Error: EOF. .


For creating the Device Cert on the rSeries Platform I used to following KB-Article which is for the DEVICE00060 Error: https://my.f5.com/manage/s/article/K000139300
- I issued a self signed certifcate with DNS and IP as SAN

Since the error didn't change I tried adding a few other things:
- Adding the self signed cert to CentralManager via Applications>Certificates & Keys>import 
- Creating a crt signed by out Internal CA (no IP in SAN cause the CA doesn't allow that), applying it on the rSeries  and uploading the chain to cm
- Testing if the rSeries really uses the applied certs on port 8888 each time with openssl s_client connect which it always does

But all that didn't change the error message at all. Any ideas?

Thank you in advance

central manager
next
rseries
  • CelebratePeak's avatar
    CelebratePeak
    Icon for Nimbostratus rankNimbostratus
    Nov 12, 2024

    It sounds like there might be an issue with your Unity setup or permissions. Here are a few things you can try to fix it:

    1. Run Unity as Administrator: Sometimes, Unity doesn't have the necessary permissions to create folders in certain directories. Right-click the Unity Editor icon and select "Run as administrator" to see if that helps.
    2. Check Folder Permissions: Make sure the "Program Files" folder (C:/Program Files/Unity) has the correct write permissions. You can right-click the folder, go to "Properties," and check the permissions under the "Security" tab.
    3. Try a Different Save Location: It's generally a good idea not to save Unity projects in the "Program Files" folder due to possible permission issues. Try creating the project in a different location, like your "Documents" or "Desktop" folder.
    4. Check for Updates: Unity 2019.3.0a4 is an alpha version, which might have some bugs. You could try updating to a more stable version of Unity if possible.
    5. Clear Cache: Sometimes, clearing the Unity cache can resolve unexpected issues. You can find cache and temporary files in the Unity folder in "AppData" (usually located at C:/Users/[Your Username]/AppData/Local/Unity). 

    Let me know if any of these steps work for you!