XMPP on Ubuntu 18.04

Discussion in 'ISPConfig 3 Priority Support' started by DantePasquale, Jan 2, 2019.

  1. DantePasquale

    DantePasquale Member HowtoForge Supporter

    Hi, I'm having trouble getting Thunderbird XMPP Client to connect to my test server via XMPP.
    Here's the info from metronome:
    Code:
    [email protected]:/var/log/metronome# metronomectl status
    Metronome is running with PID 21713
    [email protected]:/var/log/metronome# metronomectl about
    Metronome 3.11.4
    
    # Metronome directories
    Data directory:      /var/lib/metronome
    Plugin directory:    /usr/lib/metronome/isp-modules;/usr/lib/metronome/modules/
    Config directory:    /etc/metronome
    Source directory:    /usr/lib/metronome
    
    # Lua environment
    Lua version:                Lua 5.1
    
    Lua module search paths:
      /usr/lib/metronome/?.lua
      /usr/local/share/lua/5.1/?.lua
      /usr/local/share/lua/5.1/?/init.lua
      /usr/local/lib/lua/5.1/?.lua
      /usr/local/lib/lua/5.1/?/init.lua
      /usr/share/lua/5.1/?.lua
      /usr/share/lua/5.1/?/init.lua
      /root/.luarocks/share/lua/5.1/?.lua
      /root/.luarocks/share/lua/5.1/?/init.lua
    
    Lua C module search paths:
      /usr/lib/metronome/?.so
      /usr/local/lib/lua/5.1/?.so
      /usr/lib/x86_64-linux-gnu/lua/5.1/?.so
      /usr/lib/lua/5.1/?.so
      /usr/local/lib/lua/5.1/loadall.so
      /root/.luarocks/lib/lua/5.1/?.so
    
    lua5.1: /usr/bin/metronomectl:570: attempt to index field 'cfg' (a nil value)
    stack traceback:
        /usr/bin/metronomectl:570: in function '?'
        /usr/bin/metronomectl:811: in main chunk
        [C]: ?
    
    Here's the debug log output:
    Code:
    Jan 02 12:01:40 socket    debug    try to start ssl at client id: 5632b328cbc0
    Jan 02 12:01:40 socket    debug    accepted incoming client connection from: 192.168.1.71 48354 to 5291
    Jan 02 12:01:40 socket    debug    starting handshake...
    Jan 02 12:01:40 socket    debug    ssl handshake of client with id:table: 0x5632b328cbc0, attempt:1
    Jan 02 12:01:40 socket    debug    ssl handshake of client with id:table: 0x5632b328cbc0, attempt:2
    Jan 02 12:01:40 socket    debug    ssl handshake error: wrong version number
    Jan 02 12:01:40 socket    debug    closing client with id: 5632b328cbc0 wrong version number
    Jan 02 12:01:40 socket    debug    handshake failed because: wrong version number
    Jan 02 12:01:41 socket    debug    try to start ssl at client id: 5632b328f960
    Jan 02 12:01:41 socket    debug    accepted incoming client connection from: 192.168.1.71 48356 to 5291
    Jan 02 12:01:41 socket    debug    starting handshake...
    Jan 02 12:01:41 socket    debug    ssl handshake of client with id:table: 0x5632b328f960, attempt:1
    Jan 02 12:01:41 socket    debug    ssl handshake error: wrong version number
    Jan 02 12:01:41 socket    debug    closing client with id: 5632b328f960 wrong version number
    Jan 02 12:01:41 socket    debug    handshake failed because: wrong version number
    Jan 02 12:01:46 socket    debug    try to start ssl at client id: 5632b3296c30
    Jan 02 12:01:46 socket    debug    accepted incoming client connection from: 192.168.1.71 48358 to 5291
    Jan 02 12:01:46 socket    debug    starting handshake...
    Jan 02 12:01:46 socket    debug    ssl handshake of client with id:table: 0x5632b3296c30, attempt:1
    Jan 02 12:01:46 socket    debug    ssl handshake error: wrong version number
    Jan 02 12:01:46 socket    debug    closing client with id: 5632b3296c30 wrong version number
    Jan 02 12:01:46 socket    debug    handshake failed because: wrong version number
    
    NOTE: Server field is empty -- is that a/the problem?

    Screenshot from 2019-01-02 11-52-11.png Screenshot from 2019-01-02 11-53-25.png
     
    Last edited: Jan 2, 2019
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    I guess the XMPP implementation in ISPConfig is broken at the moment, the Metronome author changed many things and made its recent versions incompatible with the version that the ispconfig Ui was developed for. XMPP has already been removed from ISPConfig 3.2, so better don't use it. There are several threads in the dev forum about the issues.
     
  3. DantePasquale

    DantePasquale Member HowtoForge Supporter

    Argh, that's what I thought :( Thanks! Hey, are there any any alternatives that you like?
     
  4. till

    till Super Moderator Staff Member ISPConfig Developer

    I'm not using XMPP at all, so I can't suggest any alternatives.
     

Share This Page