haii
I an trying to connect to openfire server from a remote system that is not with in my LAN.I got an error that server not found.
I tried both by using IP address and server host name but the same error.
Is it possible to connect to server from remote server?
And i found errors in log record as:

at java.sql.DriverManager.getConnection(Unknown Source)

at java.sql.DriverManager.getConnection(Unknown Source)
at org.logicalcobwebs.proxool.DefaultConnectionBuilder.buildConnection(DefaultConnectionBuilder.java:39)
at org.logicalcobwebs.proxool.Prototyper.buildConnection(Prototyper.java:159)
at org.logicalcobwebs.proxool.ConnectionPool.getConnection(ConnectionPool.java:211)
at org.logicalcobwebs.proxool.ProxoolDriver.connect(ProxoolDriver.java:89)
at java.sql.DriverManager.getConnection(Unknown Source)
at java.sql.DriverManager.getConnection(Unknown Source)
at org.jivesoftware.database.EmbeddedConnectionProvider.getConnection(EmbeddedConnectionProvider.java:61)
at org.jivesoftware.database.DbConnectionManager.setConnectionProvider(DbConnectionManager.java:620)
at org.jivesoftware.database.DbConnectionManager.getConnection(DbConnectionManager.java:100)
at org.jivesoftware.util.JiveProperties.loadProperties(JiveProperties.java:344)
at org.jivesoftware.util.JiveProperties.init(JiveProperties.java:90)
at org.jivesoftware.util.JiveProperties$JivePropertyHolder.<clinit>(JiveProperties.java:57)
at org.jivesoftware.util.JiveProperties.getInstance(JiveProperties.java:69)
at org.jivesoftware.util.JiveGlobals.getProperty(JiveGlobals.java:551)
at org.jivesoftware.openfire.XMPPServer.initialize(XMPPServer.java:349)
at org.jivesoftware.openfire.XMPPServer.start(XMPPServer.java:468)
at org.jivesoftware.openfire.XMPPServer.<init>(XMPPServer.java:212)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at java.lang.Class.newInstance0(Unknown Source)
at java.lang.Class.newInstance(Unknown Source)
at org.jivesoftware.openfire.starter.ServerStarter.start(ServerStarter.java:113)
at org.jivesoftware.openfire.starter.ServerStarter.main(ServerStarter.java:58)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.exe4j.runtime.LauncherEngine.launch(Unknown Source)
at com.exe4j.runtime.WinLauncher.main(Unknown Source)
2012.05.04 12:48:01 org.jivesoftware.openfire.update.UpdateManager - Error checking for updates
java.net.UnknownHostException: www.igniterealtime.org
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.<init>(Unknown Source)
at java.net.Socket.<init>(Unknown Source)
at org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.createSocket(DefaultProtocolSocketFactory.java:80)
at org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.createSocket(DefaultProtocolSocketFactory.java:122)
at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:707)
at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:387)
at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:323)
at org.jivesoftware.openfire.update.UpdateManager.checkForServerUpdate(UpdateManager.java:226)
at org.jivesoftware.openfire.update.UpdateManager$1.run(UpdateManager.java:142)

so,please any one try to solve my problem as early as possible.
thaq in advance.

Dani AI

Generated

Brief summary and focused checklist (building on ): the symptoms point to two separate failure classes that commonly stop remote clients from connecting — (A) Openfire not finishing startup because of a database/driver problem, and (B) basic network/DNS/firewall issues that prevent remote hosts from reaching the server or the server from resolving external names. The network checks suggested by are necessary but not sufficient; the Openfire JVM must be running and listening on the right interfaces and ports before clients can connect.

Quick, ordered checks to run on the Openfire host and from a remote machine:

  • Confirm Openfire process is running and which interfaces/ports the JVM has bound to:
# Linux (run as root)
ss -tulpn | grep java

# Windows (admin command prompt)
netstat -ano | findstr :5222
  • From a remote machine, test reachability and DNS (do not rely on ping alone). Example tools: nc, nmap, nslookup/dig.
# remote host
nc -vz <server-ip-or-hostname> 5222 9090
nmap -Pn -p 5222,5223,5269,9090,9091 <server-ip-or-hostname>
nslookup www.igniterealtime.org

Database and startup-specific checks (likely blocking Openfire from accepting clients):

  • If startup logs show JDBC/DriverManager-style errors, verify whether Openfire is configured for an external DB. If so, confirm the correct JDBC driver jar is present in Openfire’s lib directory and that the DB connection URL, user and password in Openfire’s configuration are correct.
  • From the Openfire host, try a direct DB client connection (mysql/psql) to validate credentials and network access to the database server.

Other important notes and cautions:

  • If the server is behind NAT, remote clients must use the public IP/DNS and the router must forward XMPP ports. If DNS SRV records are used for the XMPP domain, ensure they resolve to the correct host.
  • Failure to resolve external hosts (update checks) usually points to DNS or outbound firewall restrictions; that won’t let Openfire complete some startup operations.
  • When opening ports to the Internet, secure the admin console (HTTPS, strong password) and only open required ports.

These steps separate network reachability problems from service startup/database issues; both must be resolved before remote clients can connect.

Aside from the application issue, start by validating network connectivity. Also, think about what is in between these two systems that may be filtering traffic, such as a firewall.

-Try a simple PING test. Can you ping the server by IP address?
-Try to conenct to the port that application is listening on. for example, if you are connecting to a web server, you can use a telnet client to connect on 80. If you get a blinking cursor, that mean you connected. For example:

telnet ip_address_of_server 80

-If there is a firewall in between, ask the firewall adminsitrator to look at the traffic logs and see if the traffic is passing or being blocked. If its passing, then the issue is most likely on the server, if its blocked, then you need to open the correct port(s).

commented: Good post. +0
Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.