Solved Installation of 3CX V16 with Debian ISO issue

[TazDevil56]

When I configure a fixed IP during installation process on an Hyper-V VM the installation script cannot connect to the 3CX server in order to install the PBX.
Installing with DHCP feature and manually changing IP address works fine.

Did someone else has already encoutered this issue ?

 

[cobaltit]

Are you putting in reachable DNS servers along with the static IP?

 

[NZvoip]

I've had this issue several times with ISP provided routers that block traffic by default unless they know about the device.
What is device is handing out DHCP addresses?

 

[TazDevil56]

@cobaltit : Yes I'm putting a reachable gateway and I've tried several reachable DNS server adresses (router IP address, Google DNS servers ...)

@NZvoip : You're right my DHCP server is my ISP router, I'll give a try with another router.

Is there a way to pause the installation script and get a console in order to make test on IP configuration (ping, nslookup, ...) ?

 

[StefanW]

one common issue, is when an IP was given via DHCP then you may have IPv6 DNS servers in your resolve.conf file but only IPv4 addresses on the ethX interface.

cat /etc/resolv.conf

to see your current DNS servers.

 

[TazDevil56]

@StefanW : You're right !!! As the preinstall network IPV6 auto-configuration sets only IPv6 DNS servers in resolve.conf and manual configuration of network (as mentioned here on step 2, point 4 : https://www.3cx.com/docs/manual/installing-debian-linux-pbx/) only sets IPv4 addresses on the eth0 interface.
So I've succeeded in auto-installing 3CX with the 3CX Debian ISO by deactivating IPv6 support on my router, so the network auto-configuration sets an IPv4 DNS servers in resolv.conf and I can further specify IPv4 adresses in manual configuration without any problem.

This issue is not a V16 specific issue as it also happens with V15.5 ISOs.

Thanks a lot StefanW

 

[NateDoc]

I don't think this is the only thing going on here - I've done two SBC setups recently and both had IPv4 resolv.conf info and DHCP still doesn't work. Had to override both installs once the Debian finished by booting in recovery mode and setting static info for the interface. Both on different sites and both using different virtualization. So perhaps there's something else wrong with the ISO?

 

[cobaltit]

Ok, so you didn't have reachable DNS servers on the install, at least from the VM perspective.

Btw, this isn't a 3CX issue but a Debian issue. 3CX only defines/scripts the installation and packages but the actual network handling is stock Debian.

 

[NateDoc]

Oh totally (it being a Debian issue) - I'm wondering if the Debian install / ISO changed recently as I've seen it work properly not that long ago. It's weird - DHCP is working to provide DNS accurately (as seen by what's in the resolv.conf), but not the interface info.

 

[cobaltit]

Who knows. Being dual homed is starting to create lots of 'issues' like this. Too many assumptions at various levels as to the availability of things when being dual homed or when you get DNS results in both formats. We used to see that a lot with Office 365 and with the OpenDNS Umbrella client although it's gotten better. Just another transitional bump.