CMS 2.9 - Web App "System is currently unavailable. Please try again later"

[robertb]

I have deployed CMS 2.9 in our lab to have a look into the new Webbridge3 component, however when browsing to the web page to join a meeting i receive:

"

System is currently unavailable.

Please try again later

" 

Anyone else had this during their upgrade/deployment?

Webbridge3 and Callbridge certs configured accordingly - these are self-signed for now.

Thank you

[abcdedghi1]

can you post the webbridge3  configs and status?

[robertb]

Sure,

join.lab> webbridge3

Enabled : true

HTTPS Interface whitelist : a:443

HTTPS Key file : lab.key

HTTPS Full chain certificate file : lab.crt

HTTP redirect : Enabled, Port:80

C2W Interface whitelist : a:9999

C2W Key file : lab.key

C2W Full chain certificate file : lab.crt

C2W Trust bundle : lab.crt

Beta options : none

API config:

<?xml version="1.0"?>
<webBridge id="fd32edc4-5c11-4f54-9e28-6dc9c4d5cd74">
  <url>c2w://join.lab.cloudrooms.co.za.lo:9999</url>
  <resourceArchive></resourceArchive>
  <resolveCoSpaceCallIds>true</resolveCoSpaceCallIds>
  <resolveLyncConferenceIds>true</resolveLyncConferenceIds>
  <idEntryMode>legacy</idEntryMode>
  <allowWeblinkAccess>true</allowWeblinkAccess>
  <showSignIn>false</showSignIn>
</webBridge>

[abcdedghi1]

can you turn on detailed logging, Sip trace, api , and dns and webrtc logs.

and then try to go to that webbridge link, basically reproduce the issue and then post the log bundle here?

also i imagine you did the below already too:

A port must be opened on an interface (using webbridge3 c2w listen) to allow the
callbridge to connect to the webbridge3 (the webbridge listens on that port). This is why
you have to give the address with this port when you do the APIrequest to tell a callbridge
about this webbridge. This connection must be secured with certificates.

[hogeraad01]

We are having the same issue after a new install.

We followed the quickstart guide.

We only skipped the steps 14a and 14b because we do not have this equipment.

All steps appear to be successfull, but the app remains offline.

Also no clues in the logs.

[LUCAS NEEDHAM]

I found this thread when searching for my issue.  I was setting this up in a lab and had the same symptoms.  Found a fix so I thought I'd share in case it helps.  When enabling webbridge3 I had an error stating "FAILURE: Error loading the c2w trust bundle file".  I'm using self signed certs.  Turns out I needed to generate the self signed cert with the CN attribute set to the FQDN of CMS.  Worked fine after that.  

[christph]

The common name of the c2w webbridge cert needs to match the webridge configuration in the api as well. So in the API under /webbridge/ you will need to have the URL set to c2w://<Common-Name>:9999 , if you are using 9999 as the c2w port of course. 

Heres the output of pki inspect:

cms01> pki inspect commoncore.cer
Checking ssh public keys...not found
Checking user configured certificates and keys...found
File contains a PEM encoded certificate
Certificate:
Data:
Version: 3 (0x2)
Serial Number:
1c:00:00:00:29:f8:07:b7:68:40:36:bd:e5:00:00:00:00:00:29
Signature Algorithm: sha256WithRSAEncryption
Issuer: DC=com, DC=cisco, CN=cisco-WIN-UCUM3RMI7OC-CA
Validity
Not Before: Jul 24 10:54:46 2020 GMT
Not After : Jul 24 10:54:46 2022 GMT
Subject: CN=cmscluster.cisco.com