New hostname solution missed at least one instance in XMPP

I followed the instructions to rename my host but i am getting:
org.jivesoftware.smack.XMPPException$StreamErrorException: host-unknown
You can read more about the meaning of this stream error at

stream:errorThis server does not
serve auth.meet.themysteriesoftherosary.net</stream:error>

where meet.themysteriesoftherosary.net is the old name the new one is
meet.mysteriesoftherosary.net

Where do I need to change it to avild this issue?

What instructions did you follow? Sounds like you’ve started changing the XMPP domain name and missed something.

Perhaps too late now, but technically you don’t need to change the XMPP domain just to host it on a different web domain. They are named the same in default installs for simplicity, but they can be different. And changing just the web domain is much simpler. See Change domain name to an already existing self hosting Jitsi Meet server - #7 by shawn

Yes too late now but I used a videobridge command that brought up a form and asked me to enter the new hostname which I did and it seemed to work. I had to also get new SSL certificates and by the time I got that done and started to test I found that although I could bring up the jitsi home page and get into a room but when I opened a second connection from a different network I was given a different room with the same name as the other which hadn’t been closed. Thus two rooms and no ability to communicate. I checked in the jitsi log and found the error I posted.

I found a directory in sites-enabled that pointed to the old domain so I deleted it then I rebooted. When the system came up I got right into jitsi and then went to a second machine and got right in but each with its on instance not getting into the same room. In addition when I went to look at the log it is now protected and I can’t get in.

I went through all the files I could find and changed or removed references but there is still one more but the logs have changed. I have attached the two logs. There are errors in both but only the JVB log has a reference to “themysteriesoftherosary.net” which s/b changed to “mysteriesoftherosary.net” or removed.

I am still not able to connect users to the same room.

Jicofo_LogExtract.txt (5.33 KB)

JVB_LogExtract.txt (10.8 KB)

I don’t know what it means but the prodody.err file contains:
May 30 14:02:46 portmanager error Error binding encrypted port for https: No certificate present in SSL/TLS configuration for https port 5281

for every attempted access

That error should not cause any problems. If you want to remove that noise, uncomment this line:

I’m no expert when it comes to debugging JVB/Jicofo logs, but it looks like JVB is trying to use your old domain when connecting to Prosody. Probably a missed config change in /etc/jitsi/videobridge/config.js or sip-communicator.properties.

Try grepping for the old domain and see if anything comes up?

grep -R themysteries /etc/jitsi

The “connection error” you see in there was Jicofo failing to connect to prosody (probably because you started them both at the same time and Jicofo came up first?) and subsequent connection succeeded. I can’t spot any issues there.

Thank you very much. I am making progress. I got rid of the references to the old domain. But I still can’t connect people together on jitsi
the jocofo.log shows an error when I attempt to connect to a room:

