FQDN/Domain Question

[David.Shoebridge]

We have been self-hosting in AWS 3CX systems for a few years now using our domain starpeer.com. A recent install using our domain resulted in a lot of features of 3CX not working properly. After doing some research we found the changes made in the recent upgrade make using our domain a lot harder and using the 3cx domain is recommended. So our new deployments are using the 3cx.us domain. My question is the systems that were installed as starpeer.com prior to 18 Vx and have been upgraded seem to be working fine with no issues. Is that going to change do I need to get all my systems off of the starpeer.com domain and over to the 3cx.us one?

Thank you

 

[SweetAction]

A recent install using our domain resulted in a lot of features of 3CX not working properly. After doing some research we found the changes made in the recent upgrade make using our domain a lot harder

Can you elaborate on this? Only then can we advise if the existing installs will continue without issue or not.

 

[David.Shoebridge]

We built a new system using our starpeer.com domain and certs and this caused us to not be able to program phones. We had to go into each phone and turn off certs (Yealink) and then we could manage the phone, but if the phone rebooted we could no longer manage the phone.

 

[Evolute IT]

We built a new system using our starpeer.com domain and certs and this caused us to not be able to program phones. We had to go into each phone and turn off certs (Yealink) and then we could manage the phone, but if the phone rebooted we could no longer manage the phone.

That means your SSL wasn't from a recognized CA or you didn't set it up properly.

 

[SweetAction]

Probably missing the intermediate cert in the chain. If you check against a tool like https://www.sslshopper.com/ssl-checker.html, what does it say?

 

[David.Shoebridge]

Thank you for the site that is what is missing. Interesting

 

[SweetAction]

adding the intermediate cert to the chain:
https://www.3cx.com/community/threads/update-renew-certificate.77468/post-356128

 

[SteveITS]

Kind of a side note, but browsers cache intermediate certs. So if it's a common one it could well be detected as valid by one browser or PC and not another. Meaning, the 3CX web client might not show a cert error. Over the years I have had to occasionally argue with people that their (non-3CX) web site is broken.

Using a tool like the the one linked above or Qualys will detect it. I recommend testing any custom cert.