Jitsi creates a room but then redirects to an error 404

Install & Config
#1

Hi,
After creating a room the next page gets an error 404

My system is Ubuntu 16.04 / apache2 / latest version of jitsi meet

jvb
2021-04-07 06:37:28.230 INFO: [24] HealthChecker.run#170: Performed a successful health check in PT0S. Sticky failure: false
2021-04-07 06:37:38.230 INFO: [24] HealthChecker.run#170: Performed a successful health check in PT0S. Sticky failure: false
2021-04-07 06:37:48.230 INFO: [24] HealthChecker.run#170: Performed a successful health check in PT0S. Sticky failure: false
2021-04-07 06:37:58.216 INFO: [22] VideobridgeExpireThread.expire#140: Running expire()
2021-04-07 06:37:58.231 INFO: [24] HealthChecker.run#170: Performed a successful health check in PT0S. Sticky failure: false
2021-04-07 06:38:08.230 INFO: [24] HealthChecker.run#170: Performed a successful health check in PT0S. Sticky failure: false
2021-04-07 06:38:18.231 INFO: [24] HealthChecker.run#170: Performed a successful health check in PT0S. Sticky failure: false
2021-04-07 06:38:28.230 INFO: [24] HealthChecker.run#170: Performed a successful health check in PT0S. Sticky failure: false
2021-04-07 06:38:38.231 INFO: [24] HealthChecker.run#170: Performed a successful health check in PT0S. Sticky failure: false
2021-04-07 06:38:48.230 INFO: [24] HealthChecker.run#170: Performed a successful health check in PT0S. Sticky failure: false

jicofo
Jicofo 2021-04-07 06:31:58.867 INFO: [1] org.eclipse.jetty.server.AbstractConnector.doStart() Started ServerConnector@72057ecf{HTTP/1.1, (http/1.1)}{0.0.0.0:8888}
Jicofo 2021-04-07 06:31:58.868 INFO: [1] org.eclipse.jetty.server.Server.doStart() Started @1730ms
Jicofo 2021-04-07 06:31:58.871 INFO: [1] org.jitsi.jicofo.xmpp.IqHandler.log() Registering IQ handlers with XmppConnection.
Jicofo 2021-04-07 06:31:58.876 INFO: [1] org.jitsi.xmpp.component.ComponentBase.log() Component org.jitsi.jicofo. config:
Jicofo 2021-04-07 06:31:58.876 INFO: [1] org.jitsi.xmpp.component.ComponentBase.log() ping interval: 10000 ms
Jicofo 2021-04-07 06:31:58.876 INFO: [1] org.jitsi.xmpp.component.ComponentBase.log() ping timeout: 5000 ms
Jicofo 2021-04-07 06:31:58.876 INFO: [1] org.jitsi.xmpp.component.ComponentBase.log() ping threshold: 3
Jicofo 2021-04-07 06:32:03.259 INFO: [30] org.jitsi.jicofo.xmpp.BaseBrewery.log() Added brewery instance: jvbbrewery@internal.auth.MYDOMAIN/12dcab5e-70a1-4652-96c6-1805c541617f
Jicofo 2021-04-07 06:32:03.264 INFO: [30] org.jitsi.jicofo.bridge.BridgeSelector.log() Added new videobridge: Bridge[jid=jvbbrewery@internal.auth.MYDOMAIN/12dcab5e-70a1-4652-96c6-180
5c541617f, relayId=null, region=null, stress=0.00]
Jicofo 2021-04-07 06:32:03.266 INFO: [30] org.jitsi.jicofo.bridge.JvbDoctor.log() Scheduled health-check task for: jvbbrewery@internal.auth.MYDOMAIN/12dcab5e-70a1-4652-96c6-1805c5416
17f

