Moved to new Network with new IP address, now wild fire will not run

We moved to a new building and we could not reuse the same IP address scheme from the old building due to some routing issues. Now I get a database error, but MYSQL is running just fine. Here is the message while trying to start wildfire server. I checked the error logs that I could find, but I found no answer. How can I fix this without having to add all my users again?

Database setup or configuration error: Please verify your database settings and check the logs/error.log file for detailed error messages.

java.lang.IllegalArgumentException: java.lang.NullPointerException

at org.jivesoftware.wildfire.XMPPServer.verifyDataSource(XMPPServer.java:675)

at org.jivesoftware.wildfire.XMPPServer.start(XMPPServer.java:393)

at org.jivesoftware.wildfire.XMPPServer.<init>(XMPPServer.java:148)

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.wildfire.starter.ServerStarter.start(ServerStarter.java:93)

at org.jivesoftware.wildfire.starter.ServerStarter.main(ServerStarter.java:49)

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)

Caused by: java.lang.NullPointerException

at org.jivesoftware.wildfire.XMPPServer.verifyDataSource(XMPPServer.java:664)

… 16 more

Error starting the server. Please check the log files for more information.

Server halted

Hi faywill, welcome to Ignite Realtime community B-).

There are a couple of possible causes I could think of. First, if you’re running mysql in a separate server and it’s also moved to a different ip or hostname, you might need to change conf/openfire.xml accordingly. Also, make sure that there’s no firewall blocking access to mysql port (default:3306). Second it’s probably a mysql permission problem. You might need to change the permission for openfire user in mysql.user table and set it to the new IP address. Remember that you need to reload mysql permission after the change.