Jicofo 2022-05-31 10:53:14.346 INFO: [1] Main.main#49: Starting Jicofo.
Jicofo 2022-05-31 10:53:14.543 INFO: [1] JitsiConfig.#47:
Initialized newConfig: merge of /etc/jitsi/jicofo/jicofo.conf: 1,system
properties,reference.conf @
jar:file:/usr/share/jicofo/jicofo.jar!/reference.conf: 1
Jicofo 2022-05-31 10:53:14.545 INFO: [1]
ReadOnlyConfigurationService.reloadConfiguration#51: loading config file
at path /etc/jitsi/jicofo/sip-communicator.properties
Jicofo 2022-05-31 10:53:14.547 INFO: [1] JitsiConfig.#68:
Initialized legacyConfig: sip communicator props (no description provided)
Jicofo 2022-05-31 10:53:14.548 INFO: [1]
JitsiConfig$Companion.reloadNewConfig#94: Reloading the Typesafe config
source (previously reloaded 0 times).
Jicofo 2022-05-31 10:53:15.218 INFO: [1]
JicofoServices.createAuthenticationAuthority#196: Authentication service
disabled.
Jicofo 2022-05-31 10:53:15.497 INFO: [1] XmppServices.#48: No
dedicated Service XMPP connection configured, re-using the client XMPP
connection.
Jicofo 2022-05-31 10:53:15.502 INFO: [1] XmppServices.#63: No
Jigasi detector configured.
Jicofo 2022-05-31 10:53:15.521 SEVERE: [17] [xmpp_connection=client]
XmppProviderImpl.doConnect#228: Failed to connect/login: The following
addresses failed: ‘RFC 6120 A/AAAA Endpoint + [localhost:5222]
(localhost/127.0.0.1:5222)’ failed because: java.net.ConnectException:
Connection refused (Connection refused)
org.jivesoftware.smack.SmackException$EndpointConnectionException: The
following addresses failed: ‘RFC 6120 A/AAAA Endpoint + [localhost:5222]
(localhost/127.0.0.1:5222)’ failed because: java.net.ConnectException:
Connection refused (Connection refused)
at
org.jivesoftware.smack.SmackException$EndpointConnectionException.from(SmackException.java:334)
at
org.jivesoftware.smack.tcp.XMPPTCPConnection.connectUsingConfiguration(XMPPTCPConnection.java:663)
at
org.jivesoftware.smack.tcp.XMPPTCPConnection.connectInternal(XMPPTCPConnection.java:846)
at
org.jivesoftware.smack.AbstractXMPPConnection.connect(AbstractXMPPConnection.java:529)
at
org.jitsi.impl.protocol.xmpp.XmppProviderImpl.doConnect(XmppProviderImpl.java:208)
at org.jitsi.retry.RetryStrategy$TaskRunner.run(RetryStrategy.java:167)
at
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at
java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)
Jicofo 2022-05-31 10:53:15.530 INFO: [1] BridgeSelector.#57: Using
org.jitsi.jicofo.bridge.SingleBridgeSelectionStrategy
Jicofo 2022-05-31 10:53:15.540 INFO: [1] [type=bridge
brewery=jvbbrewery] BaseBrewery.#100: Initialized with
JID=jvbbrewery@internal.auth.meet.mysteriesoftherosary.net
Jicofo 2022-05-31 10:53:15.543 INFO: [1] JicofoServices.#121: No
Jibri detector configured.
Jicofo 2022-05-31 10:53:15.544 INFO: [1] JicofoServices.#127: No
SIP Jibri detector configured.
Jicofo 2022-05-31 10:53:15.552 INFO: [1] JicofoServices.#142:
Starting HTTP server with config: host=null, port=8888, tlsPort=8843,
isTls=false, keyStorePath=null, sendServerVersion=true.
Jicofo 2022-05-31 10:53:15.643 INFO: [1]
org.eclipse.jetty.util.log.Log.initialized: Logging initialized @1840ms
to org.eclipse.jetty.util.log.Slf4jLog
Jicofo 2022-05-31 10:53:15.735 INFO: [1]
org.eclipse.jetty.server.Server.doStart: jetty-9.4.44.v20210927; built:
2021-09-27T23:02:44.612Z; git: 8da83308eeca865e495e53ef315a249d63ba9332;
jvm 11.0.15+10-Ubuntu-0ubuntu0.22.04.1
Jicofo 2022-05-31 10:53:16.027 WARNING: [1]
org.glassfish.jersey.server.wadl.WadlFeature.configure: JAXBContext
implementation could not be found. WADL feature is disabled.
Jicofo 2022-05-31 10:53:16.109 WARNING: [1]
org.glassfish.jersey.internal.inject.Providers.checkProviderRuntime: A
provider org.jitsi.rest.Version registered in SERVER runtime does not
implement any provider interfaces applicable in the SERVER runtime. Due
to constraint configuration problems the provider org.jitsi.rest.Version
will be ignored.
Jicofo 2022-05-31 10:53:16.306 INFO: [1]
org.eclipse.jetty.server.handler.ContextHandler.doStart: Started
o.e.j.s.ServletContextHandler@662e682a{/,null,AVAILABLE}
Jicofo 2022-05-31 10:53:16.319 INFO: [1]
org.eclipse.jetty.server.AbstractConnector.doStart: Started
ServerConnector@3b05a99b{HTTP/1.1, (http/1.1)}{0.0.0.0:8888}
Jicofo 2022-05-31 10:53:16.319 INFO: [1]
org.eclipse.jetty.server.Server.doStart: Started @2520ms
Jicofo 2022-05-31 10:53:20.698 INFO: [20] [xmpp_connection=client]
XmppProviderImpl.doConnect#209: Connected, JID=null
Jicofo 2022-05-31 10:53:20.803 INFO: [20]
AvModerationHandler.registrationChanged#120: Discovered av_moderation
component at avmoderation.meet.mysteriesoftherosary.net.
Jicofo 2022-05-31 10:53:20.823 INFO: [20]
ConferenceIqHandler.registrationChanged#183: Using breakout room
component address: breakout.meet.mysteriesoftherosary.net
Jicofo 2022-05-31 10:53:20.938 INFO: [20] [type=bridge
brewery=jvbbrewery] BaseBrewery.start#171: Joined the room.
Jicofo 2022-05-31 10:53:20.939 INFO: [20] [xmpp_connection=client]
XmppProviderImpl.fireRegistrationStateChanged#314: Set replyTimeout=PT15S
Jicofo 2022-05-31 10:53:25.997 INFO: [31] [type=bridge
brewery=jvbbrewery] BaseBrewery.addInstance#341: Added brewery instance:
jvbbrewery@internal.auth.meet.mysteriesoftherosary.net/26a9ba48-87a3-4eba-931b-14127337d8ab
Jicofo 2022-05-31 10:53:26.005 WARNING: [31] Main$1.warn#154: Key
‘jicofo.bridge.average-participant-packet-rate-pps’ from source
‘typesafe config (reloaded 1 times)’ is deprecated: use
jicofo.bridge.average-participant-stress
Jicofo 2022-05-31 10:53:26.007 INFO: [31]
BridgeSelector.addJvbAddress#94: Added new videobridge:
Bridge[jid=jvbbrewery@internal.auth.meet.mysteriesoftherosary.net/26a9ba48-87a3-4eba-931b-14127337d8ab,
version=null, relayId=null, region=null, stress=0.00]
Jicofo 2022-05-31 10:53:26.011 INFO: [34] JvbDoctor.bridgeAdded#129:
Scheduled health-check task for:
Bridge[jid=jvbbrewery@internal.auth.meet.mysteriesoftherosary.net/26a9ba48-87a3-4eba-931b-14127337d8ab,
version=2.1.681-g3544ed05, relayId=null, region=null, stress=0.00]
Jicofo 2022-05-31 10:56:38.961 INFO: [56]
ConferenceIqHandler.handleConferenceIq#63: Focus request for room:
rosary@conference.[an error occurred while processing this
directive]meet.mysteriesoftherosary.net
Jicofo 2022-05-31 10:56:38.981 INFO: [56] [room=rosary@conference.[an
error occurred while processing this
directive]meet.mysteriesoftherosary.net]
JitsiMeetConferenceImpl.#268: Created new conference.
Jicofo 2022-05-31 10:56:38.982 INFO: [56] [room=rosary@conference.[an
error occurred while processing this
directive]meet.mysteriesoftherosary.net]
JitsiMeetConferenceImpl.joinTheRoom#452: Joining rosary@conference.[an
error occurred while processing this directive]meet.mysteriesoftherosary.net
Jicofo 2022-05-31 10:56:38.991 INFO: [56] [room=rosary@conference.[an
error occurred while processing this
directive]meet.mysteriesoftherosary.net]
ColibriV2SessionManager.expire#115: Expiring.
Jicofo 2022-05-31 10:56:38.992 INFO: [56] [room=rosary@conference.[an
error occurred while processing this
directive]meet.mysteriesoftherosary.net]
JitsiMeetConferenceImpl.stop#429: Stopped.
Jicofo 2022-05-31 10:56:38.992 WARNING: [56]
FocusManager.conferenceRequest#212: Exception while trying to start the
conference
org.jivesoftware.smack.XMPPException$XMPPErrorException: XMPP error
reply received from conference.[an error occurred while processing this
directive]meet.mysteriesoftherosary.net: XMPPError:
remote-server-not-found - cancel. Generated by
auth.meet.mysteriesoftherosary.net
at
org.jivesoftware.smack.XMPPException$XMPPErrorException.ifHasErrorThenThrow(XMPPException.java:171)
at
org.jivesoftware.smack.XMPPException$XMPPErrorException.ifHasErrorThenThrow(XMPPException.java:165)
at
org.jivesoftware.smack.StanzaCollector.nextResultOrThrow(StanzaCollector.java:284)
at
org.jivesoftware.smack.StanzaCollector.nextResultOrThrow(StanzaCollector.java:228)
at
org.jivesoftware.smackx.disco.ServiceDiscoveryManager.discoverInfo(ServiceDiscoveryManager.java:606)
at
org.jivesoftware.smackx.disco.ServiceDiscoveryManager.discoverInfo(ServiceDiscoveryManager.java:578)
at
org.jivesoftware.smackx.muc.MultiUserChatManager.getMucServiceDiscoInfo(MultiUserChatManager.java:425)
at
org.jivesoftware.smackx.muc.MultiUserChat.enter(MultiUserChat.java:353)
at
org.jivesoftware.smackx.muc.MultiUserChat.createOrJoin(MultiUserChat.java:543)
at
org.jivesoftware.smackx.muc.MultiUserChat.createOrJoin(MultiUserChat.java:518)
at
org.jitsi.impl.protocol.xmpp.ChatRoomImpl.joinAs(ChatRoomImpl.java:247)
at
org.jitsi.impl.protocol.xmpp.ChatRoomImpl.join(ChatRoomImpl.java:215)
at
org.jitsi.jicofo.conference.JitsiMeetConferenceImpl.joinTheRoom(JitsiMeetConferenceImpl.java:479)
at
org.jitsi.jicofo.conference.JitsiMeetConferenceImpl.start(JitsiMeetConferenceImpl.java:315)
at
org.jitsi.jicofo.FocusManager.conferenceRequest(FocusManager.java:207)
at
org.jitsi.jicofo.FocusManager.conferenceRequest(FocusManager.java:161)
at
org.jitsi.jicofo.FocusManager.conferenceRequest(FocusManager.java:140)
at
org.jitsi.jicofo.xmpp.ConferenceIqHandler.handleConferenceIq(ConferenceIqHandler.kt:72)
at
org.jitsi.jicofo.xmpp.ConferenceIqHandler.handleIQRequest$lambda-4(ConferenceIqHandler.kt:156)
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)
Jicofo 2022-05-31 10:56:39.005 SEVERE: [56] Main.lambda$main$0#52: An
uncaught exception occurred in thread=Thread[Jicofo Global IO
Poolpool-2-thread-1,5,main]

