cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements
2981
Views
0
Helpful
10
Replies
Highlighted
Beginner

CMS - Webbridge TLS Handshake error

Hello All,

 

I need to some pointers in troubleshooting this error I can see in the event log of my Database Node which is also running the webbridge :

 

Mar 18 09:34:13 db1 webbridge-reverse-proxy[1]:  2018/03/18 09:34:13 http: TLS handshake error from 192.168.0.66:40229: tls: client didn't provide a certificate
Mar 18 09:34:13 db1 host: server:  connection to 192.168.0.66:443 closed: TLS handshake error

Apart from this error all seems to be running smoothly within the cluster (although I still need to integrate with expressway and configure email templates) :

 

Version - 2.3.2

Core1 - Webadmin, Callbridge Cluster, XMPP Cluster, DB Cluster, Trunk

Core2 - Webadmin, Callbridge Cluster, XMPP Cluster, DB Cluster, Trunk

DB1 - DB Cluster master, XMPP Cluster, Webbridge

Edge1 - Loadbalancer

Edge2 - Loadbalancer

 

Rgds,

Mat

10 REPLIES 10
Highlighted
Hall of Fame Cisco Employee

Start by making sure the DB clustering certificates meet the required specs and that DNS matches what thay have.

HTH

java

if this helps, please rate
Highlighted
Participant

i assume you are connecting locally with webbridge. first check if WB is listening on port 443. 

do check the following

1. Webbridge must trust Callbridge Cluster certificate bundle.

2. webbridge is listening on 443 port. also enable HTTP redirect.

3. certificate ROOTCA must be assigned on Webbridge.

 

 

HTH

AMMAR

please rate and mark answered if helpful.

Highlighted

Hello Jaime / Amar,

 

Webridge is listening on 443, Certs are good (im using a common cert for all services apart from the the loadbalancer) and DNS is good.

 

Any other ideas ?

Highlighted

which server is  192.168.0.66? Is it one of the loadbalancers?

Wondering where the cert disconnect happens

Steve

Highlighted

.66 (db1) is running clustered db, clustered xmpp and the only webridge.

Highlighted

For info, maybe somebody can take a look at the webridge.cert & callbridge.cert (both in fact are identical certs signed by the same CA and webbridge trusts callbridge.cert (attached with .cer extension changed to .txt), I also just deployed the webbridge on my 2 other nodes and have the same error in the syslogs :

 

Mar 20 15:43:38 db1 host: server:  connection to 192.168.0.61:443 closed: TLS handshake error
Mar 20 15:43:38 core1 webbridge-reverse-proxy[1]:  2018/03/20 15:43:38 http: TLS handshake error from 192.168.0.66:41942: tls: client didn't provide a certificate
Mar 20 15:43:44 core2 "webbridge":  INFO : [DEBUGGING] Stats 0, c:2, d:0
Mar 20 15:43:45 db1 host: server:  connection to 192.168.0.63:443 closed: TLS handshake error
Mar 20 15:43:45 core2 webbridge-reverse-proxy[1]:  2018/03/20 15:43:45 http: TLS handshake error from 192.168.0.66:42406: tls: client didn't provide a certificate
Mar 20 15:43:45 db1 host: server:  connection to 192.168.0.63:443 closed: TLS handshake error
Mar 20 15:43:45 core2 webbridge-reverse-proxy[1]:  2018/03/20 15:43:45 http: TLS handshake error from 192.168.0.66:41420: tls: client didn't provide a certificate
Mar 20 15:43:45 db1 webbridge-reverse-proxy[1]:  2018/03/20 15:43:45 http: TLS handshake error from 192.168.0.66:45286: tls: client didn't provide a certificate
Mar 20 15:43:45 db1 host: server:  connection to 192.168.0.66:443 closed: TLS handshake error
Mar 20 15:43:49 db1 host: server:  connection to 192.168.0.61:443 closed: TLS handshake error
Mar 20 15:43:49 core1 webbridge-reverse-proxy[1]:  2018/03/20 15:43:49 http: TLS handshake error from 192.168.0.66:34530: tls: client didn't provide a certificate
Mar 20 15:43:49 db1 host: server:  connection to 192.168.0.61:443 closed: TLS handshake error
Mar 20 15:43:49 core1 webbridge-reverse-proxy[1]:  2018/03/20 15:43:49 http: TLS handshake error from 192.168.0.66:33502: tls: client didn't provide a certificate
Mar 20 15:43:50 core1 sfpool:  database master connection status: node: 192.168.0.66, connections in use: 17, max connections: 750
Mar 20 15:43:53 db1 "webbridge":  INFO : [DEBUGGING] Stats 0, c:2, d:0

 

More logs showing webbridge connection process to callbridge, it talks about xmpp certificate, not where the link is (xmpp cert is also using same ca and the same cert as webbridge and callbridge) :

 

Mar 20 15:41:31 core1 host: server:  INFO : web bridge link 4: starting up for "192.168.0.61"
Mar 20 15:41:31 core1 "webbridge":  INFO : [SERVER_CONNECTION] initialising server connection 991e6962-7e0e-4b54-a877-26860f498b19
Mar 20 15:41:31 core1 "webbridge":  INFO : [SERVER_CONNECTION] server connection created (1) - 991e6962-7e0e-4b54-a877-26860f498b19
Mar 20 15:41:31 core1 "webbridge":  INFO : [SERVER_CONNECTION] new server connection 991e6962-7e0e-4b54-a877-26860f498b19 from 203.0.113.1ǡU¹
Mar 20 15:41:31 core1 "webbridge":  INFO : [SERVER_CONNECTION] server connection scheduling configuration request 991e6962-7e0e-4b54-a877-26860f498b19
Mar 20 15:41:31 core1 host: server:  INFO : web bridge link 4 connection established
Mar 20 15:41:31 core1 host: server:  INFO : web bridge link 4: configuration request received (custom background url: serverUpload.sf?type=background&source=991e6962-7e0e-4b54-a877-26860f498b19, logo url: serverUpload.sf?type=logo&source=991e6962-7e0e-4b54-a877-26860f498b19, archive url: serverUpload.sf?type=archive&source=991e6962-7e0e-4b54-a877-26860f498b19, certificate url: serverUpload.sf?type=xmppCertificate&source=991e6962-7e0e-4b54-a877-26860f498b19)
Mar 20 15:41:31 core2 host: server:  INFO : web bridge link 4: starting up for "192.168.0.61"
Mar 20 15:41:31 core1 "webbridge":  INFO : [SERVER_CONNECTION] server connection scheduling configuration request 991e6962-7e0e-4b54-a877-26860f498b19 - response not yet received
Mar 20 15:41:31 core1 "webbridge":  INFO : [SERVER_CONNECTION] initialising server connection 2a562c29-01a2-4ca5-bd8c-c414e7e5a3c0
Mar 20 15:41:31 core1 "webbridge":  INFO : [SERVER_CONNECTION] server connection created (2) - 2a562c29-01a2-4ca5-bd8c-c414e7e5a3c0
Mar 20 15:41:31 core1 "webbridge":  INFO : [SERVER_CONNECTION] new server connection 2a562c29-01a2-4ca5-bd8c-c414e7e5a3c0 from 203.0.113.1ǡU¹
Mar 20 15:41:31 core1 "webbridge":  INFO : [SERVER_CONNECTION] server connection scheduling configuration request 2a562c29-01a2-4ca5-bd8c-c414e7e5a3c0
Mar 20 15:41:31 core2 host: server:  INFO : web bridge link 4 connection established
Mar 20 15:41:31 core2 host: server:  INFO : web bridge link 4: configuration request received (custom background url: serverUpload.sf?type=background&source=2a562c29-01a2-4ca5-bd8c-c414e7e5a3c0, logo url: serverUpload.sf?type=logo&source=2a562c29-01a2-4ca5-bd8c-c414e7e5a3c0, archive url: serverUpload.sf?type=archive&source=2a562c29-01a2-4ca5-bd8c-c414e7e5a3c0, certificate url: serverUpload.sf?type=xmppCertificate&source=2a562c29-01a2-4ca5-bd8c-c414e7e5a3c0)
Mar 20 15:41:31 core2 host: server:  INFO : successfully pushed web bridge certificate to "https://192.168.0.61/serverUpload.sf?type=xmppCertificate&source=2a562c29-01a2-4ca5-bd8c-c414e7e5a3c0"
Mar 20 15:41:31 core1 "webbridge":  INFO : [SERVER_CONNECTION] server connection scheduling configuration request 2a562c29-01a2-4ca5-bd8c-c414e7e5a3c0 - response not yet received
Mar 20 15:41:31 core1 "webbridge":  INFO : [SERVER_CONNECTION] server configuration response received 991e6962-7e0e-4b54-a877-26860f498b19
Mar 20 15:41:31 core1 "webbridge":  INFO : [SERVER_CONNECTION]   last request scheduled 35ms ago
Mar 20 15:41:31 core1 "webbridge":  INFO : [SERVER_CONNECTION]   initial response : true
Mar 20 15:41:31 core1 "webbridge":  INFO : [SERVER_CONNECTION]   custom background image : no
Mar 20 15:41:31 core1 "webbridge":  INFO : [SERVER_CONNECTION]   custom logo image : no
Mar 20 15:41:31 core1 "webbridge":  INFO : [SERVER_CONNECTION]   custom archive : no
Mar 20 15:41:31 core1 "webbridge":  INFO : [SERVER_CONNECTION]   xmpp certificate : no
Mar 20 15:41:31 core1 "webbridge":  INFO : [SERVER_CONNECTION]   branding license : 20
Mar 20 15:41:31 core1 "webbridge":  INFO : [SERVER_CONNECTION]   cospace access:
Mar 20 15:41:31 core1 "webbridge":  INFO : [SERVER_CONNECTION]     direct hyperlink : yes
Mar 20 15:41:31 core1 "webbridge":  INFO : [SERVER_CONNECTION]     destination mode : secure
Mar 20 15:41:31 core1 "webbridge":  INFO : [SERVER_CONNECTION]   show sign in : yes
Mar 20 15:41:31 core1 host: server:  INFO : successfully pushed web bridge certificate to "https://192.168.0.61/serverUpload.sf?type=xmppCertificate&source=991e6962-7e0e-4b54-a877-26860f498b19"
Mar 20 15:41:31 core1 "webbridge":  INFO : [SERVER_CONNECTION] server configuration response received 2a562c29-01a2-4ca5-bd8c-c414e7e5a3c0
Mar 20 15:41:31 core1 "webbridge":  INFO : [SERVER_CONNECTION]   last request scheduled 25ms ago
Mar 20 15:41:31 core1 "webbridge":  INFO : [SERVER_CONNECTION]   initial response : true
Mar 20 15:41:31 core1 "webbridge":  INFO : [SERVER_CONNECTION]   custom background image : no
Mar 20 15:41:31 core1 "webbridge":  INFO : [SERVER_CONNECTION]   custom logo image : no
Mar 20 15:41:31 core1 "webbridge":  INFO : [SERVER_CONNECTION]   custom archive : no
Mar 20 15:41:31 core1 "webbridge":  INFO : [SERVER_CONNECTION]   xmpp certificate : no
Mar 20 15:41:31 core1 "webbridge":  INFO : [SERVER_CONNECTION]   branding license : 20
Mar 20 15:41:31 core1 "webbridge":  INFO : [SERVER_CONNECTION]   cospace access:
Mar 20 15:41:31 core1 "webbridge":  INFO : [SERVER_CONNECTION]     direct hyperlink : yes
Mar 20 15:41:31 core1 "webbridge":  INFO : [SERVER_CONNECTION]     destination mode : secure
Mar 20 15:41:31 core1 "webbridge":  INFO : [SERVER_CONNECTION]   show sign in : yes
Mar 20 15:41:31 core1 "webbridge":  INFO : [SERVER_CONNECTION] server configuration response received 2a562c29-01a2-4ca5-bd8c-c414e7e5a3c0
Mar 20 15:41:31 core1 "webbridge":  INFO : [SERVER_CONNECTION]   last request scheduled 25ms ago
Mar 20 15:41:31 core1 "webbridge":  INFO : [SERVER_CONNECTION]   last response received 0ms ago
Mar 20 15:41:31 core1 "webbridge":  INFO : [SERVER_CONNECTION]   custom background image : no
Mar 20 15:41:31 core1 "webbridge":  INFO : [SERVER_CONNECTION]   custom logo image : no
Mar 20 15:41:31 core1 "webbridge":  INFO : [SERVER_CONNECTION]   custom archive : no
Mar 20 15:41:31 core1 "webbridge":  INFO : [SERVER_CONNECTION]   xmpp certificate : no
Mar 20 15:41:31 core1 "webbridge":  INFO : [SERVER_CONNECTION]   branding license : 20
Mar 20 15:41:31 core1 "webbridge":  INFO : [SERVER_CONNECTION]   cospace access:
Mar 20 15:41:31 core1 "webbridge":  INFO : [SERVER_CONNECTION]     direct hyperlink : yes
Mar 20 15:41:31 core1 "webbridge":  INFO : [SERVER_CONNECTION]     destination mode : secure
Mar 20 15:41:31 core1 "webbridge":  INFO : [SERVER_CONNECTION]   show sign in : yes
Mar 20 15:41:32 core1 "webbridge":  INFO : [SERVER_CONNECTION] server configuration response received 991e6962-7e0e-4b54-a877-26860f498b19
Mar 20 15:41:32 core1 "webbridge":  INFO : [SERVER_CONNECTION]   last request scheduled 1031ms ago
Mar 20 15:41:32 core1 "webbridge":  INFO : [SERVER_CONNECTION]   last response received 996ms ago
Mar 20 15:41:32 core1 "webbridge":  INFO : [SERVER_CONNECTION]   custom background image : no
Mar 20 15:41:32 core1 "webbridge":  INFO : [SERVER_CONNECTION]   custom logo image : no
Mar 20 15:41:32 core1 "webbridge":  INFO : [SERVER_CONNECTION]   custom archive : no
Mar 20 15:41:32 core1 "webbridge":  INFO : [SERVER_CONNECTION]   xmpp certificate : no
Mar 20 15:41:32 core1 "webbridge":  INFO : [SERVER_CONNECTION]   branding license : 20
Mar 20 15:41:32 core1 "webbridge":  INFO : [SERVER_CONNECTION]   cospace access:
Mar 20 15:41:32 core1 "webbridge":  INFO : [SERVER_CONNECTION]     direct hyperlink : yes
Mar 20 15:41:32 core1 "webbridge":  INFO : [SERVER_CONNECTION]     destination mode : secure
Mar 20 15:41:32 core1 "webbridge":  INFO : [SERVER_CONNECTION]   show sign in : yes
Mar 20 15:41:34 db1 host: server:  connection to 192.168.0.61:443 closed: TLS handshake error
Mar 20 15:41:34 core1 webbridge-reverse-proxy[1]:  2018/03/20 15:41:34 http: TLS handshake error from 192.168.0.66:44713: tls: client didn't provide a certificate
Mar 20 15:41:34 core1 webbridge-reverse-proxy[1]:  2018/03/20 15:41:34 http: TLS handshake error from 192.168.0.66:38653: tls: client didn't provide a certificate
Mar 20 15:41:34 db1 host: server:  connection to 192.168.0.61:443 closed: TLS handshake error
Mar 20 15:41:37 db1 host: server:  connection to 192.168.0.61:443 closed: TLS handshake error
Mar 20 15:41:37 core1 webbridge-reverse-proxy[1]:  2018/03/20 15:41:37 http: TLS handshake error from 192.168.0.66:35158: tls: client didn't provide a certificate
Mar 20 15:41:37 db1 host: server:  connection to 192.168.0.61:443 closed: TLS handshake error
Mar 20 15:41:37 core1 webbridge-reverse-proxy[1]:  2018/03/20 15:41:37 http: TLS handshake error from 192.168.0.66:33195: tls: client didn't provide a certificate
Mar 20 15:41:39 db1 webbridge-reverse-proxy[1]:  2018/03/20 15:41:39 http: TLS handshake error from 192.168.0.66:37829: tls: client didn't provide a certificate
Mar 20 15:41:39 db1 host: server:  connection to 192.168.0.66:443 closed: TLS handshake error
Mar 20 15:41:40 db1 host: server:  connection to 192.168.0.61:443 closed: TLS handshake error
Mar 20 15:41:40 core1 webbridge-reverse-proxy[1]:  2018/03/20 15:41:40 http: TLS handshake error from 192.168.0.66:40292: tls: client didn't provide a certificate
Mar 20 15:41:40 db1 host: server:  connection to 192.168.0.61:443 closed: TLS handshake error
Mar 20 15:41:40 core1 webbridge-reverse-proxy[1]:  2018/03/20 15:41:40 http: TLS handshake error from 192.168.0.66:41963: tls: client didn't provide a certificate
Mar 20 15:41:43 core1 webbridge-reverse-proxy[1]:  2018/03/20 15:41:43 http: TLS handshake error from 192.168.0.66:45013: tls: client didn't provide a certificate
Mar 20 15:41:43 db1 host: server:  connection to 192.168.0.61:443 closed: TLS handshake error
Mar 20 15:41:43 db1 host: server:  connection to 192.168.0.61:443 closed: TLS handshake error
Mar 20 15:41:43 core1 webbridge-reverse-proxy[1]:  2018/03/20 15:41:43 http: TLS handshake error from 192.168.0.66:46577: tls: client didn't provide a certificate
Mar 20 15:41:44 core2 "webbridge":  INFO : [DEBUGGING] Stats 0, c:2, d:0
Mar 20 15:41:48 core1 host: server:  INFO : 192.168.0.27: API user "apiuser" created new web bridge eb0c20b3-2ef7-486b-9da9-4221ff6b9805 (https://192.168.0.63)
Mar 20 15:41:48 core1 host: server:  INFO : web bridge link 5: starting up for "192.168.0.63"
Mar 20 15:41:48 db1 host: server:  INFO : web bridge link 5: starting up for "192.168.0.63"
Mar 20 15:41:48 core2 "webbridge":  INFO : [SERVER_CONNECTION] initialising server connection 0238d90c-3790-4ac8-b0e0-fce2114d3677
Mar 20 15:41:48 core2 "webbridge":  INFO : [SERVER_CONNECTION] server connection created (1) - 0238d90c-3790-4ac8-b0e0-fce2114d3677
Mar 20 15:41:48 core1 host: server:  INFO : web bridge link 5 connection established
Mar 20 15:41:48 core2 "webbridge":  INFO : [SERVER_CONNECTION] new server connection 0238d90c-3790-4ac8-b0e0-fce2114d3677 from 203.0.113.1՛͵񊍡r 20 15:41:48 core2 "webbridge":  INFO : [SERVER_CONNECTION] server connection scheduling configuration request 0238d90c-3790-4ac8-b0e0-fce2114d3677
Mar 20 15:41:48 core1 host: server:  INFO : web bridge link 5: configuration request received (custom background url: serverUpload.sf?type=background&source=0238d90c-3790-4ac8-b0e0-fce2114d3677, logo url: serverUpload.sf?type=logo&source=0238d90c-3790-4ac8-b0e0-fce2114d3677, archive url: serverUpload.sf?type=archive&source=0238d90c-3790-4ac8-b0e0-fce2114d3677, certificate url: serverUpload.sf?type=xmppCertificate&source=0238d90c-3790-4ac8-b0e0-fce2114d3677)
Mar 20 15:41:48 core2 host: server:  INFO : web bridge link 5: starting up for "192.168.0.63"
Mar 20 15:41:48 core2 webbridge-reverse-proxy[1]:  2018/03/20 15:41:48 http: TLS handshake error from 192.168.0.66:45142: tls: client didn't provide a certificate
Mar 20 15:41:48 db1 host: server:  connection to 192.168.0.63:443 closed: TLS handshake error
Mar 20 15:41:48 db1 host: server:  INFO : failed to establish connection to web bridge link 5 (connection failure)
Mar 20 15:41:48 core2 webbridge-reverse-proxy[1]:  2018/03/20 15:41:48 http: TLS handshake error from 192.168.0.66:44927: tls: client didn't provide a certificate
Mar 20 15:41:48 db1 host: server:  connection to 192.168.0.63:443 closed: TLS handshake error
Mar 20 15:41:48 core2 "webbridge":  INFO : [SERVER_CONNECTION] initialising server connection e402b8d0-8f46-4fef-8e8a-6260512a73a2
Mar 20 15:41:48 core2 "webbridge":  INFO : [SERVER_CONNECTION] server connection created (2) - e402b8d0-8f46-4fef-8e8a-6260512a73a2
Mar 20 15:41:48 core2 "webbridge":  INFO : [SERVER_CONNECTION] new server connection e402b8d0-8f46-4fef-8e8a-6260512a73a2 from 203.0.113.1՛͵񊍡r 20 15:41:48 core2 "webbridge":  INFO : [SERVER_CONNECTION] server connection scheduling configuration request e402b8d0-8f46-4fef-8e8a-6260512a73a2
Mar 20 15:41:48 core2 host: server:  INFO : web bridge link 5 connection established
Mar 20 15:41:48 core2 host: server:  INFO : web bridge link 5: configuration request received (custom background url: serverUpload.sf?type=background&source=e402b8d0-8f46-4fef-8e8a-6260512a73a2, logo url: serverUpload.sf?type=logo&source=e402b8d0-8f46-4fef-8e8a-6260512a73a2, archive url: serverUpload.sf?type=archive&source=e402b8d0-8f46-4fef-8e8a-6260512a73a2, certificate url: serverUpload.sf?type=xmppCertificate&source=e402b8d0-8f46-4fef-8e8a-6260512a73a2)
Mar 20 15:41:48 core2 "webbridge":  INFO : [SERVER_CONNECTION] server connection scheduling configuration request 0238d90c-3790-4ac8-b0e0-fce2114d3677 - response not yet received
Mar 20 15:41:48 core2 "webbridge":  INFO : [SERVER_CONNECTION] server connection scheduling configuration request e402b8d0-8f46-4fef-8e8a-6260512a73a2 - response not yet received
Mar 20 15:41:48 core1 host: server:  INFO : successfully pushed web bridge certificate to "https://192.168.0.63/serverUpload.sf?type=xmppCertificate&source=0238d90c-3790-4ac8-b0e0-fce2114d3677"
Mar 20 15:41:48 core2 "webbridge":  INFO : [SERVER_CONNECTION] server configuration response received 0238d90c-3790-4ac8-b0e0-fce2114d3677
Mar 20 15:41:48 core2 "webbridge":  INFO : [SERVER_CONNECTION]   last request scheduled 29ms ago
Mar 20 15:41:48 core2 "webbridge":  INFO : [SERVER_CONNECTION]   initial response : true
Mar 20 15:41:48 core2 "webbridge":  INFO : [SERVER_CONNECTION]   custom background image : no
Mar 20 15:41:48 core2 "webbridge":  INFO : [SERVER_CONNECTION]   custom logo image : no
Mar 20 15:41:48 core2 "webbridge":  INFO : [SERVER_CONNECTION]   custom archive : no
Mar 20 15:41:48 core2 "webbridge":  INFO : [SERVER_CONNECTION]   xmpp certificate : no
Mar 20 15:41:48 core2 "webbridge":  INFO : [SERVER_CONNECTION]   branding license : 20
Mar 20 15:41:48 core2 "webbridge":  INFO : [SERVER_CONNECTION]   cospace access:
Mar 20 15:41:48 core2 "webbridge":  INFO : [SERVER_CONNECTION]     direct hyperlink : yes
Mar 20 15:41:48 core2 "webbridge":  INFO : [SERVER_CONNECTION]     destination mode : secure
Mar 20 15:41:48 core2 "webbridge":  INFO : [SERVER_CONNECTION]   show sign in : yes
Mar 20 15:41:48 core2 "webbridge":  INFO : [SERVER_CONNECTION] server configuration response received 0238d90c-3790-4ac8-b0e0-fce2114d3677
Mar 20 15:41:48 core2 "webbridge":  INFO : [SERVER_CONNECTION]   last request scheduled 30ms ago
Mar 20 15:41:48 core2 "webbridge":  INFO : [SERVER_CONNECTION]   last response received 1ms ago
Mar 20 15:41:48 core2 "webbridge":  INFO : [SERVER_CONNECTION]   custom background image : no
Mar 20 15:41:48 core2 "webbridge":  INFO : [SERVER_CONNECTION]   custom logo image : no
Mar 20 15:41:48 core2 "webbridge":  INFO : [SERVER_CONNECTION]   custom archive : no
Mar 20 15:41:48 core2 "webbridge":  INFO : [SERVER_CONNECTION]   xmpp certificate : no
Mar 20 15:41:48 core2 "webbridge":  INFO : [SERVER_CONNECTION]   branding license : 20
Mar 20 15:41:48 core2 "webbridge":  INFO : [SERVER_CONNECTION]   cospace access:
Mar 20 15:41:48 core2 "webbridge":  INFO : [SERVER_CONNECTION]     direct hyperlink : yes
Mar 20 15:41:48 core2 "webbridge":  INFO : [SERVER_CONNECTION]     destination mode : secure
Mar 20 15:41:48 core2 "webbridge":  INFO : [SERVER_CONNECTION]   show sign in : yes
Mar 20 15:41:48 core2 "webbridge":  INFO : [SERVER_CONNECTION] server configuration response received e402b8d0-8f46-4fef-8e8a-6260512a73a2
Mar 20 15:41:48 core2 "webbridge":  INFO : [SERVER_CONNECTION]   last request scheduled 32ms ago
Mar 20 15:41:48 core2 "webbridge":  INFO : [SERVER_CONNECTION]   initial response : true
Mar 20 15:41:48 core2 "webbridge":  INFO : [SERVER_CONNECTION]   custom background image : no
Mar 20 15:41:48 core2 "webbridge":  INFO : [SERVER_CONNECTION]   custom logo image : no
Mar 20 15:41:48 core2 "webbridge":  INFO : [SERVER_CONNECTION]   custom archive : no
Mar 20 15:41:48 core2 "webbridge":  INFO : [SERVER_CONNECTION]   xmpp certificate : no
Mar 20 15:41:48 core2 "webbridge":  INFO : [SERVER_CONNECTION]   branding license : 20
Mar 20 15:41:48 core2 "webbridge":  INFO : [SERVER_CONNECTION]   cospace access:
Mar 20 15:41:48 core2 "webbridge":  INFO : [SERVER_CONNECTION]     direct hyperlink : yes
Mar 20 15:41:48 core2 "webbridge":  INFO : [SERVER_CONNECTION]     destination mode : secure
Mar 20 15:41:48 core2 "webbridge":  INFO : [SERVER_CONNECTION]   show sign in : yes
Mar 20 15:41:48 core2 host: server:  INFO : successfully pushed web bridge certificate to "https://192.168.0.63/serverUpload.sf?type=xmppCertificate&source=e402b8d0-8f46-4fef-8e8a-6260512a73a2"
Mar 20 15:41:49 core2 "webbridge":  INFO : [SERVER_CONNECTION] server configuration response received e402b8d0-8f46-4fef-8e8a-6260512a73a2
Mar 20 15:41:49 core2 "webbridge":  INFO : [SERVER_CONNECTION]   last request scheduled 1032ms ago
Mar 20 15:41:49 core2 "webbridge":  INFO : [SERVER_CONNECTION]   last response received 1000ms ago
Mar 20 15:41:49 core2 "webbridge":  INFO : [SERVER_CONNECTION]   custom background image : no
Mar 20 15:41:49 core2 "webbridge":  INFO : [SERVER_CONNECTION]   custom logo image : no
Mar 20 15:41:49 core2 "webbridge":  INFO : [SERVER_CONNECTION]   custom archive : no
Mar 20 15:41:49 core2 "webbridge":  INFO : [SERVER_CONNECTION]   xmpp certificate : no
Mar 20 15:41:49 core2 "webbridge":  INFO : [SERVER_CONNECTION]   branding license : 20
Mar 20 15:41:49 core2 "webbridge":  INFO : [SERVER_CONNECTION]   cospace access:
Mar 20 15:41:49 core2 "webbridge":  INFO : [SERVER_CONNECTION]     direct hyperlink : yes
Mar 20 15:41:49 core2 "webbridge":  INFO : [SERVER_CONNECTION]     destination mode : secure
Mar 20 15:41:49 core2 "webbridge":  INFO : [SERVER_CONNECTION]   show sign in : yes
Mar 20 15:41:50 core1 sfpool:  database master connection status: node: 192.168.0.66, connections in use: 17, max connections: 750
Mar 20 15:41:50 db1 webbridge-reverse-proxy[1]:  2018/03/20 15:41:50 http: TLS handshake error from 192.168.0.66:40022: tls: client didn't provide a certificate
Mar 20 15:41:50 db1 host: server:  connection to 192.168.0.66:443 closed: TLS handshake error
Mar 20 15:41:51 core2 webbridge-reverse-proxy[1]:  2018/03/20 15:41:51 http: TLS handshake error from 192.168.0.66:40763: tls: client didn't provide a certificate
Mar 20 15:41:51 db1 host: server:  connection to 192.168.0.63:443 closed: TLS handshake error
Mar 20 15:41:51 core2 webbridge-reverse-proxy[1]:  2018/03/20 15:41:51 http: TLS handshake error from 192.168.0.66:34036: tls: client didn't provide a certificate
Mar 20 15:41:51 db1 host: server:  connection to 192.168.0.63:443 closed: TLS handshake error
Mar 20 15:41:53 db1 "webbridge":  INFO : [DEBUGGING] Stats 0, c:2, d:0
Mar 20 15:41:53 db1 host: server:  connection to 192.168.0.61:443 closed: TLS handshake error
Mar 20 15:41:53 core1 webbridge-reverse-proxy[1]:  2018/03/20 15:41:53 http: TLS handshake error from 192.168.0.66:38164: tls: client didn't provide a certificate
Mar 20 15:41:53 core1 webbridge-reverse-proxy[1]:  2018/03/20 15:41:53 http: TLS handshake error from 192.168.0.66:33324: tls: client didn't provide a certificate
Mar 20 15:41:53 db1 host: server:  connection to 192.168.0.61:443 closed: TLS handshake error
Mar 20 15:41:54 db1 host: server:  connection to 192.168.0.63:443 closed: TLS handshake error
Mar 20 15:41:54 core2 webbridge-reverse-proxy[1]:  2018/03/20 15:41:54 http: TLS handshake error from 192.168.0.66:34285: tls: client didn't provide a certificate
Mar 20 15:41:54 db1 host: server:  connection to 192.168.0.63:443 closed: TLS handshake error
Mar 20 15:41:54 core2 webbridge-reverse-proxy[1]:  2018/03/20 15:41:54 http: TLS handshake error from 192.168.0.66:42930: tls: client didn't provide a certificate
Mar 20 15:41:57 db1 host: server:  connection to 192.168.0.63:443 closed: TLS handshake error
Mar 20 15:41:57 core2 webbridge-reverse-proxy[1]:  2018/03/20 15:41:57 http: TLS handshake error from 192.168.0.66:39772: tls: client didn't provide a certificate
Mar 20 15:41:57 db1 host: server:  connection to 192.168.0.63:443 closed: TLS handshake error
Mar 20 15:41:57 core2 webbridge-reverse-proxy[1]:  2018/03/20 15:41:57 http: TLS handshake error from 192.168.0.66:35759: tls: client didn't provide a certificate
Highlighted

I'm having this exact same issue..  where I have a single webbridge CMS.. not beable to connect to the Call Bridge Group.

Did you manage to find a resolution mate?

Ben

Highlighted

I reinstalled the cluster to a more recent version (I dont think the more recent version is the fix) , and instead of using common certificates created a unqiue certificate for each service and each node. I no longer have the issue. Maybe I messed up in the certs.

Highlighted

Thanks mate. Just to expand what youre saying.. you created separate certs
for Call bridge server, xmpp service, db cluster service, web bridge
service, LB service and trunk service. Hence didn’t use any cert twice per
say.
Highlighted

Hello,

 

Yep, thats correct. But I'm sure their must have been a mistake on my certs I did orginally.