sbc on debian, ssl error

[korazy]

I have my on-premise debian sbc with vultr hosted 3cx. Last night, my sbc stopped working and is in an endless loop with registration up then down. Below is from the the file /var/log/3cxsbc/3cxsbc.log on my sbc that shows an ssl error. This error log repeats every 5 minutes-ish. How do I fix this?

My vultr hosted 3cx is working.
With my iphone, I can make and receive calls as normal using the 3cx app.
I can logon to the management console.
The let's encrypt SSL cert for managment console is valid.
The SBC has been running for about a year, first time having a problem.


CRIT | 20231209-124234.842 | 3CX | SBC | 139799500306368 | Log.cpp:159 | Log started: type = file, level = ERR, size = 104857600, resip = ERR, remote = -1 CRIT | 20231209-124234.957 | 3CX | SBC | 139799500306368 | Bridge.cpp:28 | System Clock: resolution 0 microseconds, not monotonic ERR | 20231209-124234.958 | 3CX | RESIP | 139799500306368 | ssl/Security.cxx:268 | Error calling stat() for /var/lib/3cxsbc/.sipCerts: No such file or directory CRIT | 20231209-124235.049 | 3CX | SBC | 139799500306368 | RPiTunnel.cpp:373 | Running in console mode ERR | 20231209-124241.199 | 3CX | SBC | 139799500306368 | TunnelTcp.cpp:607 | SSL error (5): ERR | 20231209-124241.199 | 3CX | SBC | 139799500306368 | TunnelTcp.cpp:305 | Bridge failure on secure read: Unknown system error ERR | 20231209-124247.351 | 3CX | SBC | 139799500306368 | TunnelTcp.cpp:607 | SSL error (5): ERR | 20231209-124247.351 | 3CX | SBC | 139799500306368 | TunnelTcp.cpp:305 | Bridge failure on secure read: Unknown system error ERR | 20231209-124253.532 | 3CX | SBC | 139799500306368 | TunnelTcp.cpp:607 | SSL error (5): ERR | 20231209-124253.532 | 3CX | SBC | 139799500306368 | TunnelTcp.cpp:305 | Bridge failure on secure read: Unknown system error CRIT | 20231209-124253.532 | 3CX | SBC | 139799500306368 | RPiTunnel.cpp:390 | Stopping: Maximum number of connection attempts reached CRIT | 20231209-124253.660 | 3CX | SBC | 139799500306368 | RPiTunnel.cpp:385 | ** Main console thread exits.

 

[korazy]

In addition to the original issue, the SBC is a vm on esxi. I deleted the old sbc and created a new one using the 3cx debian download and the problem is the same.

 

[korazy]

In addition to the original problem. On the SBC, after fresh install. when I try to run apt-get update, I get the following error:

root@ftincsbc1:~# apt-get update
Hit:1 http://repo.3cx.com/3cx buster InRelease
Get:2 http://downloads-global.3cx.com/downloads/debian buster-testing InRelease
Hit:3 http://deb.debian.org/debian buster InRelease
Get:4 http://security.debian.org buster/updates InRelease [34.8 kB]
Hit:5 http://deb.debian.org/debian buster-updates InRelease
Err:2 http://downloads-global.3cx.com/downloads/debian buster-testing InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D34B9BFD90503A6B
Reading package lists... Done
W: GPG error: http://downloads-global.3cx.com/downloads/debian buster-testing InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D34B9BFD90503A6B
E: The repository 'http://downloads-global.3cx.com/downloads/debian buster-testing InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

 

[N_G]

An sbc should not be in the cloud but on the local network where the phones are.

 

[korazy]

An sbc should not be in the cloud but on the local network where the phones are.

I have my on-premise debian sbc with vultr hosted 3cx. The SBC is on-premise. The 3cx pbx is hosted with vultr.

 

[SweetAction]

If you put in your FQDN of your 3CX server and port here, does it come back with any errors?
https://www.sslshopper.com/ssl-checker.html

 

[korazy]

I'm not sure what happend. I left the SBC off over night, turn it on this afternoon, shoftly after my 12:58pm CST response and it's been working again.

 

[N_G]

@korazy sorry i misread your post. Just to be sure its a copmletely stock SBC, no changes to the linux install?

 

[korazy]

@korazy sorry i misread your post. Just to be sure its a copmletely stock SBC, no changes to the linux install?

Not sure if you saw my previous post, but it is working now. I had the SBC turned off overnight and then turned it on the next day and it just started working.

The SBC is a guest VM on ESXI. I add vmware tools to debian. That is the only change.