I'm using 3CX version 20 Update 7 on a Debian 12 server, and I've run into a bizarre issue where entire extensions seem to vanish from the admin console without any clear reason. This isn't a case of call forwarding or disabled users; the extensions completely disappear. I've gone through the logs thoroughly and found no evidence of deletion events, permission issues, or database errors. Being the only admin with no regular user access to modify extensions adds to the confusion. Over just one week, more than eight extensions have disappeared, including one that was confirmed to be working last week. I even tried restoring a backup from two weeks ago, but the missing extensions didn't come back, which makes it even stranger. There were no restarts, updates, snapshots, or automated jobs running when this happened, and disk space is all good. The only log entries I see after an extension disappears are messages indicating that no user or outbound rule was found for that number, which is logical since 3CX no longer recognizes the extension. Has anyone else experienced something similar in version 20? I'm looking for any insights or suggestions you might have!
3 Answers
I haven't experienced this personally, but if I were you, I'd strongly consider setting up a high-availability mode with two VMs. This can safeguard against such issues in the future. Even for SBCs, it's wise to use redundancy if you're not utilizing router phones. Here’s a link to 3CX's failover documentation if that helps: [3CX Failover](https://www.3cx.com/docs/failover/). Hopefully, you'll get to the bottom of this soon!
That sounds really strange! It might be worth checking if your 3CX software is compatible with the system libraries on Debian 12, especially since you mentioned extensions disappearing after updates. Sometimes, issues arise when software interacts with outdated libraries, but if you haven't updated recently, this might not be your case. Double-check your database integrity as well—corruption might lead to such erratic behavior. Also, ensure that there aren't any automated scripts that could potentially touch your database.
I've seen odd behaviors like this, and it could be related to database integrity or permissions. Even if you're the only admin, it's a good idea to verify that your 3CX data folder has the correct file system and database permissions. Also, check for any log files, particularly in `/var/log/3cxpbx`, around the time the extensions disappeared. Sometimes automated scripts unintentionally modify entries in the database, so keep an eye on that too!
Thanks for the tip! Just to clarify, there were no OS or 3CX updates when this started. The last 3CX update was over six months ago, and Debian hasn't been upgraded either, so the issue came out of the blue.