Hetzner Cloud 3CX from Debian 9 to Debian 10 error

[johnvam]

Hello!
I use for my clients Hetzner Cloud servers. Today I installed a new Debian 9 server with 3CX and tried to upgrade to Debian 10 using the upgrade button in Updates section.
But update fails. Check the attached file.
Any idea?

As always I install Debian 9 3CX using the following commands :
apt-get update
apt-get upgrade -y
apt-get dist-upgrade -y
wget -O- http://downloads-global.3cx.com/downloads/3cxpbx/public.key | apt-key add -
echo "deb http://downloads-global.3cx.com/downloads/debian stretch main" | tee /etc/apt/sources.list.d/3cxpbx.list
sh -c 'apt update; apt upgrade -y; apt full-upgrade -y; apt-get autoremove -y; apt-get autoclean -y'
apt install net-tools dphys-swapfile
apt install 3cxpbx -y

 

[StefanW]

Dear @johnvam

not that I could say something for/against the Hetzner cloud itself, but it is not officially supported by 3CX.
We don't test our software there and cannot guarantee what will happen there later. For example the upgrade from Deb9 to Deb10 we don't check there if it works or not...

I strongly advise you to use one of the tested and maintained hosters, such as Google, Amazon (EC2 or LightSail) or Microsoft Azure.

And when I see that you have already time update issues, and VOIP is very time accuracy dependent...
systemd-timesyncd -- Timed out

 

[Alphabetic]

Might want to check you got the NTP installed

apt update
apt install ntp

 

[johnvam]

Dear @StefanW
we use 3CX for 3+ years and we have almost 300 production servers @ Hetzner without any problem at all!!
Till now we use Debian 9 installations and using command line we install 3CX successfully.
We are not able to change the way we work because this way make us more competitive in the Greek market. So we earn both, you and us.
I thing that you should inform us for manual installation of 3CX on Debian 10 because many Cloud server providers do not support ISO installation.
Thank you

 

[ChrisC_3CX]

@johnvam

As you may already know, installing 3CX via the command line is no longer a supported nor recommended method as part of our effort to streamline the 3CX deployment and future proof installations for upcoming updates/upgrades as well as ensure smooth operation of the PBXs functionality.

That said, you could potentially check if your cloud provider allows uploading a custom ISO either by default or through a request, and if yes, that would probably be the path that requires the least effort at least for now.

 

[johnvam]

@johnvam

As you may already know, installing 3CX via the command line is no longer a supported nor recommended method as part of our effort to streamline the 3CX deployment and future proof installations for upcoming updates/upgrades as well as ensure smooth operation of the PBXs functionality.

That said, you could potentially check if your cloud provider allows uploading a custom ISO either by default or through a request, and if yes, that would probably be the path that requires the least effort at least for now.

I will ask my cloud provider but as you know most of them do not support ISO uploading. I could use Digital Ocean as you do. Can you share how to install 3CX on Digital Ocean in order to be fully aligned with your support?
Thank you

 

[johnvam]

You advertise that 3CX is a cloud pbx but you support only ISO installation and you know better than me that none of the major cloud providers support iso file. You could at least help us on that. You promote digital ocean google and azure. You could offer us instructions how to install on them and be aligned with your support.
Thank you

 

[Evolute IT]

You advertise that 3CX is a cloud pbx but you support only ISO installation and you know better than me that none of the major cloud providers support iso file. You could at least help us on that. You promote digital ocean google and azure. You could offer us instructions how to install on them and be aligned with your support.
Thank you

You can try Vultr. They do support custom ISOs.

AWS, Azure and Google each have a dedicated marketplace image for 3CX.

As for DigitalOcean, it's still a mistery to me as well lol

 

[johnvam]

Vultr is not as good as digital ocean. As for azure google and awa they are very expensive for the Greel market.
So 3CX support team must give us instructions for digital ocean. They use them for hosted. So they can share the knowledge with their partners.

 

[StefanW]

Digital Ocean (DO) will be soon an official part of our deployment wizard + marketplace.

 

[johnvam]

Digital Ocean (DO) will be soon an official part of our deployment wizard + marketplace.

OK that sounds great!!!
How often? Because we have 300 3CXs on Hetzner that cannot be upgraded to v18...
So we must start the migration all of them to DO.
Thank you

 

[johnvam]

Digital Ocean (DO) will be soon an official part of our deployment wizard + marketplace.

Also I have one very important question. Now all the v16 manual installations cannot be upgraded to v18 because procedure fails. When we have the first stable v18, all v16 will be upgraded to v18 automatically if automatic upgrade is enabled on PBX or not?
I'm afraid system failure in case of automatic upgrade to the first stable v18.
Thank you

 

[StefanW]

Check the error mail of the upgrade attempt why it stops, there is a report log attached.

No, version upgrades (v16 -> v18) are not automatically applied even automatic update is on, only updates (U1 ->U2)

 

[akakern95]

Hi johnvam,

we also recently switched to Hetzner Cloud because hosting is extremely cheap compared to AWS.
I faced the same error as you and I was able to upgrade after deleting the 2 hetzner entries in the source list folder.

After investigating the upgrade log i found those lines:
Preparation: Found an uncommon source list in /etc/apt/sources.list.d/: hetzner-mirror.list - 0[39m
::FAIL::

After like 40 minutes I still did not get an update complete email so I checked the machine. My network interface did not get started again after upgrading.
So I did another "systemctl restart networking" and I was able to connect again.

I have to do some further testing to see if everything works as expected but ATM it looks fine.

I am afraid that all my other instances hosted at AWS will fail the upgrade too if a little change like adding a source list kills the upgrade process.
In the past CLI installation was supported and to renew our certs on those instances we installed ACME and tmux on those Debians.

 

[StefanW]

The sources check is a pre-check item before we start the upgrade process.
Therefore I would strongly dought that the "attempt" has caused your network interface to stop.

However, if we see sources we don't know, and we know what is in a default AWS EC2 instance, we will just stop.

 

[akakern95]

Hi @StefanW
I think you misunderstood me. The failed attempt did not stop the network interface. It just failed because of the precheck.
But after I deleted the "unknown" source lists the upgrade was working and after upgrading to Debian 10 it stopped the network interface.
In this case, it was a Hetzner Cloud instance.

 

[StefanW]

I assume that you have no Debian 9 repositories now to get sources from?

 

[akakern95]

I assume that you have no Debian 9 repositories now to get sources from?

I think it should be fine. The Hetzner Sources were just mirrors.
When i do an "apt update" i contacts those servers:

Get:1 http://security.debian.org buster/updates InRelease [65.4 kB]
Hit:2 http://downloads-global.3cx.com/downloads/debian buster-testing InRelease
Hit:3 http://deb.debian.org/debian buster InRelease
Get:4 http://deb.debian.org/debian buster-updates InRelease [51.9 kB]
Hit:5 http://downloads-global.3cx.com/downloads/debian buster InRelease

 

[StefanW]

buster-testing InRelease?
When you are on deb9 then this should be not Buster...

 

[akakern95]

buster-testing InRelease?
When you are on deb9 then this should be not Buster...

I think you still misunderstand me.

I was able to do the upgrade to V18 and Debian 10.
I just had to delete the hetzner sources in the source list folder and then the upgrade was working.