Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

XMPP not working (anymore) #15365

Closed
Azimoth opened this issue Jul 8, 2018 · 2 comments
Closed

XMPP not working (anymore) #15365

Azimoth opened this issue Jul 8, 2018 · 2 comments

Comments

@Azimoth
Copy link

Azimoth commented Jul 8, 2018

Home Assistant release with the issue:
0.73

Last working Home Assistant release (if known):
unknown

Operating environment (Hass.io/Docker/Windows/etc.):
Debian 9.4 (Python virtual environment)

Component/platform:
https://www.home-assistant.io/components/notify.xmpp/

Description of problem:
Notifications cannot be sent anymore.

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

notify:
  - platform: xmpp
    name: recipient1
    sender: [email protected]
    password: !secret
    recipient: [email protected]

  - platform: xmpp
    name: recipient2
    sender: [email protected]
    password: !secret
    recipient: [email protected]

Traceback (if applicable):

2018-07-08 19:57:04 ERROR (read_thread) [sleekxmpp.xmlstream.resolver] All nameservers failed to answer the query _xmpp-client._tcp.my.duckdns.org. IN SRV: Server 2a02:908:2:a::1 UDP port 53 answered SERVFAIL; Server 2a02:908:2:b::1 UDP port 53 answered SERVFAIL; Server 192.168.x.x UDP port 53 answered SERVFAIL
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.5/site-packages/sleekxmpp/xmlstream/resolver.py", line 289, in get_SRV
    dns.rdatatype.SRV)
  File "/srv/homeassistant/lib/python3.5/site-packages/dns/resolver.py", line 947, in query
    raise NoNameservers(request=request, errors=errors)
dns.resolver.NoNameservers: All nameservers failed to answer the query _xmpp-client._tcp.my.duckdns.org. IN SRV: Server 2a02:908:2:a::1 UDP port 53 answered SERVFAIL; Server 2a02:908:2:b::1 UDP port 53 answered SERVFAIL; Server 192.168.x.x UDP port 53 answered SERVFAIL
2018-07-08 19:57:04 ERROR (read_thread) [sleekxmpp.xmlstream.xmlstream] CERT: Invalid certificate trust chain.
2018-07-08 19:57:04 ERROR (read_thread) [sleekxmpp.xmlstream.xmlstream] Can not read from closed socket.

Additional information:
I am using LetsEncrypt certs and ca-certificates version 20161130+nmu1 is installed on the system. The XMPP server is Prosody version 0.10.2-1~bpo9+1.
It did work in the past, but stopped at some point a few months ago.

@Azimoth
Copy link
Author

Azimoth commented Jul 8, 2018

Found the solution: sleekxmpp doesn't support anything above TLS1 (I enforced TLS 1.1).
For more details see here.

@flowolf
Copy link
Contributor

flowolf commented Oct 14, 2018

the TLSv1 issue is fixed with #17283
@fabaff please close

@home-assistant home-assistant locked and limited conversation to collaborators Feb 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants