Debian ISO Install Issue

Status
Not open for further replies.

Virtual3Rhys

SOHO User
Basic Certified
Joined
Nov 29, 2021
Messages
3
Reaction score
0
I am installing 3CX onto a KVM VM but it doesn't seem to install the reconfiguration file.

The virtual machine is being installed on an OVH Dedicated Server, which means that I need to use a failover IP where the gateway isn't part of the same subnet of the IP. This causes an issue at the networking part of the install process and prevents the reconfiguration file from being downloaded, this is fine because I can go into the shell and manually configure the interface and add the routes which allows me to ping 8.8.8.8 and resolve google.co.uk

I then exit the shell and click on the menu item "Download debconf reconfiguration profile" which now works and allows me to go through the entire install process. However, after the VM has rebooted the 3CX setup process doesn't start, it instead boots straight to login.

This process has worked previously so I am unsure why it no longer works. If anyone can help me out that would be great.
 
Last edited:
I am trying to install 3CX onto a KVM VM but I have an issue with the networking, even though I have previously used a workaround.

The issue is that the gateway IP for the VM is not in the same subnet as the interface IP, causing Debian to reject it. Typically, I can work around this by accessing the shell and manually adding the necessary IP and routes. Afterwards, I return to the installation menu and select "Download debconf reconfiguration file." After the installation, the VM reboots but 3CX doesn't appear to have been installed successfully but the file /etc/3cxpbx/3cxmarkers exists.

Here is a 5 minute video of the install -


I have reviewed the logs and I can see that the Debian install is successful however the /usr/local/bin/post-install doesn't run successfully.

Have you or anyone at 3CX got a workaround for this? I can provided any logs that are required.

Best Regards,
Rhys
 
Did I miss the bit where you restarted the interface to apply the new IP settings before testing?

Presumably at reboot your new settings are being applied whereas your test pings / lookups are using the IP configuration picked up from DHCP.
 
During the install I am not able to restart the interface. However adding the routes to the default gateway manually allows traffic to get to the internet using the DHCP settings.

After the server has reboot the internet works because I have defined a static IP address during the install process. That's what the test pings and lookups use.

I am trying to show that the server has an internet connection through the entire install process so I don't believe that is where the fault lies.
 
Status
Not open for further replies.

Forum statistics

Threads
111,974
Messages
590,081
Members
164,899
Latest member
mazet