3CX Linux Repository Returning “NOSPLIT / Invalid Clearsigned File” on Debian 11/12 (Cannot Install or Upgrade PBX)

[ICR10500]

Hi everyone,


I’m looking for assistance or clarification regarding an issue with the 3CX Linux repositories. For the past 24+ hours, the Debian repo has been returning errors that prevent package retrieval, installation, or upgrades.


I am unable to install 3CX on either Debian 11 or Debian 12 because the repository is returning a clearsigned file error with the message “NOSPLIT”, which appears to indicate an invalid signature or a corrupted Release/InRelease file.

Environment​

• Debian 11 (Bullseye) and Debian 12 (Bookworm) tested
• Azure VM (production PBX)
• Local Hyper-V test VM
• Same result across multiple networks (office, home, mobile hotspot)
• No proxy, no SSL inspection
• Problem confirmed via curl -I and apt-get

---

Error Output​

Err: http://downloads.3cx.com/downloads/3cxpbx bullseye InRelease Clearsigned file isn't valid, got 'NOSPLIT' (does the network require authentication?)
E: The repository 'http://downloads.3cx.com/downloads/3cxpbx bullseye InRelease' is not signed

The same happens for Bookworm.
http://downloads.3cx.com/downloads/3cxpbx bookworm

The repository was working for me up until yesterday afternoon.

I can reach the server via HTTP(S), but the Release/InRelease file appears invalid or corrupted. The SBC repository (repo.3cx.com/3cx) is also intermittently returning GPG key errors unless removed.

---

What I Have Already Tried​

• Multiple Debian versions (11 and 12)
• Different Azure VM sizes and generations
• Local Hyper-V VMs to rule out Azure network
• Switching between downloads.3cx.com and downloads-global.3cx.com
• Removing and re-adding the GPG key
• Forcing apt to ignore expiration (Acquire::Check-Valid-Until=false)
• Testing via curl -I (no proxy, no packet modification)
• Reinstalling from scratch (same error immediately after adding repo)

Everything points to a problem with the repository metadata/signature rather than my environment.

---

Why This Is Time-Critical​

My 3CX v18 license expires on December 1st.
I planned to migrate to a new v20 installation on Debian 11/12, but currently the repo failure makes this impossible.


The ISO installer works fine on-prem, but I also need the ability to install on Azure.

---

Questions​

1. Is this a known issue with the 3CX Debian repositories?
2. Is there an ETA for when the repository metadata/signatures will be fixed?
3. Is there a temporary alternative repo or mirror that can be used?
4. Is the Debian repo intentionally blocked or deprecated? (Just confirming.)
5. Does 3CX recommend installing via ISO only at this time?

Any official guidance or confirmation would be greatly appreciated so I can plan my production upgrade path before December 1st.

Thank you in advance.

— Andrew

 

[KyriacosS_3CX]

Can you advice the contents of your /etc/apt/sources.list files?

 

[KyriacosS_3CX]

Hi,

In case you did not resolve this already, the repository URLs you posted are very old, and have not been in use for several years.

Please use the official 3CX ISO or to deploy in Azure etc you can use the marketplace images.

 

[SteveITS]

Does 3CX recommend installing via ISO only

AFAIK 3CX only supports ISO installs, or marketplace images. https://www.3cx.com/docs/manual/install/#h.kkz6f4xtt9u

Also, re: license, you'll need to renew the old license and then it will work after migration.

 

[ICR10500]

Thank you everyone for the replies.
I tried the marketplace image on azure and got so far but it didn't work well.

I restarted the process with a clean install and follow the steps in this github ghist install 3CX on Debian 12 Bookworm · GitHub
I got to the point where I could load a configuration file using the web.

However, that didn't go so well, and I now have a FQDN lock on my domain, as I made too many attempts to register because of a problem in the config file I uploaded. But that is a different issue and not related to this issue.

I'll be working over the weekend to get this fixed. Our license expires on 1st December. So, time is short!

 

[ICR10500]

I successfully upgraded our system to v20. I performed an in-place upgrade to do this.