Hi, I’m new to ICG, getting this error, any clues? Could not manager your device because of an internal error 45
igel-community.github.io/IGEL-Docs-v02/Docs/HOWTO-COSMOS/#faq-os-12
Q: Trying to connect OS 12 to UMS using the one-time password method but I get this message: `could not manage your device because of an internal error (#45)`.
A: You may have to create a new endpoint web certificate that has all the IP addresses, Fully Qualified Domain Names, and short names that the device can connect to. Steps:
• Start `UMS Console`
• Open `UMS Administration`
• Select `Global Configuration` > `Certificate Management` > `Web`
• Add new endpoint web certificate with all the IP addresses, fully qualified domain names (FQDN), and short names that the device can connect to
NOTE: `Web Certificates`
• The web certificate is used for the web server port (Default port: 8443)
• This port is used for transferring files to the device, all WebDav actions, interserver communication, the IMI, and the `UMS Web App`.
• Additional details kb.igel.com/endpointmgmt-12.01/en/using-your-own-certificates-for-communication-over-the-web-port-default-8443-77864040.html#UsingYourOwnCertificatesforCommunicationovertheWebPort(Default:8443)-CreatingtheEndCertificates Creating the End Certificates
• raw.githubusercontent.com/IGEL-Community/IGEL-Docs-v02/main/docs/Docs/videos/HOWTO-COSMOS-New_Web_Cert.mp4 Video showing steps to create and enable a new web cert
That is my UMS, am I missing a SN for the ICS itself?
I would first make sure that the following works w/o ICG first.
Q: How do I use `rmagent-register` to register OS 12 device to my UMS?
A: Follow steps to test `rmagent-register`
• Start `UMS Console`
• Open `UMS Administration`
• Select `Global Configuration` > `First-authentication Keys`
• Select `(+)`
• Create `Mass-deployment key` with `First-authentication key` TRY-IGEL
• On IGEL OS 12 open a `Terminal` window as root and type
•
“`rmagent-register -s UMS-SERVER-NAME-OR-IP -p 8443 -a TRY-IGEL“`
In your screenshot of the certs, is that just an endpoint certificate with no root?
You should have a root cert at a minimum.
Also, what does your ICG cert page look like?
strange, tested from my customer and there the LE Root was okay, might be auto imported.
I would break that out into root, int, endpoint cert
The combination is probably giving you problems
Maybe use those for both UMS and ICG to simplify it
@member
but able to scan and add via UMS
That is the IP address of your UMS?
used with rmagent-register?
correct
so rmagent-register do not work, but scan in UMS works and add the device correctly.
That makes sense actually. Did you try correcting the cert chain?
Yeah I tried uninstall ICG, but might need to reinstall both UMS and ICG?
rebuild that is
No, just pull in the full chain in UMS and update the endpoint
at least now it seems ok
let me spin up another VM
Your endpoint cert isn’t nested in your screenshot
it needs to be under the int
Thanks guys, after following @member 3 cert approach, it worked 🙂
Continue reading and comment on the thread ‘Hi, I’m new to ICG, getting this error, any clues? Could not manager your device because of an internal error 45’. Not a member? Join Here!
Learn more, search the IGEL Knowledge Base
Ask a question or comment on the above message thread?
Join or log in to the IGEL Community to ask us anything and meet other IGEL customers, partners, and EUC enthusiasts.Submit a question, or Join Today!