{"action":"created","issue":{"url":"https://api.github.com/repos/siacs/Conversations/issues/862","labels_url":"https://api.github.com/repos/siacs/Conversations/issues/862/labels{/name}","comments_url":"https://api.github.com/repos/siacs/Conversations/issues/862/comments","events_url":"https://api.github.com/repos/siacs/Conversations/issues/862/events","html_url":"https://github.com/siacs/Conversations/issues/862","id":53976676,"number":862,"title":"Server not found WLAN issues","user":{"login":"tokudan","id":692610,"avatar_url":"https://avatars.githubusercontent.com/u/692610?v=3","gravatar_id":"","url":"https://api.github.com/users/tokudan","html_url":"https://github.com/tokudan","followers_url":"https://api.github.com/users/tokudan/followers","following_url":"https://api.github.com/users/tokudan/following{/other_user}","gists_url":"https://api.github.com/users/tokudan/gists{/gist_id}","starred_url":"https://api.github.com/users/tokudan/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tokudan/subscriptions","organizations_url":"https://api.github.com/users/tokudan/orgs","repos_url":"https://api.github.com/users/tokudan/repos","events_url":"https://api.github.com/users/tokudan/events{/privacy}","received_events_url":"https://api.github.com/users/tokudan/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":16,"created_at":"2015-01-11T00:21:23Z","updated_at":"2015-02-27T10:29:15Z","closed_at":null,"body":"Hello,\r\n\r\nthis might or might not be related to #811. I just saw Conversations being unable to connect again, while my laptop using Psi+ had no trouble connecting (and reconnecting when I forced the connection to close from the server) to my Prosody server. I saw it happen twice since upgrading to 0.10 now.\r\n\r\nI restarted Prosody to ensure that the server had no issue with any cached data. Psi+ happily reconnected after a couple of seconds.\r\nWatching the server log I did not see any connection attemps from Conversations, which just kept repeating the \"Server nicht gefunden\" (~ server not found) message\r\n\r\nBoth my laptop and the android device are connected through the same WLAN, so the routing should be exactly the same.\r\nNot sure if Psi+ uses the SRV records to determine the actual server name, but this shouldn't really matter as my domain name and the SRV record point to the same IP both in IPv4 and IPv6:\r\nexample.com IN A 1.2.3.4\r\nexample.com IN AAAA 1:2:3:4:5::6\r\nxmpp.example.com IN A 1.2.3.4\r\nxmpp.example.com IN AAAA 1:2:3:4:5::6\r\n_xmpp-client._tcp.example.com  18000 IN SRV     0 5 5222 xmpp.example.com\r\n\r\nAfter disconnecting from the WLAN, Conversations was able to connect at once. Reenabling WLAN resulted in Conversations being able to connect through the WLAN as well.\r\n\r\nI did not see any way to enabling logging somewhere or to get a better error message what exactly failed. Can you provide more detailed errors in Conversations?"},"comment":{"url":"https://api.github.com/repos/siacs/Conversations/issues/comments/76372353","html_url":"https://github.com/siacs/Conversations/issues/862#issuecomment-76372353","issue_url":"https://api.github.com/repos/siacs/Conversations/issues/862","id":76372353,"user":{"login":"iNPUTmice","id":192229,"avatar_url":"https://avatars.githubusercontent.com/u/192229?v=3","gravatar_id":"","url":"https://api.github.com/users/iNPUTmice","html_url":"https://github.com/iNPUTmice","followers_url":"https://api.github.com/users/iNPUTmice/followers","following_url":"https://api.github.com/users/iNPUTmice/following{/other_user}","gists_url":"https://api.github.com/users/iNPUTmice/gists{/gist_id}","starred_url":"https://api.github.com/users/iNPUTmice/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/iNPUTmice/subscriptions","organizations_url":"https://api.github.com/users/iNPUTmice/orgs","repos_url":"https://api.github.com/users/iNPUTmice/repos","events_url":"https://api.github.com/users/iNPUTmice/events{/privacy}","received_events_url":"https://api.github.com/users/iNPUTmice/received_events","type":"User","site_admin":false},"created_at":"2015-02-27T10:29:15Z","updated_at":"2015-02-27T10:29:15Z","body":"Oh thats not the Conversation DNS cache here that we are running into thats the DNS cache of the underlying C functions of the operating system. I quickly googled that and I have no idea on how to reset those.\r\nI mean what Conversations does is basically tell the OS please resolve xmpp.mydomain.tld for me.\r\nI also don't know why re-enabling an account would cause the the DNS library to flush. Maybe because this will create a new object?! However as a work around this is not really feasible because this will loose all state information. (like session and so forth)\r\n\r\n> Other Apps including Google Push Services are affected as well.\r\n\r\nStop buying Samsung phones?! If your phone is younger than 6 month just return it...\r\n\r\nI know I'm not really helping here and I'm sorry about that. But everything Conversations could do it this point would be some ugly, ugly workarounds. (Maybe do DNS completly by itself?)\r\nThe problem here is that I neither have a Samsung device nor an IPv6 network (ok the latter could maybe arranged somehow.)\r\nIf someone who owns a Samsung device would come up with a solution that is not too dirty I'm willing to merge it"}}