Hi,
I try to use Grommunio meet. The installation is done from appliance setup. Mail, web, chat and meet are online. If I start a meeting, after a few seconds I get this screen:
In journalctl I see only warnings, that the presence status couldn't bet set
Jul 17 16:24:03 vm3 jvb.sh[26209]: Jul 17, 2022 4:24:03 PM org.jitsi.utils.logging2.LoggerImpl log
Jul 17 16:24:03 vm3 jvb.sh[26209]: WARNING: Failed to login. Disconnecting to trigger a re-connect.
Jul 17 16:24:03 vm3 jvb.sh[26209]: Jul 17, 2022 4:24:03 PM org.jitsi.utils.logging2.LoggerImpl log
Jul 17 16:24:03 vm3 jvb.sh[26209]: INFO: Closed.
Jul 17 16:24:08 vm3 jvb.sh[26209]: Jul 17, 2022 4:24:08 PM org.jitsi.utils.logging2.LoggerImpl log
Jul 17 16:24:08 vm3 jvb.sh[26209]: WARNING: Cannot set presence extension: not connected.
Jul 17 16:24:08 vm3 jvb.sh[26209]: Jul 17, 2022 4:24:08 PM org.jitsi.utils.logging2.LoggerImpl log
Jul 17 16:24:08 vm3 jvb.sh[26209]: INFO: Connected.
Jul 17 16:24:08 vm3 jvb.sh[26209]: Jul 17, 2022 4:24:08 PM org.jitsi.utils.logging2.LoggerImpl log
Jul 17 16:24:08 vm3 jvb.sh[26209]: INFO: Logging in.
Jul 17 16:24:08 vm3 jvb.sh[26209]: Jul 17, 2022 4:24:08 PM org.jitsi.utils.logging2.LoggerImpl log
Jul 17 16:24:08 vm3 jvb.sh[26209]: WARNING: Failed to login. Disconnecting to trigger a re-connect.
Jul 17 16:24:08 vm3 jvb.sh[26209]: Jul 17, 2022 4:24:08 PM org.jitsi.utils.logging2.LoggerImpl log
Jul 17 16:24:08 vm3 jvb.sh[26209]: INFO: Closed.
Jul 17 16:24:12 vm3 jvb.sh[26209]: Jul 17, 2022 4:24:12 PM org.jitsi.utils.logging2.LoggerImpl log
Jul 17 16:24:12 vm3 jvb.sh[26209]: INFO: Performed a successful health check in PT0.000012S. Sticky failure: false
Jul 17 16:24:13 vm3 jvb.sh[26209]: Jul 17, 2022 4:24:13 PM org.jitsi.utils.logging2.LoggerImpl log
In prosody log I see only this lines on info level
Jul 17 16:21:47 c2s55a79aad00c0 info Client connected
Jul 17 16:21:47 c2s55a79aad00c0 info Stream encrypted (TLSv1.3 with TLS_AES_256_GCM_SHA384)
Jul 17 16:21:47 c2s55a79aad00c0 info Client disconnected: connection closed
and this lines on debug level
Jul 17 16:21:32 socket debug server.lua: accepted new client connection from 127.0.0.1:56344 to 5222
Jul 17 16:21:32 c2s55bf29c3efb0 info Client connected
Jul 17 16:21:32 c2s55bf29c3efb0 debug Client sent opening <stream:stream> to auth.vm3.edvnet-uk.com
Jul 17 16:21:32 c2s55bf29c3efb0 debug Sending[c2s_unauthed]: <?xml version='1.0'?>
Jul 17 16:21:32 c2s55bf29c3efb0 debug Sending[c2s_unauthed]: <stream:stream xmlns:stream='http://etherx.jabber.org/streams' xml:lang='en' from='auth.vm3.edvnet-uk.com' id='c858d04d-5a00-4a84-a1f9-ed2df66296af' version='1.0' xmlns='jabber:client'>
Jul 17 16:21:32 c2s55bf29c3efb0 debug Sent reply <stream:stream> to client
Jul 17 16:21:32 c2s55bf29c3efb0 debug Not offering authentication on insecure connection
Jul 17 16:21:32 c2s55bf29c3efb0 debug Sending[c2s_unauthed]: <stream:features>
Jul 17 16:21:32 runneraUUZthA5 debug creating new coroutine
Jul 17 16:21:32 c2s55bf29c3efb0 debug Received[c2s_unauthed]: <starttls xmlns='urn:ietf:params:xml:ns:xmpp-tls'>
Jul 17 16:21:32 c2s55bf29c3efb0 debug Sending[c2s_unauthed]: <proceed xmlns='urn:ietf:params:xml:ns:xmpp-tls'>
Jul 17 16:21:32 socket debug server.lua: we need to do tls, but delaying until send buffer empty
Jul 17 16:21:32 c2s55bf29c3efb0 debug TLS negotiation started for c2s_unauthed...
Jul 17 16:21:32 socket debug server.lua: attempting to start tls on tcp{client}: 0x55bf29d1b198
Jul 17 16:21:32 socket debug server.lua: ssl handshake done
Jul 17 16:21:32 c2s55bf29c3efb0 debug Client sent opening <stream:stream> to auth.vm3.edvnet-uk.com
Jul 17 16:21:32 c2s55bf29c3efb0 debug Sending[c2s_unauthed]: <?xml version='1.0'?>
Jul 17 16:21:32 c2s55bf29c3efb0 debug Sending[c2s_unauthed]: <stream:stream xmlns:stream='http://etherx.jabber.org/streams' xml:lang='en' from='auth.vm3.edvnet-uk.com' id='48878fcf-ed8a-49d0-a320-d663f3a9eab2' version='1.0' xmlns='jabber:client'>
Jul 17 16:21:32 c2s55bf29c3efb0 debug Sent reply <stream:stream> to client
Jul 17 16:21:32 c2s55bf29c3efb0 info Stream encrypted (TLSv1.3 with TLS_AES_256_GCM_SHA384)
Jul 17 16:21:32 c2s55bf29c3efb0 debug Channel binding 'tls-unique' undefined in context of TLS 1.3
Jul 17 16:21:32 c2s55bf29c3efb0 debug Offering mechanism PLAIN
Jul 17 16:21:32 c2s55bf29c3efb0 debug Not offering disabled mechanism DIGEST-MD5
Jul 17 16:21:32 c2s55bf29c3efb0 debug Offering mechanism SCRAM-SHA-1
Jul 17 16:21:32 c2s55bf29c3efb0 debug Sending[c2s_unauthed]: <stream:features>
Jul 17 16:21:32 c2s55bf29c3efb0 debug Received[c2s_unauthed]: <auth mechanism='SCRAM-SHA-1' xmlns='urn:ietf:params:xml:ns:xmpp-sasl'>
Jul 17 16:21:32 auth.vm3.edvnet-uk.com:auth_internal_plain debug get_password for username 'focus'
Jul 17 16:21:32 auth.vm3.edvnet-uk.com:saslauth debug sasl reply: <challenge xmlns='urn:ietf:params:xml:ns:xmpp-sasl'>cj0jNGpmSCZcMEtJTnAwKVdRa3ohRVlNZE1hOjslcTliJjIzNzdiZGQ4LWNkMzAtNDdhYS04MDg1LWNjZTRmOTNhNmFkMCxzPU9XRmlOalExTUdNdE16WXpOeTAwTmpjNUxXSTBPV010TmpWbE5XRXlZall6
WlRsaCxpPTQwOTY=</challenge>
Jul 17 16:21:32 c2s55bf29c3efb0 debug Sending[c2s_unauthed]: <challenge xmlns='urn:ietf:params:xml:ns:xmpp-sasl'>
Jul 17 16:21:32 c2s55bf29c3efb0 debug Received[c2s_unauthed]: <response xmlns='urn:ietf:params:xml:ns:xmpp-sasl'>
Jul 17 16:21:32 auth.vm3.edvnet-uk.com:saslauth debug sasl reply: <failure xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><not-authorized/><text>The response provided by the client doesn't match the one we calculated.</text></failure>
Jul 17 16:21:32 c2s55bf29c3efb0 debug Sending[c2s_unauthed]: <failure xmlns='urn:ietf:params:xml:ns:xmpp-sasl'>
Jul 17 16:21:32 c2s55bf29c3efb0 debug Received </stream:stream>
Jul 17 16:21:32 c2s55bf29c3efb0 debug Sending[c2s_unauthed]: </stream:stream>
Jul 17 16:21:32 c2s55bf29c3efb0 debug c2s stream for 127.0.0.1 closed: session closed
Jul 17 16:21:32 c2s55bf29c3efb0 debug Destroying session for (unknown) ((unknown)@auth.vm3.edvnet-uk.com)
Jul 17 16:21:32 c2s55bf29c3efb0 info Client disconnected: connection closed
Jul 17 16:21:32 c2s55bf29c3efb0 debug Destroying session for (unknown) ((unknown)@(unknown))
Jul 17 16:21:32 socket debug server.lua: closed client handler and removed socket from list
Jul 17 16:21:32 socket debug server.lua: accepted new client connection from 127.0.0.1:56346 to 5222
Jul 17 16:21:32 c2s55bf29cbd1f0 info Client connected
Jul 17 16:21:32 c2s55bf29cbd1f0 debug Client sent opening <stream:stream> to auth.vm3.edvnet-uk.com
Jul 17 16:21:32 c2s55bf29cbd1f0 debug Sending[c2s_unauthed]: <?xml version='1.0'?>
Jul 17 16:21:32 c2s55bf29cbd1f0 debug Sending[c2s_unauthed]: <stream:stream xmlns:stream='http://etherx.jabber.org/streams' xml:lang='en' from='auth.vm3.edvnet-uk.com' id='092b771f-00e7-4d57-a2fe-e3a859243eee' version='1.0' xmlns='jabber:client'>
Jul 17 16:21:32 c2s55bf29cbd1f0 debug Sent reply <stream:stream> to client
Jul 17 16:21:32 c2s55bf29cbd1f0 debug Not offering authentication on insecure connection
Jul 17 16:21:32 c2s55bf29cbd1f0 debug Sending[c2s_unauthed]: <stream:features>
Jul 17 16:21:32 runnercg7_U6iM debug creating new coroutine
Jul 17 16:21:32 c2s55bf29cbd1f0 debug Received[c2s_unauthed]: <starttls xmlns='urn:ietf:params:xml:ns:xmpp-tls'>
Jul 17 16:21:32 c2s55bf29cbd1f0 debug Sending[c2s_unauthed]: <proceed xmlns='urn:ietf:params:xml:ns:xmpp-tls'>
Jul 17 16:21:32 socket debug server.lua: we need to do tls, but delaying until send buffer empty
Jul 17 16:21:32 c2s55bf29cbd1f0 debug TLS negotiation started for c2s_unauthed...
Jul 17 16:21:32 socket debug server.lua: attempting to start tls on tcp{client}: 0x55bf29b725b8
Jul 17 16:21:32 socket debug server.lua: ssl handshake done
Jul 17 16:21:32 c2s55bf29cbd1f0 debug Client sent opening <stream:stream> to auth.vm3.edvnet-uk.com
Jul 17 16:21:32 c2s55bf29cbd1f0 debug Sending[c2s_unauthed]: <?xml version='1.0'?>
Jul 17 16:21:32 c2s55bf29cbd1f0 debug Sending[c2s_unauthed]: <stream:stream xmlns:stream='http://etherx.jabber.org/streams' xml:lang='en' from='auth.vm3.edvnet-uk.com' id='e31cfe15-809f-4987-9600-dea95567f7ce' version='1.0' xmlns='jabber:client'>
Jul 17 16:21:32 c2s55bf29cbd1f0 debug Sent reply <stream:stream> to client
Jul 17 16:21:32 c2s55bf29cbd1f0 info Stream encrypted (TLSv1.3 with TLS_AES_256_GCM_SHA384)
Jul 17 16:21:32 c2s55bf29cbd1f0 debug Channel binding 'tls-unique' undefined in context of TLS 1.3
Jul 17 16:21:32 c2s55bf29cbd1f0 debug Offering mechanism PLAIN
Jul 17 16:21:32 c2s55bf29cbd1f0 debug Not offering disabled mechanism DIGEST-MD5
Jul 17 16:21:32 c2s55bf29cbd1f0 debug Offering mechanism SCRAM-SHA-1
Jul 17 16:21:32 c2s55bf29cbd1f0 debug Sending[c2s_unauthed]: <stream:features>
Jul 17 16:21:32 c2s55bf29cbd1f0 debug Received[c2s_unauthed]: <auth mechanism='SCRAM-SHA-1' xmlns='urn:ietf:params:xml:ns:xmpp-sasl'>
Jul 17 16:21:32 auth.vm3.edvnet-uk.com:auth_internal_plain debug get_password for username 'focus'
Jul 17 16:21:32 auth.vm3.edvnet-uk.com:saslauth debug sasl reply: <challenge xmlns='urn:ietf:params:xml:ns:xmpp-sasl'>cj0nMStSM05haWRLLmolYHNQXzVQaWJaSSVOWy0+SDVxY2FmZTBjNmNlLWFhMWItNDQzYi1iNTY2LWQ2ODQ4N2Q2OWVmZCxzPU56QTRNVFZsTURFdE1EVTROUzAwTldNekxUazJZemd0TXpJNU1tVTVZMlZrWXpjeSxpPTQwOTY=</challenge>
Jul 17 16:21:32 c2s55bf29cbd1f0 debug Sending[c2s_unauthed]: <challenge xmlns='urn:ietf:params:xml:ns:xmpp-sasl'>
Jul 17 16:21:32 c2s55bf29cbd1f0 debug Received[c2s_unauthed]: <response xmlns='urn:ietf:params:xml:ns:xmpp-sasl'>
Jul 17 16:21:32 auth.vm3.edvnet-uk.com:saslauth debug sasl reply: <failure xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><not-authorized/><text>The response provided by the client doesn't match the one we calculated.</text></failure>
Jul 17 16:21:32 c2s55bf29cbd1f0 debug Sending[c2s_unauthed]: <failure xmlns='urn:ietf:params:xml:ns:xmpp-sasl'>
Jul 17 16:21:32 c2s55bf29cbd1f0 debug Received </stream:stream>
Jul 17 16:21:32 c2s55bf29cbd1f0 debug Sending[c2s_unauthed]: </stream:stream>
Jul 17 16:21:32 c2s55bf29cbd1f0 debug c2s stream for 127.0.0.1 closed: session closed
Jul 17 16:21:32 c2s55bf29cbd1f0 debug Destroying session for (unknown) ((unknown)@auth.vm3.edvnet-uk.com)
Jul 17 16:21:32 c2s55bf29cbd1f0 info Client disconnected: connection closed
Jul 17 16:21:32 c2s55bf29cbd1f0 debug Destroying session for (unknown) ((unknown)@(unknown))
Jul 17 16:21:32 socket debug server.lua: closed client handler and removed socket from list
Jul 17 16:21:37 socket debug server.lua: accepted new client connection from 127.0.0.1:56348 to 5222
Installation details
S | Name | Type | Version | Arch | Repository
---+------------------------------------+---------+--------------------------------------+--------+------------------
i | grommunio | pattern | 1-lp153.8.1 | x86_64 | grommunio
i+ | grommunio-admin-api | package | 1.7.47.1e03415-lp153.129.1 | noarch | grommunio
i+ | grommunio-admin-common | package | 6.cb985db-lp153.10.1 | noarch | grommunio
i+ | grommunio-admin-web | package | 2.4.0.3.5277083-lp153.77.1 | noarch | grommunio
i+ | grommunio-antispam | package | 3.2-lp153.3.1 | x86_64 | grommunio
i+ | grommunio-archive | package | 1.3.12.g137.d1b0df1b-lp153.45.6 | x86_64 | grommunio
i+ | grommunio-chat | package | 6.2.1-lp153.15.1 | x86_64 | grommunio
i+ | grommunio-common | package | 6.2dbc6d3-lp153.13.1 | x86_64 | grommunio
i+ | grommunio-cui | package | 1.0.33.a04e052-lp153.16.1 | noarch | grommunio
i+ | grommunio-dav | package | 1.0.10.1ac602d-lp153.1.1 | noarch | grommunio
i | grommunio-error-pages | package | 1.0.6.9c50afb-lp153.7.1 | noarch | grommunio
i+ | grommunio-files | package | 10.9.1-lp153.13.1 | noarch | grommunio
i+ | grommunio-imapsync | package | 2.200-lp153.4.1 | noarch | grommunio
i+ | grommunio-index | package | 0.1.11.8787c3c-lp153.16.1 | x86_64 | grommunio
i+ | grommunio-office | package | 7.0.0-lp153.17.3 | x86_64 | grommunio
i | grommunio-office-fonts | package | 7.0.0-lp153.17.3 | noarch | grommunio
i+ | grommunio-release | package | 2022.05.1-lp153.1.1 | x86_64 | grommunio
i+ | grommunio-setup | package | 1.0.62.d4c0c8b-lp153.40.1 | noarch | grommunio
i+ | grommunio-sync | package | 1.0.27-lp153.137.1 | noarch | grommunio
i+ | grommunio-web | package | 3.0.43.48d49b2d-lp153.110.1 | noarch | grommunio
i+ | gromox | package | 1.27.0.6903e2287-lp153.2.1 | x86_64 | grommunio
i+ | gromox-debuginfo | package | 1.27.0.6903e2287-lp153.2.1 | x86_64 | grommunio
i+ | gromox-debugsource | package | 1.27.0.6903e2287-lp153.2.1 | x86_64 | grommunio
i+ | grub2-theme-grommunio | package | 1-lp153.11.4 | noarch | grommunio
i+ | jitsi-jibri | package | 8.0.115.gddb146c-lp153.2.1 | noarch | grommunio
i+ | jitsi-jicofo | package | 2.0.7001+1.0.862.gaace8cf-lp153.1.1 | noarch | grommunio
i+ | jitsi-jigasi | package | 1.1.216.ga2399b9-lp153.1.1 | x86_64 | grommunio
i+ | jitsi-meet | package | 2.0.6726-lp153.16.2 | noarch | grommunio
i+ | jitsi-meet-branding-grommunio | package | 2.0.6726-lp153.3.1 | noarch | grommunio
i+ | jitsi-meet-prosody-plugins | package | 2.0.6726-lp153.16.2 | noarch | grommunio
i+ | jitsi-videobridge | package | 2.0.6726+2.1.682.g0192d75e-lp153.5.1 | noarch | grommunio
i+ | NAME="grommunio" | product | "2022.05.1" | noarch | (System Packages)
i+ | patterns-grommunio | package | 1-lp153.8.1 | x86_64 | grommunio
i+ | plymouth-theme-grommunio | package | 1-lp153.11.4 | noarch | grommunio
i | system-user-grommunio | package | 2-lp153.9.4 | noarch | grommunio
i | system-user-gromox | package | 2-lp153.11.1 | noarch | grommunio
i | systemd-presets-branding-grommunio | package | 2021.02-lp153.3.1 | noarch | grommunio
I've tested the connection from Windows 10 Firefox ESR and Chrome over DSL and Android Chrome over LTE. The grommunio server is a vm directly connected to the internet via static IPv4/v6.
How can I find more infos to successfully run a meeting?
Thanks
Ulf