Without more detailed messages, it is hard to identify what’s going wrong. Assuming that your client supports the protocol, a common cause for failure is using a TLS certificate that does not properly cover the hostname of the server that is running Openfire. This is a guess, though. You should try to find more diagnostic information in the client’s log files, and in Openfire’s logs.
Your instance of Openfire is configured to use the value of localhost as the XMPP domain name. This will cause problems, as it cannot be routed over the internet.
If you use localhost as your domain name, then your TLS certificates will be, at best, self-signed (meaning that they are unlikely to be recognized/accepted by third party software).
You should have a proper XMPP domain name value. It is easiest to give it the same name as what is used to reach the server that is running Openfire over the network (eg: example.org). If you cannot use the fully qualified domain name of the computer that is running Openfire as an XMPP domain name, then you will need to setup DNS SRV records to map between the domain name and its hosts.
I have the thing now on 3 servers, one is open, all ports etc, no firewall, it doesn’t work there either. It is a software error of the manufacturer. If you google, the error ICE ERROR goes back to the year 2014, and was never fixed.
If no one has a solution, we have to work with WhatsAPP again :-(. I hate WhatsAPP #help#openfire#jitsi#bug#ice#error#iceerror#administrator#developer#plugin#call