Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Flatly)
  • No Skin
Collapse
Brand Logo

NetXMS Forum

K

KSAIT

@KSAIT
Unfollow Follow
About
Posts
3
Topics
1
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • Unifi OS Server - How to detect as "Wireless Controller"
    K KSAIT
    Support

    Hi there,

    In the 6.0.2 release notes it said
    Added wireless controller bridge for UniFi controllers (PR #255)

    What would we need to do to enable this?
    We don't have a Unifi appliance, rather a basic Linux Ubuntu VM that runs Unifi OS Server https://help.ui.com/hc/en-us/articles/34210126298775-Self-Hosting-UniFi

    The VM has a NetXMS agent on & we've added the server into the wireless domain , but doesn't currently then pick up the Unifi install on the device at all - Is there a way at all to have NetXMS pick this up? I don't believe the server OS spits out SNMP at all, so it might not be possible but thought I'd ask!

    Kind regards


  • Change in certificate trust in v7?
    K KSAIT
    Support

    Hi there

    Ah thank you for such a quick response - Perfect yes that makes sense.

    I have copied the new ddl in & tested - All works perfectly now.

    Kind regards & thanks again for all your work on this product.


  • Change in certificate trust in v7?
    K KSAIT
    Support

    Hello - Aye this has caused us issues as well with the notification drivers on our Windows install.

    Telegram & our SMTP one both say

    curl_easy_perform() failed (60: SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19))
    

    SMTP one we can bypass this by adding "VerifyPeer=false" to the config as a temp fix (It's Office 365) but Telegram we can't.

    If we run "openssl s_client -connect api.telegram.org:443" on the machine it returns with

    Verify return code: 19 (self-signed certificate in certificate chain)
    

    Running

    openssl s_client -connect api.telegram.org:443 -CAstore org.openssl.winstore:
    

    Forces it to load in the windows certificate store & then passes all ok.

    So we've done what is in the post above

    Downloaded the Mozilla ca bundle and imported into our NetXMS Server config (netxmsd.conf) & the agent config on the server (nxagentd.conf) , but still fails on both drivers
    (It appears to be being loaded in)

    2026.11.04 11:34:48.438 *I* [config             ]      +- CACertificates
    2026.11.04 11:34:48.438 *I* [config             ]           value: C:\NetXMS\etc\cacert.pem
    

    Telegram uses a Godaddy cert if it helps at all

    Curl version is

    2026.11.04 11:34:48.456 *D* [init.curl          ] cURL initialized (version: libcurl/8.21.0 OpenSSL/3.5.9 zlib/1.3.1.1-motley WinLDAP)
    
  • Login

  • Don't have an account? Register

  • Login or register to search.
Powered by NodeBB Contributors
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups