Solved Teams certificate showing as expired

[dattics]

Hi, we already have Teams Integration up and everything has been working nice.

However, after some weeks, every time we want to change some configuration (https://example.3cx.co/#/app/settings/office365), the certificate shows as expired, even though, the expiration date is on 2022.

We are on version 18.0 Update 2 (Build 307) installed on an Azure VM (via marketplace).

This has also happen to other of our customers using the integration.

Before clicking OK to save:



After saving:

 

[NickD_3CX]

Can you try rebooting one of the Azure instances and see if the issue remains?

 

[dattics]

Can you try rebooting one of the Azure instances and see if the issue remains?

I already tried this, but the issue persists.

 

[Cutshaw]

Sounds like maybe rekey and re-download cert from the provider. I had to do this and came across some good articles in the kb related to cert stuff.

https://www.3cx.com/community/threads/pem-chain-format.83242/

Still looking to see if I can find something directly related to your issue.

 

[ewebster]

I am having this same issue.

 

[NickD_3CX]

I am having this same issue.
View attachment 26648

The cert name is a bit weird in your case, because after you upload it and press OK, when you go back to this page it should have changed names to the format "domain_cert_xxxxxxxxxxxx.pem".

Are you also on Azure?

 

[ewebster]

Nick, I am working with an on-premise Windows system. and a wildcard certificate.

The cert name is a bit weird in your case, because after you upload it and press OK, when you go back to this page it should have changed names to the format "domain_cert_xxxxxxxxxxxx.pem".

Are you also on Azure?

 

[StefanW]

wild-cards are in this place not supported!

 

[NickD_3CX]

Nick, I am working with an on-premise Windows system. and a wildcard certificate.

https://www.3cx.com/docs/microsoft-teams-integration-faqs/#h.txihzzszti82

As StefanW said. Also have a read through the whole doc to learn other common "pitfalls".

 

[ewebster]

https://www.3cx.com/docs/microsoft-teams-integration-faqs/#h.txihzzszti82

As StefanW said. Also have a read through the whole doc to learn other common "pitfalls".

Thanks for pointing this out, my apologies. I've never been one for reading instructions thoroughly, and again my lack of reading has failed me. Things look much better now having followed the instructions.

 

[dattics]

I bought a normal (no-wildcard) certificate to my domain:

teams.xyz.domain.com --> Error persists

Could this be another error? Does it accept two subdomains?

 

[NickD_3CX]

I bought a normal (no-wildcard) certificate to my domain:

teams.xyz.domain.com --> Error persists

Could this be another error? Does it accept two subdomains?

Go here: https://www.sslshopper.com/ssl-checker.html
Input your Teams FQDN with the Teams Port (5062) and check. If there is any error, you need to fix it first.

Example:
teams.xyz.domain.com:5062

 

[dattics]

I bought a new SSL certificate (not wildcard) with GoDaddy, upload it and shows as "Expired on: 12/31/2000 7:00:00 PM".

 

[Evolute IT]

I bought a new SSL certificate (not wildcard) with GoDaddy, upload it and shows as "Expired on: 12/31/2000 7:00:00 PM".

Sounds like you used the wrong files as certificate and key.

Once again, make sure you read the whole docs once or twice before trying it. The order of the content of the files is also very important.

 

[NickD_3CX]

I bought a new SSL certificate (not wildcard) with GoDaddy, upload it and shows as "Expired on: 12/31/2000 7:00:00 PM".

OK, and you uploaded the certs I assume.
Did you run in through the sslshopper link I sent you? What did it say, no problems?

If it showed a problem with the Intermediates, see here:
https://www.3cx.com/docs/microsoft-teams-integration-faqs/#h.uos0mgcmlxo5

 

[jaywagener]

Anyone find a fix for this? I have the same problem on one of our servers. It just started doing this recently. Initial config, sync, and install all went well. Users are able to call out/in through Teams, but now when I go to add a user in the 3CX O365 User Sync tab, I am unable to same and it sends me over to the Teams Direct Routing tab and says my cert expired 22 years ago. An SSL check of the cert doesn't show any errors:

 

[jaywagener]

... I am unable to same and it sends me over to the Teams Direct Routing tab and says my cert expired 22 years ago.

Sorry, meant to say I am unable to "save"...

 

[NickD_3CX]

Sorry, meant to say I am unable to "save"...

The Teams certificates you uploaded are in /var/lib/3cxpbx/Instance1/Bin/Cert/ .
Can you try running the command openssl x509 -enddate -noout -in <teams Cert PEM file> and tell me what the output is?

 

[jason-ct]

Hi Nick,

We are experiencing the same issue, but was working successfully last year at setup. I'm including the first few lines of the OpenSSL Output which displays the validity and issuer

Issuer: C = US, O = DigiCert Inc, OU = www.digicert.com, CN = RapidSSL RSA CA 2018
Validity
Not Before: Jun 30 00:00:00 2020 GMT
Not After : Jul 1 12:00:00 2022 GMT

 

[NickD_3CX]

Hi Nick,

We are experiencing the same issue, but was working successfully last year at setup. I'm including the first few lines of the OpenSSL Output which displays the validity and issuer

Issuer: C = US, O = DigiCert Inc, OU = www.digicert.com, CN = RapidSSL RSA CA 2018
Validity
Not Before: Jun 30 00:00:00 2020 GMT
Not After : Jul 1 12:00:00 2022 GMT

I sent you a PM.