…prosody
Apr 07 06:31:57 MYDOMAIN:muc_lobby_rooms warn Lobby rooms will not work with Prosody version 0.10 or less.
Apr 07 06:31:57 conference.MYDOMAIN:muc_domain_mapper info Loading mod_muc_domain_mapper for host conferenceduration.MYDOMAIN!
Apr 07 06:31:57 conferenceduration.MYDOMAIN:conference_duration_component warn conference duration will not work with Prosody version 0.10 or less.
Apr 07 06:31:57 conference.MYDOMAIN:muc_domain_mapper info Loading mod_muc_domain_mapper for host auth.MYDOMAIN!
Apr 07 06:31:57 c2s18c8100 info Client connected
Apr 07 06:31:58 c2s1843a20 info Client connected
Apr 07 06:31:58 c2s18c8100 info Authenticated as focus@auth.MYDOMAIN
Apr 07 06:31:58 c2s1843a20 info Authenticated as jvb@auth.MYDOMAIN
Apr 07 06:31:58 jcp17eb280 info Incoming Jabber component connection
Apr 07 06:31:58 focus.MYDOMAIN:component info External component successfully authenticated

#2

Ubuntu 16.04, I think, is really, really old. You might want to consider upgrading.
Prosody for one is unhappy about the version you’re running.

#3

Does it feel unhappy with 18.04?

just upgraded and having the same problem :frowning:

… jvb
2021-04-07 16:04:54.538 INFO: [1] org.eclipse.jetty.server.Server.doStart: jetty-9.4.35.v20201120; built: 2020-11-20T21:17:03.964Z; git: bdc54f03a5e0a7e280fab27f55c3c75ee8da89fb; jvm
1.8.0_282-8u282-b08-0ubuntu1~18.04-b08
2021-04-07 16:04:54.607 INFO: [17] [hostname=localhost id=shard] MucClient$1.connected#259: Connected.
2021-04-07 16:04:54.608 INFO: [17] [hostname=localhost id=shard] MucClient.lambda$getConnectAndLoginCallable$7#594: Logging in.
2021-04-07 16:04:54.633 INFO: [1] org.eclipse.jetty.server.handler.ContextHandler.doStart: Started o.e.j.s.ServletContextHandler@4ef782af{/,null,AVAILABLE}
2021-04-07 16:04:54.647 INFO: [1] org.eclipse.jetty.server.AbstractConnector.doStart: Started ServerConnector@7fb4f2a9{HTTP/1.1, (http/1.1)}{0.0.0.0:9090}
2021-04-07 16:04:54.647 INFO: [1] org.eclipse.jetty.server.Server.doStart: Started @1254ms
2021-04-07 16:04:54.648 INFO: [1] MainKt.main#137: Starting private http server
2021-04-07 16:04:54.661 INFO: [17] [hostname=localhost id=shard] MucClient$1.authenticated#265: Authenticated, b=false
2021-04-07 16:04:54.730 INFO: [1] org.eclipse.jetty.server.Server.doStart: jetty-9.4.35.v20201120; built: 2020-11-20T21:17:03.964Z; git: bdc54f03a5e0a7e280fab27f55c3c75ee8da89fb; jvm
1.8.0_282-8u282-b08-0ubuntu1~18.04-b08
2021-04-07 16:04:54.738 INFO: [17] [hostname=localhost id=shard] MucClient$MucWrapper.join#720: Joined MUC: jvbbrewery@internal.auth.MYDOMAIN
…jicofo
Jicofo 2021-04-07 16:04:53.876 INFO: [1] org.jitsi.jicofo.Main.log() OSGi services started.
Jicofo 2021-04-07 16:04:53.900 INFO: [1] org.jitsi.jicofo.JicofoServices.log() Authentication service disabled.
Jicofo 2021-04-07 16:04:53.905 INFO: [1] org.jitsi.jicofo.JicofoServices.log() Starting HTTP server with config: org.jitsi.rest.JettyBundleActivatorConfig@530612ba.
Jicofo 2021-04-07 16:04:53.970 INFO: [1] org.eclipse.jetty.util.log.initialized() Logging initialized @910ms to org.eclipse.jetty.util.log.Slf4jLog
Jicofo 2021-04-07 16:04:54.116 INFO: [1] org.eclipse.jetty.server.Server.doStart() jetty-9.4.35.v20201120; built: 2020-11-20T21:17:03.964Z; git: bdc54f03a5e0a7e280fab27f55c3c75ee8da8
9fb; jvm 1.8.0_282-8u282-b08-0ubuntu1~18.04-b08
Jicofo 2021-04-07 16:04:54.417 INFO: [18] org.jitsi.jicofo.ProtocolProviderHandler.log() XmppProtocolProvider(focus@auth.MYDOMAIN/focus6106942126530 (Jabber)): RegistrationStateChang
eEvent[ oldState=Unregistered; newState=RegistrationState=Registered; reasonCode=-1; reason=null]
Jicofo 2021-04-07 16:04:54.418 INFO: [18] org.jitsi.jicofo.ProtocolProviderHandler.log() Set replyTimeout=PT15S
Jicofo 2021-04-07 16:04:54.450 INFO: [18] org.jitsi.jicofo.xmpp.BaseBrewery.log() Joined brewery room: jvbbrewery@internal.auth.MYDOMAIN
Jicofo 2021-04-07 16:04:54.451 INFO: [18] org.jitsi.jicofo.FocusManager.log() XMPP provider reg state: RegistrationState=Registered
Jicofo 2021-04-07 16:04:54.458 INFO: [18] org.jitsi.impl.protocol.xmpp.XmppProtocolProvider.log() XMPP provider Jabber:focus@auth.MYDOMAIN/focus6106942126530@localhost connected (JID
: focus@auth.MYDOMAIN/focus6106942126530)
…prosody
Apr 07 16:04:53 conference.MYDOMAIN:muc_domain_mapper info Loading mod_muc_domain_mapper for host MYDOMAIN!
Apr 07 16:04:53 conferenceduration.MYDOMAIN:conference_duration_component warn conference duration will not work with Prosody version 0.10 or less.
Apr 07 16:04:53 conference.MYDOMAIN:muc_domain_mapper info Loading mod_muc_domain_mapper for host conferenceduration.MYDOMAIN!
Apr 07 16:04:53 conference.MYDOMAIN:muc_domain_mapper info Loading mod_muc_domain_mapper for host auth.MYDOMAIN!
Apr 07 16:04:53 c2s5564584a74a0 info Client connected
Apr 07 16:04:54 c2s5564584c35a0 info Client connected
Apr 07 16:04:54 c2s5564584a74a0 info Stream encrypted (TLSv1.2 with ECDHE-RSA-AES128-GCM-SHA256)
Apr 07 16:04:54 c2s5564584a74a0 info Authenticated as focus@auth.MYDOMAIN
Apr 07 16:04:54 c2s5564584c35a0 info Stream encrypted (TLSv1.2 with ECDHE-RSA-AES128-GCM-SHA256)
Apr 07 16:04:54 c2s5564584c35a0 info Authenticated as jvb@auth.MYDOMAIN

