powered by Jive Software

What happened to SSL Settings?

I set up the Jive Messenger no problem. I created a self-signed cert no problem. I stop/start the Jive service no problem, but after this step, the SSL Settings in the Jive Messenger Admin Console are no longer there, even though there is a link to same. If I click on the link in the Admin Console, all I get is a blank page.

I can connect on port 5222 no problem using Psi or Gaim, but I need to connect on port 5223. Any command line settings that I can tweak?

BTW, I’‘m a relative newbie to the whole IM server thing. I’‘ve RTFM’'d and there is nothing on the above in the forum or in the docs about my issue.

Thanks…

Can you check the logs and paste in what looks relevant from the error log? You should see a logs link in the admin console.

Regards,

Matt

2005.03.11 09:11:45 [org.jivesoftware.messenger.net.SSLConfig.(SSLConfig.java:75)] SSLConfig startup problem.

storeType: []

keyStoreLocation: /opt/jive_messenger/

keypass:

trustStoreLocation: /opt/jive_messenger/

trustpass: []

java.security.KeyStoreException: not found

at java.security.KeyStore.getInstance(Unknown Source)

at org.jivesoftware.messenger.net.SSLConfig.(SSLConfig.java:65)

at org.jivesoftware.messenger.net.SSLSocketAcceptThread.(SSLSocketAcceptThre ad.java:93)

at org.jivesoftware.messenger.spi.ConnectionManagerImpl.createSocket(ConnectionMan agerImpl.java:73)

at org.jivesoftware.messenger.spi.ConnectionManagerImpl.start(ConnectionManagerImp l.java:148)

at org.jivesoftware.messenger.XMPPServer.startModules(XMPPServer.java:309)

at org.jivesoftware.messenger.XMPPServer.start(XMPPServer.java:198)

at org.jivesoftware.messenger.XMPPServer.(XMPPServer.java:116)

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

at org.jivesoftware.messenger.starter.ServerStarter.main(ServerStarter.java:46)

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.install4j.runtime.Launcher.main(Unknown Source)

2005.03.11 09:11:45 org.jivesoftware.messenger.spi.ConnectionManagerImpl.createSocket(ConnectionMana gerImpl.java:88) Could not setup SSL socket

java.io.IOException

at org.jivesoftware.messenger.net.SSLConfig.createServerSocket(SSLConfig.java:147)

at org.jivesoftware.messenger.net.SSLSocketAcceptThread.(SSLSocketAcceptThre ad.java:93)

at org.jivesoftware.messenger.spi.ConnectionManagerImpl.createSocket(ConnectionMan agerImpl.java:73)

at org.jivesoftware.messenger.spi.ConnectionManagerImpl.start(ConnectionManagerImp l.java:148)

at org.jivesoftware.messenger.XMPPServer.startModules(XMPPServer.java:309)

at org.jivesoftware.messenger.XMPPServer.start(XMPPServer.java:198)

at org.jivesoftware.messenger.XMPPServer.(XMPPServer.java:116)

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

at org.jivesoftware.messenger.starter.ServerStarter.main(ServerStarter.java:46)

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.install4j.runtime.Launcher.main(Unknown Source)

2005.03.11 09:11:51 org.jivesoftware.messenger.container.AdminConsolePlugin.initializePlugin(AdminCo nsolePlugin.java:139) Trouble initializing admin console

org.mortbay.util.MultiException[java.io.FileNotFoundException: /opt/jive_messenger (Is a directory)]

at org.mortbay.http.HttpServer.doStart(HttpServer.java:673)

at org.mortbay.util.Container.start(Container.java:72)

at org.jivesoftware.messenger.container.AdminConsolePlugin.initializePlugin(AdminC onsolePlugin.java:122)

at org.jivesoftware.messenger.container.PluginManager.loadPlugin(PluginManager.jav a:191)

at org.jivesoftware.messenger.container.PluginManager.access$300(PluginManager.jav a:69)

at org.jivesoftware.messenger.container.PluginManager$PluginMonitor.run(PluginMana ger.java:420)

at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)

at java.util.concurrent.FutureTask$Sync.innerRunAndReset(Unknown Source) at java.util.concurrent.FutureTask.runAndReset(Unknown Source)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101 (Unknown Source)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodi c(Unknown Source)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknow n Source)

at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

at java.lang.Thread.run(Unknown Source)

java.io.FileNotFoundException: /opt/jive_messenger (Is a directory)

at java.io.FileInputStream.open(Native Method)

at java.io.FileInputStream.(Unknown Source)

at org.mortbay.http.SunJsseListener.createFactory(SunJsseListener.java:227)

at org.mortbay.http.JsseListener.newServerSocket(JsseListener.java:193)

at org.mortbay.util.ThreadedServer.open(ThreadedServer.java:466)

at org.mortbay.util.ThreadedServer.start(ThreadedServer.java:495)

at org.mortbay.http.SocketListener.start(SocketListener.java:203)

at org.mortbay.http.HttpServer.doStart(HttpServer.java:703)

at org.mortbay.util.Container.start(Container.java:72)

at org.jivesoftware.messenger.container.AdminConsolePlugin.initializePlugin(AdminC onsolePlugin.java:122)

at org.jivesoftware.messenger.container.PluginManager.loadPlugin(PluginManager.jav a:191)

at org.jivesoftware.messenger.container.PluginManager.access$300(PluginManager.jav a:69)

at org.jivesoftware.messenger.container.PluginManager$PluginMonitor.run(PluginMana ger.java:420)

at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)

at java.util.concurrent.FutureTask$Sync.innerRunAndReset(Unknown Source) at java.util.concurrent.FutureTask.runAndReset(Unknown Source)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101 (Unknown Source)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodi c(Unknown Source)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknow n Source)

at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

at java.lang.Thread.run(Unknown Source)

Anyone understand what may be the case here?

Thanks…

So, the main thing that looks strange is the key store and trust store location. They are listed as /opt/jive_messenger instead of /opt/jive_messenger/resources/security. Did you manually override the keyStoreLocation and trustStoreLocation values?

Regards,

Matt

I ran into this problem twice with two different causes:

  1. I was using Opera to view the Admin Console, and that was just plain unhappy all around.

  2. I had the wrong user/group ownership of the keystore.

Check those two conditions in addition to what Matt said.

I had the a simular problem as well today.

My paths were correct so i restored the keystore and truststore files. After a restart I had my ssl connection back. Then I added a new cert since JM still searched for the old one.

After another restart I could delete the old cert and changed my passord for the keystore and in JM. I restared again and finaly had a ssl connection with my cert.