|
Unknown opened 4 years ago
|
|
|
I tried hot-chilli server (create account in the domain
@lord-aerion could you get and share Android's logcat? (https://developer.android.com/studio/command-line/logcat or use an app: https://github.com/plusCubed/matlog)? |
|
|
Hi, thanks for the quick reply. Both my
Happy to send you the logcat. I've set up adb and have also install matlog, but Iogcat produces a lot of output :-). How do I reduce it so it captures the information you're hoping to find? |
|
|
I can confirm (as admin of nerdculture.de) that authentication doesn't work. For the authentication I used https://git.chinwag.org/chinwag/ejabberd-auth-mastodon - and in some slight variation also for nerdica.net (Friendica). While logging into my hookipa.net account with Stork is working, this basically leaves the extauth script as differences between working and non-working scenario. BeagleIM and SiskinIM do not have this issue with the same extauth script for those domains. Another information about this: when adding the optional hostname to the account settings (e.g. xmpp.hookipa.net) the login for nerdculture.de is working with Stork as well. Hope this helps... |
|
|
You should be able to filter out the result by application/package - use @ingoj thank you for the hint about the script and comment in the MUC (lack of hostname prevents connection). I'd say that this is due configuration of those instances DNS:
Connecting to the first one works without any issue: Trying to connect to the second one fails: If we try to do 'direct-TLS' it fails too: It seems like on 443 normal web-traffic should be handled Do you know what was the intent? Is it supposed to handle both files and direct-TLS on the same port? Apart from that, even so - DirectTLS should not be advertised with
Yes, Stork should not try to re-connect to the same hostname if if fails, but those DNS entries should be fixed as well… |
|
|
Ah, wait... DNS... Port 443 should point to 31.172.31.206 whereas 5222 should point to 31.172.31.205. That's one thing I can fix. However, during my testing I also changed the priority of the SRV records - without a success for connection. I'll check DNS again and maybe remove the second entry, just to simplify the setup... let's wait for the DNS to propagate... |
|
|
Erm, but what is the intention of the setup? Currently it points to the same machine, but with two different ports, and it seems incorrect, unless |
|
|
Ok, bind9 had also an hickup.. After deleting the *.jnl files and restarting the nameserver I now get this: vserv:/var/www/webmail# host -t srv _xmpp-client._tcp.nerdculture.de _xmpp-client._tcp.nerdculture.de has SRV record 5 0 5222 jabber.windfluechter.net. Let's wait for the TTL to refresh... |
|
|
Hmmm... ok, so the DNS had its time to propagate the changed zone... Only thing is: Stork still can't connect and I even don't see my user in the debug log of ejabberd. Even when trying to monitor with tcpdump on the server it seems as if there is no connection established or even tried at all. Maybe @lord-aerion can see more in the Android logs... |
|
|
When I add the hostname I can indeed log in on Here are the log entries for a connection attempt without providing the hostname. There are no entries for |
|
|
Just tried generating logs for a connection attempt to |
|
|
OK, I decided to signup or an account and try it myself and managed to get some details: @ingoj - it seems that DNSSEC signature is invalid (as per @bmalkow - could you comment on that? |
|
|
@woj-tek Ok, one of my secondary nameserver had some issues with outdated RRSIG, but should be resolved now: https://dnsviz.net/d/nerdculture.de/dnssec/
|
|
|
@ingoj now I was able to connect with Stork to recently created account. @lord-aerion - does it work now for you for that domain? Regarding hot-chilli -- please check in logcat if you have any exceptions when not filtering by tigase (only search for the phrase and then check logs around it) |
|
|
@woj-tek Hmmm, I still can't connect with Stork... Wondering why...? |
|
|
@ingoj to nerdculture.de? Unfortunately at this point you'd have to provide logcat as I'm connecting to
|
|
|
Hi, sorry about my silence. I'm suffering from depression and sometimes find it hard to concentrate on something. Couldn't bring myself to look into this. Unfortunately I still can't log in on
I'll have a look now and will post the results here shortly. |
|
|
All right, here are two fresh logcats:
With both accounts the behaviour is the same as before: Regarding hot-chilli, could there be a different between |
|
|
Hmmm, Stork is not resolving the SRV record, but the A record: Doing a lookup: So, basically Stork is correct when it cannot connect to 31.172.31.213:5222, because there is no XMPP server listening. I have no idea why it doesn connect to 31.172.31.205:5222, where ejabberd is listening. So, what does go wrong as Stork is stating |
|
|
@lord-aerion no worries. Regarding the issue both chilli instances have exact DNS entries (though I'm not sure you experienced DNS issue with chilli servers).: Though, checking DNS entries for all domains: and comparing them with Stork log - it seems there is also a DNS resolution issue in this case (it tries to connect to A record for @lord-aerion & @ingoj - is there any StackTrace there with "Exception"? The log entry should contain it. It's possible that MiniDNS is throwing an issue here but without more logs/details I'm unable to say with certainty (and I can't reproduce it). I even tried to run MiniDNS directly on my machine and it return results just fine: and What is curious though is that resolution takes quite some time (more than 30s) - maybe there is some timeout? Could you try running REPL from MiniDNS explained here: https://github.com/MiniDNS/minidns#repl ? |
|
|
Hi @woj-tek, sorry for the lengthy absence. After months of nothing, suddenly had a burst of work and at the end of the day I couldn't bring myself to spend even more time behind the PC to carry on with this. My black dog wouldn't let me. Here's some "Exception" stack trace for |
|
|
Here's the same information for I'm afraid I'm not quite sure what I should do with MiniDNS, or how to run it on my system. |
|
|
Thank you @lord-aerion for those logs - could you try to gather complete stack traces from around those lines (possibly searching for They seem to be responsible for the issue, but those lines only don't give enough information. (@ingoj - or maybe you given that you experience same issue)? |
|
|
Sorry for another delay, lots of stuff came up that consumed all my time. Here's a selection of a more complete log. It's probably more than you need. I've tried to reduce it by stripping out a bunch of ALSA and other system related lines. I hope this provides you with what you need, but let me know if not and I'll produce more. This is of a connection attempt to nerdculture.de only. As it's quite a lenghty log I've attached it as a file instead of cluttering up the thread. |
|
|
Thank you for the logs, relevant entries: @lord-aerion what DNS server do you use? Have you configured them manually? Could you check if setting them to There was a similar issue reported in DNS library repository (https://github.com/MiniDNS/minidns/issues/74) but it should be fixed in this version already. @bmalkow - could you take a quick look? |
|
|
I'm using Pi-hole + Unbound running on a Raspberry Pi Zero W, but I'm also getting this issue when using my 4G connection, with or without NordVPN. I've just tried a static DNS address of 1.1.1.1 and 1.0.0.1, sadly with the same result. The log still shows the above DNS errors. |
|
|
Hmmm, captured network today, but still unable to login from my Samsung S5 mini with Android 6.0.1. Here are the pcaps attached... as you can see it is doing DNSSEC... the first pcap is from configuring the account from scratch, the second is another try after failed login attempt. So, from the miniDNS issue I conclude that my Android version is not fixed regarding that issue, so I might be a bad tester here. Which also might explain why @woj-tek could log in to nerdculture, but I couldn't. |
|
|
Hi there, was wondering if there was any progress on this issue. I want to set my sister up with an XMPP account on Hot Chilli. Her phone is very low on space so I need to set her up with Stork as it's less than half the size of Pix-Art Messenger (which is what I'm using at the moment because of the issue in this thread). |
|
|
Hi, unfortunately we weren't able to dedicate time to fix this issue yet. |
Describe the bug I'm unable to sign in on two different XMPP servers, both of which work absolutely fine in every other XMPP client I've tried, both desktop and Android.
The two servers are
nerdculture.deandhot-chilli.net.To Reproduce Steps to reproduce the behavior:
nerdculture.dea "Checking connection" dialog pops up and disappears almost immediately, follow by a "Connection error" dialog 3b. Withhot-chilli.netthe "Checking connection" dialog pops up too but stays active for around 2 minutes, displaying 0% and 0/6 all that time, until it too throws a "Connection error".Expected behavior Both accounts should log in without any issues.
Screenshots
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context A third account I've tried,
movim.euworks without an issue.