I have had Openfire 4.5.1 working for some time, even if lightly used.
Something else must have changed on the server as now the web interface on :9090 & :9091 just time out.
I can send & receive messages, so Openfire is running as a service, but it’s just not accessible from the web page
This is Ubuntu 19.10, & the web server is Apache/2.4.41 although that isn’t used could it be interfering in some way?
ufw (my firewall) says ports 7443, 9090 & 9091 are open & netstat tells me java is listening, but a search for open ports using Fing finds 9090 but not 9091 (don’t know if that is relevant). lsof tells me:
Everything seems to be in order from the data that you provide. Are there any clues in the log files? Have you tried restarting Openfire - see if something weird gets logged?
2020.04.07 10:09:21 INFO [org.jitsi.util.concurrent.RecurringRunnableExecutor.thread-org.jitsi.videobridge.health.Health]: org.jitsi.impl.libjitsi.LibJitsiImpl - Failed to initialize service implementation org.jitsi.impl.neomedia.Media>
java.lang.NoClassDefFoundError: Could not initialize class org.jitsi.impl.neomedia.device.DeviceConfiguration
at org.jitsi.impl.neomedia.MediaServiceImpl.(MediaServiceImpl.java:160) ~[libjitsi-1.0-20190128.210332-374.jar!/:?]
at sun.reflect.GeneratedConstructorAccessor35.newInstance(Unknown Source) ~[?:?]
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) ~[?:1.8.0_242]
at java.lang.reflect.Constructor.newInstance(Constructor.java:423) ~[?:1.8.0_242]
at java.lang.Class.newInstance(Class.java:442) ~[?:1.8.0_242]
at org.jitsi.impl.libjitsi.LibJitsiImpl$ServiceLock.initializeService(LibJitsiImpl.java:196) [libjitsi-1.0-20190128.210332-374.jar!/:?]
at org.jitsi.impl.libjitsi.LibJitsiImpl$ServiceLock.getService(LibJitsiImpl.java:131) [libjitsi-1.0-20190128.210332-374.jar!/:?]
at org.jitsi.impl.libjitsi.LibJitsiImpl.getService(LibJitsiImpl.java:91) [libjitsi-1.0-20190128.210332-374.jar!/:?]
at org.jitsi.impl.libjitsi.LibJitsiOSGiImpl.getService(LibJitsiOSGiImpl.java:95) [libjitsi-1.0-20190128.210332-374.jar!/:?]
at org.jitsi.service.libjitsi.LibJitsi.invokeGetServiceOnImpl(LibJitsi.java:172) [libjitsi-1.0-20190128.210332-374.jar!/:?]
at org.jitsi.service.libjitsi.LibJitsi.getMediaService(LibJitsi.java:124) [libjitsi-1.0-20190128.210332-374.jar!/:?]
at org.jitsi.videobridge.Conference.getMediaService(Conference.java:1109) [jitsi-videobridge-1.1-20190125.162313-103.jar!/:?]
at org.jitsi.videobridge.Content.getMediaService(Content.java:739) [jitsi-videobridge-1.1-20190125.162313-103.jar!/:?]
at org.jitsi.videobridge.RtpChannel.getMediaService(RtpChannel.java:780) [jitsi-videobridge-1.1-20190125.162313-103.jar!/:?]
at org.jitsi.videobridge.RtpChannel.initialize(RtpChannel.java:893) [jitsi-videobridge-1.1-20190125.162313-103.jar!/:?]
at org.jitsi.videobridge.Content.createRtpChannel(Content.java:339) [jitsi-videobridge-1.1-20190125.162313-103.jar!/:?]
at org.jitsi.videobridge.Content.createRtpChannel(Content.java:263) [jitsi-videobridge-1.1-20190125.162313-103.jar!/:?]
at org.jitsi.videobridge.health.Health.check(Health.java:152) [jitsi-videobridge-1.1-20190125.162313-103.jar!/:?]
at org.jitsi.videobridge.health.Health.doCheck(Health.java:244) [jitsi-videobridge-1.1-20190125.162313-103.jar!/:?]
at org.jitsi.videobridge.health.Health.doRun(Health.java:495) [jitsi-videobridge-1.1-20190125.162313-103.jar!/:?]
at org.jitsi.util.concurrent.PeriodicRunnableWithObject.run(PeriodicRunnableWithObject.java:87) [libjitsi-1.0-20190128.210332-374.jar!/:?]
at org.jitsi.util.concurrent.RecurringRunnableExecutor.run(RecurringRunnableExecutor.java:216) [libjitsi-1.0-20190128.210332-374.jar!/:?]
at org.jitsi.util.concurrent.RecurringRunnableExecutor.runInThread(RecurringRunnableExecutor.java:292) [libjitsi-1.0-20190128.210332-374.jar!/:?]
at org.jitsi.util.concurrent.RecurringRunnableExecutor.access$000(RecurringRunnableExecutor.java:36) [libjitsi-1.0-20190128.210332-374.jar!/:?]
at org.jitsi.util.concurrent.RecurringRunnableExecutor$1.run(RecurringRunnableExecutor.java:328) [libjitsi-1.0-20190128.210332-374.jar!/:?]
2020.04.07 10:09:21 ERROR [org.jitsi.util.concurrent.RecurringRunnableExecutor.thread-org.jitsi.videobridge.health.Health]: org.jitsi.videobridge.health.Health - Health check failed in 25ms:
java.lang.NullPointerException: null
at org.jitsi.videobridge.RtpChannel.initialize(RtpChannel.java:903) ~[jitsi-videobridge-1.1-20190125.162313-103.jar!/:?]
at org.jitsi.videobridge.Content.createRtpChannel(Content.java:339) ~[jitsi-videobridge-1.1-20190125.162313-103.jar!/:?]
at org.jitsi.videobridge.Content.createRtpChannel(Content.java:263) ~[jitsi-videobridge-1.1-20190125.162313-103.jar!/:?]
at org.jitsi.videobridge.health.Health.check(Health.java:152) ~[jitsi-videobridge-1.1-20190125.162313-103.jar!/:?]
at org.jitsi.videobridge.health.Health.doCheck(Health.java:244) ~[jitsi-videobridge-1.1-20190125.162313-103.jar!/:?]
at org.jitsi.videobridge.health.Health.doRun(Health.java:495) [jitsi-videobridge-1.1-20190125.162313-103.jar!/:?]
at org.jitsi.util.concurrent.PeriodicRunnableWithObject.run(PeriodicRunnableWithObject.java:87) [libjitsi-1.0-20190128.210332-374.jar!/:?]
at org.jitsi.util.concurrent.RecurringRunnableExecutor.run(RecurringRunnableExecutor.java:216) [libjitsi-1.0-20190128.210332-374.jar!/:?]
at org.jitsi.util.concurrent.RecurringRunnableExecutor.runInThread(RecurringRunnableExecutor.java:292) [libjitsi-1.0-20190128.210332-374.jar!/:?]
at org.jitsi.util.concurrent.RecurringRunnableExecutor.access$000(RecurringRunnableExecutor.java:36) [libjitsi-1.0-20190128.210332-374.jar!/:?]
at org.jitsi.util.concurrent.RecurringRunnableExecutor$1.run(RecurringRunnableExecutor.java:328) [libjitsi-1.0-20190128.210332-374.jar!/:?]
2020.04.07 10:09:31 INFO [org.jitsi.util.concurrent.RecurringRunnableExecutor.thread-org.jitsi.videobridge.health.Health]: org.jitsi.videobridge.Videobridge - CAT=stat create_conf,conf_id=1732fc953af7377d conf_name=null,logging=false,c>
2
I have Redfire installed & this is obviously a problem which needs fixed but will this prevent the Admin login appearing? I thought I’d have to fix this once I could log in
I assume that I can switch off the plugins by editing one of the XML files? Same for controlling the detail of the log files. I’ve only ever done any “complex” configuration via the web interface, so I don’t want to screw it up any further
Simply remove all .jar files from the ‘plugins’ directory ( you can leave the folders). Openfire will unload/reload plugins when it detects that the corresponding jar file changed (or was deleted). To reactivate the plugin, simply put the jar file back. Some plugins benefit from a restart of Openfire after you do this.
Ah, that’s a good find. OFMeet is a pretty complex plugin, so if anything is causing unexpected behavior, that one is on the top of the things to look at - even though I’ve not had this happen before. Side-note: OFMeet is distinct from Redfire. OFMeet is a wrapper for the Jitsi Meet stack. Redfire … is not (I’m not terribly familiar with that plugin).