Something’s not quite right with your config.js file. In https://meet.mysteriesoftherosary.net/config.js I see:

Which explains the following error in Jicofo:

XMPP error
reply received from conference.[an error occurred while processing this
directive]
meet.mysteriesoftherosary.net: XMPPError:
remote-server-not-found - cancel

Perhaps SSI is not enabled for the nginx location block that’s serving up config.js?

I have no clue as to where config.js is or what should be in it… https://meet.mysteriesoftherosary.net normally resolves to /var/www/meet.mysteriesoftherosary.net/. there is nothing there except the key and chained.crt

For a default Jitsi install, that file can be found in /etc/jitsi/meet/YOURDOMAIN-config.js. It’s contents should look something like this: jitsi-meet/config.js at master · jitsi/jitsi-meet · GitHub

When the app loads https://YOURDOMAIN/config.js, that file is served up by nginx, which will also replace the <!--# echo var... --> directive with dynamically inferred values.

Take a look in /etc/nginx/sites-available/YOURDOMAIN.conf – you should see the location blocks that handles /config.js requests which looks something like this:

    location = /config.js {
        alias /etc/jitsi/meet/YOURDOMAIN-config.js;
    }

    # ...

    location ~ ^/([^/?&:'"]+)/config.js$
    {
        set $subdomain "$1.";
        set $subdir "$1/";

        alias /etc/jitsi/meet/YOURDOMAIN-config.js;
    }

Also noticed that https://meet.mysteriesoftherosary.net/something_arbitrary/config.js returns a 404 rather than the config. I would have expected the same config.js content to be returned but with the <!--# echo var... --> block replaced with “something_arbitrary/”.

Are you comfortable sharing your nginx config?

Also, do you see any errors in nginx logs? /var/log/nginx/error.log