You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
NethVoice: report API login fails due to self-signed SSL certificate #7922
The NethVoice CTI component of the NethVoice module attempts to connect to the NethVoice report API but fails when the server presents a self-signed SSL certificate. This causes the login process to abort, resulting in issues accessing or updating reporting data.
Steps to reproduce:
Install NethVoice with certificate.
Start or reload the NethVoice module so it attempts to log in to the report API.
Observe the logs for authentication or connectivity errors with the reporting endpoint.
Expected behavior:
The NethVoice module should connect to the report API even if the server uses a self-signed SSL certificate (when administrative intent allows), or should provide a clear method for handling/reporting certificate validation options.
Actual behavior:
The module’s login request to the report API fails when a self-signed certificate is detected. The following warning is logged, and reporting data cannot be retrieved:
2026-02-23T09:21:58+01:00 [1:nethvoice5:nethvoice5] 2026-02-23T09:21:58+01:00 - warn: [arch_astproxy] problem logging in to nethvoice report with request: self signed certificate in certificate chain
api-cli run update-module --data '{"module_url":"ghcr.io/nethesis/nethvoice:1.8.0-testing.38","instances":["nethvoiceX"],"force":true}'
The CTI now logs in to the report API on its local address (127.0.0.1:REPORTS_API_PORT, from listen_address in the report conf.json) instead of https://NETHVOICE_HOST/pbx-report-api, so the certificate on the NethVoice host, DNS and NAT no longer matter for this call.
Setup: NethVoice with an active subscription (the report API refuses the login without it), reports enabled. CTI log lines are read with runagent -m nethvoiceX podman logs nethcti-server 2>&1 | grep -i nullCallPeriod (or the module logs in the cluster-admin UI).
Test Case 1 - Self-signed certificate (the bug)
Before the update, with a self-signed certificate on the NethVoice host (no Let's Encrypt), the log shows problem logging in to nethvoice report with request: self signed certificate in certificate chain
After the update the log shows nullCallPeriod updated getting it from nethvoice-report: <value> and no TLS error
Change the "null call" time in the reports settings: within a minute the log shows the new value
Test Case 2 - Valid certificate (regression)
Same checks as Test Case 1 with a Let's Encrypt certificate: nullCallPeriod updated ... with the configured value, no errors
Test Case 3 - Null call period still applied
With a "null call" time of e.g. 10 seconds, a queue call abandoned before 10 seconds is not listed in the queue recall lists, one abandoned after 10 seconds is
Test Case 4 - Restore
Restore a NethVoice backup (new instance, so a new REPORTS_API_PORT): within a minute of startup the CTI log shows nullCallPeriod updated ..., with no ECONNREFUSED repeating
Test Case 5 - Reports UI unchanged
The reports web UI (/pbx-report) still logs in and shows data, settings can be saved
Activity
edospadoni commentedon Oct 23, 2026
Test
Release: https://github.com/nethesis/ns8-nethvoice/releases/tag/1.8.0-testing.38 or later (nethesis/ns8-nethvoice#1100, nethcti-server nethesis/nethcti-server#372)
The CTI now logs in to the report API on its local address (
127.0.0.1:REPORTS_API_PORT, fromlisten_addressin the reportconf.json) instead ofhttps://NETHVOICE_HOST/pbx-report-api, so the certificate on the NethVoice host, DNS and NAT no longer matter for this call.Setup: NethVoice with an active subscription (the report API refuses the login without it), reports enabled. CTI log lines are read with
runagent -m nethvoiceX podman logs nethcti-server 2>&1 | grep -i nullCallPeriod(or the module logs in the cluster-admin UI).Test Case 1 - Self-signed certificate (the bug)
problem logging in to nethvoice report with request: self signed certificate in certificate chainnullCallPeriod updated getting it from nethvoice-report: <value>and no TLS errorTest Case 2 - Valid certificate (regression)
nullCallPeriod updated ...with the configured value, no errorsTest Case 3 - Null call period still applied
Test Case 4 - Restore
REPORTS_API_PORT): within a minute of startup the CTI log showsnullCallPeriod updated ..., with noECONNREFUSEDrepeatingTest Case 5 - Reports UI unchanged
/pbx-report) still logs in and shows data, settings can be savedfix(astproxy): reach the report API on its local address (#372)
fix(cti): reach the report API on its local address (#1100)