Hello! So, I work in a company that uses Spark as chat software between employees. I tried to update my Spark to that latest version (3.0.2), while I used the 2.7.0 version. When I try to connect in the old version, it goes well, but when I try it in the new version, this error appears:
Here is the error in text format. The image above shows both versions running at the same time, but I opened the old one after the error appeared.
org.jivesoftware.smack.SmackException$EndpointConnectionException: The following addresses failed: 'RFC 6120 A/AAAA Endpoint + [remoto:5222] (0.0.0.0/0.0.0.0:5222)' failed because: java.net.SocketTimeoutException: Connect timed out, 'RFC 6120 A/AAAA Endpoint + [remoto:5222] (0.0.0.0/0.0.0.0:5222)' failed because: java.net.SocketTimeoutException: Connect timed out
at org.jivesoftware.smack.SmackException$EndpointConnectionException.from(SmackException.java:334)
at org.jivesoftware.smack.tcp.XMPPTCPConnection.connectUsingConfiguration(XMPPTCPConnection.java:664)
at org.jivesoftware.smack.tcp.XMPPTCPConnection.connectInternal(XMPPTCPConnection.java:849)
at org.jivesoftware.smack.AbstractXMPPConnection.connect(AbstractXMPPConnection.java:526)
at org.jivesoftware.gui.LoginUIPanel.login(LoginUIPanel.java:1253)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:572)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
at java.base/java.lang.Thread.run(Thread.java:1583)
The new client appears to resolve the IP address for the service called ‘remoto’ to 0.0.0.0. That is not right. It should be a non-zero IP address.
Perhaps you need to modify DNS settings (or the ‘hosts’ file on your operating system), or you need to configure the correct IP address as the ‘connect host’ in the ‘advanced’ settings of Spark.
So, I tried editing my hosts file and inserting the remoto IPv4 and the name inside of it, but with no success. One thing I noticed is that the 2.7.0 version shares the same configuration as the 3.0.2 version. I also took a look at every configuration in the login screen, and they are the same; unfortunately, 2.7.0 connects normally, while 3.0.2 doesn’t.
Sorry for the large image. Here’s the configuration on both versions. Could it be a problem with Openfire Server on the server computer? Because I don’t have access to Openfire, as its in the IT department.
Curious. It’s not immediately obvious to me what could be causing this.
Maybe it is worth trying an older version (something between 2.7.0 and 3.0.2) to see if that work? Maybe a bug got introduced in some version, that affects only you.
I notice that you use a proxy. That’s not something that I test for. Maybe that is somehow related.
So I’ve tested almost every version between 3.0.2 and 2.7.0, and only 2.7.0 is working; none of the other versions can authenticate. I don’t know what is causing this. I even removed 2.7.0 from my computer to see if it could be some type of compatibility problem or smt like that.
It was a problem with the proxy; I did not pay attention to the fact that I’m on a local network, lol. So, as soon as I deactivated it and tried to connect, it worked normally—only some messages about certificates, but at least its working now! Thx guus!
