Let's Encrypt - DST Root CA X3 Expiration Hotfix

[StefanW]

A hotfix is now available for customers who have been affected by an expired root cross-signing certificate by Let’s Encrypt - one of the most popular SSL/TLS certificate issuers globally.

Who is affected and how​

3CX configured the chain of certificates by following the popular project certbot, which is commonly used on web s...

Continue reading the Original Blog Post.

 

[piran]

Maybe just me, but the section called

"Who should take action"​

Only lists people who do not need to take any action (e.g. if you are hosted you do *not* need to take action)..

 

[NickD_3CX]

Maybe just me, but the section called

"Who should take action"​

Only lists people who do not need to take any action (e.g. if you are hosted you do *not* need to take action)..

We believe that it is equally important that a 3CX Administrator knows if they don't need to take an action, against if they do need to take an action.
Hanging in the balance thinking "do I or do I not need to worry" is the worst feeling, so we just liad everything out.

Also the title is written that way to draw attention as that is quite an important paragraph.

Anyhow, we are discussing semantics now, I think we can all agree the article is clear.

 

[Polaris15]

Does the hotfix require a reboot or would it cause any downtime? We are having issues with phones not staying in sync and running Provision Now does not update logos and BLF's etc.

 

[Saqqara]

Does the hotfix require a reboot or would it cause any downtime? We are having issues with phones not staying in sync and running Provision Now does not update logos and BLF's etc.

No reboot required, but it does cause minor downtime - while it updates the files which requires certain services to be stopped

 

[Polaris15]

Thanks, will do it out of hours

 

[jed]

Hi - e-Mail TEST - 4.3.2 Internal server error

We upgraded all our (internal) hosting servers (Mainly v16 Latest + a few v18) with the Hotfix, and now we cannot send Welcopme e-mail from our servers, by using 3CX SMTP Servers. When sending at Test e-mail, we get an "4.3.2 Internal server error" status

Is there something we have missed in the prepperation for this Hotfix?

Thank you in advance

 

[NickD_3CX]

Hi - e-Mail TEST - 4.3.2 Internal server error

We upgraded all our (internal) hosting servers (Mainly v16 Latest + a few v18) with the Hotfix, and now we cannot send Welcopme e-mail from our servers, by using 3CX SMTP Servers. When sending at Test e-mail, we get an "4.3.2 Internal server error" status

Is there something we have missed in the prepperation for this Hotfix?

Thank you in advance

Could you check again now please?
It was affected by the OVH outage that affected some of our services as well.

 

[jed]

It was affected by the OVH outage that affected some of our services as well.

PERFECT, Thank you, everything (or at least Mail send) is working again

 

[Polaris15]

Using 3CX SMTP Server, I am having an issue where emails are being sent to existing users but for any new extensions the welcome email is not sending. If I change a new extension to an existing email address it works fine? Nothing in the Office365 Message Trace so not even getting to O365

 

[NickD_3CX]

Under Settings --> Email, does the "TEST" button work and send you an email to the admin account?

Are the new extensions in the same domain? Have you tried a more 'generic' email like @gmail.com or @hotmail.com to see if emails are delivered there? (to see if it is something to specific users of a specific domain...)

Check of course Spam folder as well.

 

[Polaris15]

The email test works fine. New extensions are on the same domain so some of the other users we have. Tested the mailbox manually from an external email address and emails are going through fine. Checked for typos multiple times. Never hits spam because it never hits Office365 according to the message trace. Probably some misconfiguration somewhere but I am baffled! Are the SMTP logs recorded anywhere so I can see what error is coming back if there is one?

 

[NickD_3CX]

The email test works fine. New extensions are on the same domain so some of the other users we have. Tested the mailbox manually from an external email address and emails are going through fine. Checked for typos multiple times. Never hits spam because it never hits Office365 according to the message trace. Probably some misconfiguration somewhere but I am baffled! Are the SMTP logs recorded anywhere so I can see what error is coming back if there is one?

Send me in a PM the last email address that you sent an email to and it didn't go through and I will try and check it.

 

[Polaris15]

Done, thank you