#4

Post the output of this command:

dpkg -s prosody | grep Version

#5

Version: 0.10.0-1build1

#6

and …

#7

“and …” what?
You need to upgrade your Prosody to version 0.11+

#8

It fails to install

prosody is already the newest version (0.10.0-1build1).

#9

You need an upgrade not an install.

[How to] How to upgrade Prosody for Jitsi

#10

Version: 0.11.8-1~bionic1

but the same …
should I reinstall all?

prosodyctl status
Prosody is running with PID 23527
Prosody 0.11.8

Prosody directories

Data directory: /var/lib/prosody
Config directory: /etc/prosody
Source directory: /usr/lib/prosody
Plugin directories:
/usr/lib/prosody/modules/

Lua environment

Lua version: Lua 5.2

Lua module search paths:
/usr/lib/prosody/?.lua
/usr/local/share/lua/5.2/?.lua
/usr/local/share/lua/5.2/?/init.lua
/usr/local/lib/lua/5.2/?.lua
/usr/local/lib/lua/5.2/?/init.lua
/usr/share/lua/5.2/?.lua
/usr/share/lua/5.2/?/init.lua

Lua C module search paths:
/usr/lib/prosody/?.so
/usr/local/lib/lua/5.2/?.so
/usr/lib/x86_64-linux-gnu/lua/5.2/?.so
/usr/lib/lua/5.2/?.so
/usr/local/lib/lua/5.2/loadall.so

LuaRocks: Not installed

Network

Backend: select

Lua module versions

lfs: LuaFileSystem 1.6.3
libevent: 2.1.8-stable
luaevent: 0.4.6
lxp: LuaExpat 1.3.0
socket: LuaSocket 3.0-rc1
ssl: 0.6

#11

fixed. Apache2 config for the directory:

    require all granted
    Options +Includes
    directoryindex index.html
    AddOutputFilter Includes html
        XBitHack on