UIM 20.3 Operator Console Spinning Forever

[GaryBarber]

Recently upgraded to UIM 20.3.
Created a new VM for CABI 
Deployed the robot and the cabi 4.30 and wasp 20.30 probes to the new VM and configured.
Deployed the dashboard packages to the cabi VM

I can access cabi through https://maas2-cab1:8443 and load the UIM Summary dashboard.

Logging into Operator Console just gives me a spinning icon on the home screen.

[GaryBarber]

I don't know if it's related but my wasp.log is full of:

Nov 04 16:27:38:745 DEBUG [https-jsse-nio-8443-exec-13, com.firehunter.ump.auth.NmsAuth] Failure to decrypt sidjavax.crypto.BadPaddingException: Given final block not properly padded. Such issues can arise if a bad key is used during decryption.
Nov 04 16:27:38:745 DEBUG [https-jsse-nio-8443-exec-13, com.firehunter.ump.auth.NmsAuth] Invalid sid 2f6c624a52566f387378447a6f2f585245796c367248494c314f47475643586e784432515a4b616b4976453d
Nov 04 16:27:38:749 DEBUG [https-jsse-nio-8443-exec-13, com.firehunter.ump.auth.NmsAuth] Authorizing sid 2f6c624a52566f387378447a6f2f585245796c367248494c314f47475643586e784432515a4b616b4976453d for session F5E4F621C884764B6B4F2E683E6097E9

[Garin Walsh]

My logs are full of these messages too - not sure that indicate anything to do with your problem.

The first test is to verify you can reach CABI from your browser - try loading https://ip of cabi/cabijs

[yoni.rozman]

Hi,

what helped for me is 2 things:

1. adding key to both wasp probes (UMP & CABI)

cabi = /hub_domain/hub_hub/cabi_robot/cabi

2.Applying same kind of tomcat SSL certificates on both UMP and CABI wasp probes. Not self-signed but from same Certification Authority.

[Luc Christiaens]

- the cabi server must have a copy of the /nimsoft/security/certificate.pem coming from your main hub
- on the cabi server controller.cfg add a new key:
cryptkey = C:\Nimsoft\security\certificate.pem

[GaryBarber]

That works, and I can see the UIM Summary dashboard in there.

[GaryBarber]

The certificate was added when the robot was installed.

[GaryBarber]

This did the trick. I found I had to add the cabi key to ump_common and setup in raw configure to get it working. Thanks.

[Magen Kamil]

have the same issue... you get it when trying to config https?
how to resolve it?

[Andrew Cooper]

OC server and CABI server need to use the same protocol, ie both using http or both using https, you cannot have OC with https and CABI using http, the OP console will not work

------------------------------
Knows a little about UIM/DXim, AE, Automic
------------------------------