Web Conference Unable to connect to server | MDaemon Technologies, Ltd.

Web Conference Unable to connect to server


  • I am on MDaemon 25.5.1 hosted on Windows 2019 Standard. I am unable to use the Web Conference feature. When I login to Webmail I get a small temporary pop-up that says "Web Conference Unable To Connect To Server" I have the Conference feature enabled, to the best of my knowledge, everywere it should be. I have a valid certificate issued from a trusted third party authority. Below is my RTC-ServerMain.log


    -----------------------------------------
    2025-10-30 13:23:45 | CRITICAL | MDaemon RTC Server starting...
    2025-10-30 13:23:45 | CRITICAL | loading directories
    2025-10-30 13:23:45 | CRITICAL | Making sure that this is running on the primary node
    2025-10-30 13:23:45 | CRITICAL | Loading config file...
    2025-10-30 13:23:45 | CRITICAL | No valid IP address found in configuration. Attempting fallback to domain IPs.
    2025-10-30 13:23:45 | CRITICAL | Config loaded
    2025-10-30 13:23:45 | DEBUG | Configuration: {"logLevel":0,"maxRoomPeers":20,"signalPort":3443,"stunServer":{"announcedIps":["::1"],"maxPort":11000,"minPort":10000},"turnServer":{"provider":""},"version":"1.0.3","pemDir":"C:\\MDaemon\\PEM\\_rtcserver"}
    2025-10-30 13:23:45 | DEBUG | Initializing servers...
    2025-10-30 13:23:45 | CRITICAL | No valid HTTPS certificate files found. Extracting MDaemon certificate as fallback.
    2025-10-30 13:23:45 | CRITICAL | If you want to use a different certificate, please place the privatekey.pem and publickey.pem files in the C:\MDaemon\PEM\_rtcserver directory, and restart RTCServer.
    2025-10-30 13:23:45 | INFO | Extracting certificate...
    2025-10-30 13:23:45 | DEBUG | Certificate extraction output: iniFilePath: ..\App\MDaemon.inistore_location: LocalMachinestore_name: Mycert_hash: <REDACTED>
    2025-10-30 13:23:45 | ERROR | Certificate extraction stderr: Error in PFXExportCertStoreEx (get size). Error code: 2148073483Error message: Key not valid for use in specified state.The key is not valid for use in specified state.
    2025-10-30 13:23:45 | ERROR | Failed to load certificate: ENOENT: no such file or directory, open 'C:\MDaemon\RTCServer\credentials\certificate.pfx'
    2025-10-30 13:23:45 | ERROR | Failed to copy public key from PFX: ENOENT: no such file or directory, copyfile 'C:\MDaemon\RTCServer\credentials\publickey_from_pfx.pem' -> 'C:\MDaemon\PEM\_rtcserver\publickey_from_pfx.pem'
    2025-10-30 13:23:45 | ERROR | Failed to copy private key from PFX: ENOENT: no such file or directory, copyfile 'C:\MDaemon\RTCServer\credentials\privatekey_from_pfx.pem' -> 'C:\MDaemon\PEM\_rtcserver\privatekey_from_pfx.pem'
    2025-10-30 13:23:45 | DEBUG | Using extracted certificate files from MDaemon
    2025-10-30 13:23:45 | ERROR | Error deleting temporary certificate: ENOENT: no such file or directory, unlink 'C:\MDaemon\RTCServer\credentials\certificate.pfx'
    2025-10-30 13:23:45 | ERROR | Error deleting temporary public key: ENOENT: no such file or directory, unlink 'C:\MDaemon\RTCServer\credentials\publickey_from_pfx.pem'
    2025-10-30 13:23:45 | ERROR | Error deleting temporary private key: ENOENT: no such file or directory, unlink 'C:\MDaemon\RTCServer\credentials\privatekey_from_pfx.pem'
    2025-10-30 13:23:46 | INFO | STUN Servers initialized
    2025-10-30 13:23:46 | INFO | Getting active rooms to restore
    2025-10-30 13:23:46 | INFO | Signal server running on port 3443
    2025-10-30 13:23:46 | DEBUG | No active rooms found



  • I see two issues.

    1. You need to add the local and/or public IP addresses of the MDaemon server as STUN server IP addresses.  You can do this by logging into Remote Administration as a Global Admin and going to Main | Web Conferencing Server.

    2. The export of the MDaemon certificate is failing, this is probably because its marked as not exportable in the Windows Certificate Manager.  You'll need to either re-import the certificate into the Windows Certificate store as exportable or place a privatekey.pem and publickey.pem files in the C:\MDaemon\PEM\_rtcserver directory, and restart RTCServer.


  • That was it. Thank you. The confusion came from the .pem files not being in the C:\MDaemon\PEM\_rtcserver directory. Our certificates are not typically stored in the Windows Certificate Store as exportable. I really appreciate the help.


  • You are welcome, I'm glad you were able to get the issue resolved!


Please login to reply this topic!