Cant provision w60b via SBC

[craign]

Hi, we are trying to provision 3 different w60b via an SBC and the device does not provision.
It is the same issue as this post: https://www.3cx.com/community/threads/provisioning-of-yealink-w60b.85246/page-2#post-401424
however I cant see how it was solved. Please advise possible solutions.
Thanks
Craig

 

[JohnS_3CX]

Hello,

1. Have you installed the latest 3CX updates? Especially this

2. Are you using a 3CX FQDN or custom?

 

[Saqqara]

Please provide more info on your setup - https://www.3cx.com/community/threads/information-to-provide-when-requesting-help.67558/

Are you using a 3CX FQDN and Letsencrypt SSL or your own

 

[craign]

Hi,
Its a 3CX FQDN on our own server
all updates are installed: Your system is up to date. Last checked: Today, 12:15

 

[JohnS_3CX]

Lets double-check the certificates before anything:

1. Go here
2. Type your fqdn with its SSL port. Example: mycompany.3cx.com:5001
3. Check the results, there should be only 2 certificates in the chain. NOT 3 certificates.

If you see 3 certificates and the bottom one is ISRG Root X1, with the below issuer, then you might have a problem


Let us know what you find.

 

[Saqqara]

When you say it does not provision - please can you expand this.

Can you access the base unit via IP using the default username and password ?

If the base unit has been provisioned by 3CX, the password will be Device Web Page Password

What version of 3CX ?

Have you added the extensions under the extension tab - FXS / DECT

 

[craign]

When you say it does not provision - please can you expand this.

Can you access the base unit via IP using the default username and password ?

If the base unit has been provisioned by 3CX, the password will be Device Web Page Password

What version of 3CX ?

Have you added the extensions under the extension tab - FXS / DECT

Hi,

Yes we are provisioning correctly - can access devices etc. We have 30 provisioned across all our branches the last batch of units don't provision.
I see Johns question is returning the problem certificate.

 

[craign]

Lets double-check the certificates before anything:

1. Go here
2. Type your fqdn with its SSL port. Example: mycompany.3cx.com:5001
3. Check the results, there should be only 2 certificates in the chain. NOT 3 certificates.

If you see 3 certificates and the bottom one is ISRG Root X1, with the below issuer, then you might have a problem
View attachment 25749

Let us know what you find.

Hi,

Yes it is returning that certificate - do we need to remove it?

Craig

 

[JohnS_3CX]

Hi Craig,

I will PM you shortly

 

[craign]

Hi John,

Yes, thank you it provisioned - much appreciated.
We manage a few other servers - is it likely we will have a similar issue? We only use the cordless at this particular site though.

 

[JohnS_3CX]

Hi,

Check the rest of your FQDNs in the SSL checker to see if you get the same result as we discussed before.

If so, you will need to manually renew certs.
https://www.3cx.com/docs/self-hosted-instances-ssh/

Do not renew certificates unnecessarily or repeatedly. Only in this specific instance that we found these conditions.