3CX broken after upgrading from V20 U6 to U7

[PBX_Programmer]

I've got a little on-premises virtualised 3CX system which I use for testing things like new updates before I roll them out to production systems.

Today I was getting ready to perform a backup in readiness for upgrading from V20 U6 to U7, but as I was doing that the system decided to go ahead and update automatically. It didn't come back up again.

I gave it an hour or more and still it was just saying that it was trying to reconnect. I refreshed the page and it took me to the login page ok, but when I try to log in it says "3CX Admin Console is not responding. Please refresh and try again". I did this several times but I get the same result.

In the console I ran the command "service 3CX* status", but nothing at all was returned.

I then ran "3CXStopServices" followed by "3CXStartServices" which eventually returned the following:



I must confess I am not very familiar with Debian or just Linux in general. From the above though, I'm guessing the 3CXCfgServ01 service failed to start for whatever reason, and then all the other services subsequently failed to start because they were dependant on that one starting up first?

What I'm currently trying to do is view those log files it mentions to see if I can figure out why it failed. But is this a common thing? Am I the only one with this issue? I can't see any other threads about it so far. Luckily it's a virtual machine and I've got snapshots of it so I have been able to roll it back to a state prior to it breaking. I have attempted the same procedure 3 times now, just going to updates within the 3CX management console and choosing the new release, and it fails in the same way every time.

Is there something obvious that i might be doing wrong? I don't want to update and production systems and end up with them broken in the same way.

Thanks!

 

[Charles_3CX]

Could you please open a ticket with us at 3CX technical support via your partner portal so we can request the logs for review?

 

[SBV-IT]

3CX v20.0 Update 7 (Build 1057) – Database fails to start due to missing *timescaledb* library​

If someone runs into the same problem I had after updating to 3CX Version 20.0 Update 7 (Build 1057):
the issue seems to be that the shared library timescaledb is not available in the PostgreSQL database.
Because of that, the database fails to start, and 3CX cannot update its tables.

---

Fix​

You need to add timescaledb to the PostgreSQL configuration and reinstall 3CX to trigger the database schema upgrade.

Steps:

1. Edit the PostgreSQL configuration file:

sudo nano /etc/postgresql/15/main/postgresql.conf

Add or modify the following line:

shared_preload_libraries = 'timescaledb'

2. Restart the PostgreSQL service:

sudo systemctl stop [email protected]
 sudo systemctl start [email protected]

*(Alternatively you can use `sudo systemctl restart [email protected]`.)*

3. Check if PostgreSQL is running:

sudo systemctl status [email protected]

4. Reinstall 3CX to retrigger the database update:

sudo apt remove 3cxpbx
sudo apt install 3cxpbx

---

Result​

After that, 3CX should successfully upgrade the database and start again.

---

Post formatted and proofread with the help of ChatGPT (GPT-5).

 

[AndreasPo_3CX]

Hi @SBV-IT

I sent you a PM

 

[Marco pbx]

I have another issue after upgrading to U7. , hosted 3cx 24sc
I have sip trunk registrations to other pbx system and time to time it starts to fail. Other pbx system says they do not have any network issues.



What can be the issue from our side to fix this sip register and rtp issue? we can not hear the customers time to time.

Should i uncheck the option ( Automatically bind to IPV6 adapters) box? i do not remember if it was there before the update.

 

[KyriacosS_3CX]

Should i uncheck the option ( Automatically bind to IPV6 adapters) box? i do not remember if it was there before the update.

If your network generally does not use IPv6, go ahead and uncheck it. This though might not be the actual cause of the problem, but unchecking it will be one troubleshooting step.