Pi SBC Licensing error

[DylanB]

Hi People

I am trying to setup a Raspberry Pi 4 as a SBC.

I have reloaded the Raspbian OS multiple times and ruled the OS of the Pi out as a potential problem.
When I run the "wget https://downloads-global.3cx.com/downloads/misc/d10pi.zip; sudo bash d10pi.zip" command on the Pi the correct page pops up with the 2 options that are:
"1. 3CX"
"2. 3CX SBC"
I then press 2 and continue with the instillation.

The prompts of the PBX details are then entered and I receive this error:
"Unable to reach 3CX Sever at
https://.................com
Please double check "3CX Provisioning URL" value and
confirm that the SBC Trunk is created properly from within
your 3CX management Console.

Also 3CX must have a valid secure SSL Certificate so if
you have a custom certificate which has expired or not
renewed, the installation will fail."

I have made sure that the license is renewed and up to date.
The URL is correct because it was copied from the 3CX website.

The Pi runs and works as a SBC with a different PBX.

I am unsure if the Pi is giving this error because the PBX I want to set it u with has a wildcard certificate or if there is some sort of other problem?

 

[Evolute IT]

Hi People

I am trying to setup a Raspberry Pi 4 as a SBC.

I have reloaded the Raspbian OS multiple times and ruled the OS of the Pi out as a potential problem.
When I run the "wget https://downloads-global.3cx.com/downloads/misc/d10pi.zip; sudo bash d10pi.zip" command on the Pi the correct page pops up with the 2 options that are:
"1. 3CX"
"2. 3CX SBC"
I then press 2 and continue with the instillation.

The prompts of the PBX details are then entered and I receive this error:
"Unable to reach 3CX Sever at
https://.................com
Please double check "3CX Provisioning URL" value and
confirm that the SBC Trunk is created properly from within
your 3CX management Console.

Also 3CX must have a valid secure SSL Certificate so if
you have a custom certificate which has expired or not
renewed, the installation will fail."

I have made sure that the license is renewed and up to date.
The URL is correct because it was copied from the 3CX website.

The Pi runs and works as a SBC with a different PBX.

I am unsure if the Pi is giving this error because the PBX I want to set it u with has a wildcard certificate or if there is some sort of other problem?

What URL did you enter? Had your created the SBC entry in 3CX?

 

[DylanB]

What URL did you enter? Had your created the SBC entry in 3CX?

I used the "wget https://downloads-global.3cx.com/downloads/misc/d10pi.zip; sudo bash d10pi.zip" command on the Pi.
I got that URL form "https://www.3cx.com/docs/installing-pbx-raspberry-pi/" witch I followed step by step.

And I have created the SBC Entry in 3CX yes.

 

[ChrisC_3CX]

I am unsure if the Pi is giving this error because the PBX I want to set it u with has a wildcard certificate or if there is some sort of other problem?

Since you're using a custom FQDN do bear in mind that you might need to import the certificate on the Pi's OS level too.

EDIT:
What do you get if you run:

wget https://<FQDN>:<HTTPS_PORT>

 

[DylanB]

Since you're using a custom FQDN do bear in mind that you might need to import the certificate on the Pi's OS level too.

EDIT:
What do you get if you run:

wget https://<FQDN>:<HTTPS_PORT>

wget https://<FQDN>:<HTTPS_PORT>
bash: syntax error near unexpected token `newline'

 

[ChrisC_3CX]

Where <FQDN> put your own FQDN (e g mydomain.3cx.com) and where <HTTPS_PORT> put the port you configured for HTTPS (e g 443 or 5001).

For instance:

wget https://mydomain.3cx.com:443

 

[DylanB]

Where <FQDN> put your own FQDN (e g mydomain.3cx.com) and where <HTTPS_PORT> put the port you configured for HTTPS (e g 443 or 5001).

For instance:

wget https://mydomain.3cx.com:443

"GnuTLS: The TLS connection was non-properly terminated.
Unable to establish SSL connection."

 

[ChrisC_3CX]

I'll PM you for more information on this.

 

[DylanB]

I'll PM you for more information on this.

Thank you
Do you need any contact info?

 

[ChrisC_3CX]

Do you need any contact info?

No need, I have sent you a PM via the forums.

 

[SweetAction]

Does your SSL cert contain the intermediate certificate?

Customers who are using custom domain must ensure:

1. A valid certificate covering the installations FQDN as per common certificate validation rules. Wild cards can be used, however, wild card certificates cannot be re-used for secure SIP transport as per RFC later.
2. Necessary "Intermediate-Certificates" must be included in the Nginx web server certificate. Follow the guidelines of your certificate issuer. Generally, all certificate issuers rely on intermediate certificates. You can test your setup here: https://www.sslshopper.com/ssl-checker.html

 

[jamesnet]

@SweetAction is the answer. Beat my head against the wall on this one. Most things worked fine after I replaced my FQDN cert and I forgot that intermediate. Random things wouldn't work. SBC provisioning, pushing some updates to phones.