Unable to install from Debian v10 ISO

[CSerpent]

I'm having a very big oddity on installing from the v10 ISO today. It goes through the standard Deb build, networking all ok etc etc...

However when it comes to installing, it gives no version number, just "3CX Version" and "3CX SBC Version". It then basically goes to the standard Deb prompt, no installation.

Any thoughts?

 

[CSerpent]

Appears it may be a fault with the server's SSL cert? Public key not available?

 

[CentrexJ]

Never saw that before. Does the vm have internet access? What system are you using to run it?

 

[CSerpent]

Yep, you can do an apt-get as normal from the Deb servers, it's the GPG cert from downloads-global.3cx.com that's failing. Running on an ESXi 6.7 server that runs another 3CX system quite happily.

 

[CSerpent]

Kind of solution from this post

wget -O- http://downloads-global.3cx.com/downloads/3cxpbx/public.key | sudo apt-key add -

Just not ideal as we then have to start the 3CX install again.

 

[ChrisC_3CX]

This should've not been an issue.

Have you used the latest 3CX v18 ISO found in the partner portal downloads section?

 

[CSerpent]

Absolutely, Chris. This is where the ISO came from.

 

[ChrisC_3CX]

That is strange, the fact that you do not see the version numbers when selecting PBX or SBC suggests that there may have been a communication issue with the repositories preventing the installation from retrieving the available versions during the early installation process. If this is the case, it would explain why the public key is missing also as that is also retrieved during this process.

Are there any network restrictions in place that may be contributing to the issue at all?

Also, had you used the 3CX ISO to deploy the instance from the beginning or did you perhaps use a VMWare template based on the ISO?

 

[CSerpent]

There definitely wasn't a communication issue, I tested the same box with a standard Deb ISO and that worked absolutely fine including all apt pulls. There's no network restrictions on this box either, as that was also tested.

This was the v18 ISO pulled directly from the 3CX portal and uploaded to the ESXi box.

 

[ChrisC_3CX]

Out of curiosity, had you happened to try the following on the Host in question at all:

wget http://downloads-global.3cx.com/downloads/3cxpbx/public.key

Does it actually download the key?

 

[CSerpent]

I ran (on Saturday):
wget -O- http://downloads-global.3cx.com/downloads/3cxpbx/public.key | sudo apt-key add -
Which succeeded.

Just ran
wget http://downloads-global.3cx.com/downloads/3cxpbx/public.key

And that works from it.

 

[ChrisC_3CX]

Okay so there seems there's nothing preventing the specific client from downloading the key in general.

This is quite strange, had you only made one attempt to deploy this instance or did you make multiple attempts with each one failing with the same results? In other words, if it indeed was only one attempt, is there any chance it was just a network hiccup with the one attempt?

 

[CSerpent]

Okay so there seems there's nothing preventing the specific client from downloading the key in general.

This is quite strange, had you only made one attempt to deploy this instance or did you make multiple attempts with each one failing with the same results? In other words, if it indeed was only one attempt, is there any chance it was just a network hiccup with the one attempt?

Multiple attempts at building from the same ISO. Each time, same result. Definitely wasn't a network hiccup as this was over several hours over a leased line.

 

[Lee Cramman]

Could this be an over eager security appliance intercepting the request? I've seen some that intercept web requests and replace them with their own response, including an unsigned security cert.

 

[ChrisC_3CX]

@CSerpent

I'll PM you shortly for more information on this matter.

 

[CSerpent]

Could this be an over eager security appliance intercepting the request? I've seen some that intercept web requests and replace them with their own response, including an unsigned security cert.

I had pondered that, but the VM was using an existing IP that had already been configured for 3CX, and it had a public IP on ens224 too (tested with ens192 with and without gateway/routing rules)