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:

 

[jaywagener]

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?

We ended up re-keying the cert and that resolved the issue.

 

[Martin_Thomas_HPA]

Hello whe have this issue too. I have created and uploaded our Cert again. No Success....

Meassage: Expired on 01.01.2021 01:00:00

Cert is valid until: 2022-07-29

please help!! Our Teamsconnection is now down untli it will be fixed!!!

 

[jaywagener]

I would verify you are NOT using a wildcard certificate and would rekey, not just reload the certificate, if you are not using a wildcard cert. if it is a wildcard, it may work for a while but will stop. You will need to load a certificate that is specific to a certain domain, not a *.domain.com cert.

 

[Martin_Thomas_HPA]

what do you mean with rekey? I have here a cert file and a Key file from the cert admin in our Company. Whe have only this wildcard cert for all services. There wars no problem until now with this cert. When i say to him that i need a non wildcard cert he will ask why, because it was ok until now. I see no tecnical reason why i must pay for an extra cert.....

 

[NickD_3CX]

Hi @Martin_Thomas_HPA ,

It seems you are using a Wildcard cert:


The first thing you need to do is issue a new cert but for your specific FQDN as we explain here:
https://www.3cx.com/docs/microsoft-teams-business-voice/#h.qcem6kowu7v9
https://www.3cx.com/docs/microsoft-teams-integration-faqs/#h.txihzzszti82

By doing this, you will also be doing what @jaywagener suggested, re-issuing the certificate.

 

[Martin_Thomas_HPA]

With the newest 3cx Update the issue is solved for us..

Thank You

 

[NickD_3CX]

Glad to hear that!

Update 3 makes a few more validations for the Certificate as well as accepting more formats of Private keys that are uploaded.

I will set this thread as 'Solved', but if someone is continuing to have problems after upgrading to V18 U3, please open a new thread in this forum category.