Skip to content

NethVoice: report API login fails due to self-signed SSL certificate #7922

Open

Description

@Amygos

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:

  1. Install NethVoice with certificate.
  2. Start or reload the NethVoice module so it attempts to log in to the report API.
  3. 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

Components:

See also

Activity

  1. added this to the NethVoice 1.6 milestone on Mar 18, 2026
  2. added
    nethvoiceBug or features releted to the NethVoice project
    nethvoice-ctiThe issue is related to NethLink (NethVoice Web client)
    on Mar 18, 2026
  3. self-assigned this
    on Mar 18, 2026
  4. moved this from Todo to In Progress in NethVoiceon Oct 23, 2026
  5. edospadoni commented on Oct 23, 2026

    @edospadoni
    Member

    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)

    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
  6. added
    testingPackages are available from testing repositories
    on Oct 23, 2026
  7. moved this from In Progress to Testing in NethVoiceon Oct 23, 2026
  8. removed their assignment
    on Oct 26, 2026
  9. removed
    testingPackages are available from testing repositories
    on Oct 26, 2026
  10. moved this from Testing to Verified in NethVoiceon Oct 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    nethvoiceBug or features releted to the NethVoice projectnethvoice-ctiThe issue is related to NethLink (NethVoice Web client)verifiedAll test cases were verified successfully

    Type

    Projects

    • Status
      Verified

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions