Error in prosody-config after upgrades?

After first having upgraded my Jitsi-meet install to jitsi-videobridge2(which by the way was a bit problematic, with some dependency-problems) and today some new updates I noticed something strange in my prosody-configuration in /etc/prosody/conf.d. My servers domain-name is jitsi.egmont-hs.dk

VirtualHost “jitsi.egmont-hs.dk”
authentication = “anonymous”
ssl = {
key = “/etc/prosody/certs/jitsi.egmont-hs.dk.key”;
certificate = “/etc/prosody/certs/jitsi.egmont-hs.dk.crt”;
}
– we need bosh
modules_enabled = {
“bosh”;
“pubsub”;
“ping”; – Enable mod_ping
}

    c2s_require_encryption = false

Component “conference.jitsi.egmont-hs.dk” “muc”
storage = “none”
admins = { “focus@auth.jitsi.egmont-hs.dk” }

Component “jitsi-videobridge.jitsi.egmont-hs.dk”
component_secret = “*********”

VirtualHost “auth.jitsi.egmont-hs.dk”
ssl = {
key = “/etc/prosody/certs/auth.jitsi.egmont-hs.dk.key”;
certificate = “/etc/prosody/certs/auth.jitsi.egmont-hs.dk.crt”;
}
authentication = “internal_plain”

Component “focus.jitsi.egmont-hs.dk”
component_secret = “********”

Component “internal.auth.jitsi.egmont-hs.dk” “muc”
storage = “none”
modules_enabled = { “ping”; }
admins = { “focusUser@auth.jitmeet.example.com”, “jvb@auth.jitmeet.example.com” }

This last part with

focusUser@auth.jitmeet.example.com", “jvb@auth.jitmeet.example.com

has to be wrong, right? Has anyone but me had this problem?
I’ll change it to the right domain. But should this focusUser not just be focus?
Any way, the system is running exept that I get these warnings in prosody.log:

jitsi-videobridge.jitsi.egmont-hs.dk:component warn Component not connected, bouncing error

I’m new to this, so I’m not sure that it is related.

So after correcting the domain in the prosody-config, I’m stuck with an error, that i can’t figure out.
When prosody starts, it correctly connects the two clients, focus and jvb. But then I repeatedly get this warning in the prosody-log: Component not connected, bouncing error
Here is an extract from the prosody-log, when it starts:
------------------------
|Apr 01 19:26:31 mod_posix|info|Prosody is about to detach from the console, disabling further console output|
|Apr 01 19:26:31 mod_posix|info|Successfully daemonized to PID 25217|
|Apr 01 19:26:32 c2s561b71c4e6d0|info|Client connected|**
|Apr 01 19:26:32 c2s561b71c4e6d0|info|Stream encrypted (TLSv1.2 with ECDHE-RSA-AES256-GCM-SHA384)|**
|Apr 01 19:26:32 c2s561b71c4e6d0|info|Authenticated as focus@auth.jitsi.egmont-hs.dk|**
| |Apr 01 19:26:32 <jitsi-videobridge.jitsi.egmont-hs.dk:component|warn|Component not connected, bouncing error for: iq id=‘ZCZM9-34’ type=‘get’ to=‘jitsi-videobridge.jitsi.egmont-hs.dk’ from=‘focus@auth.jitsi.egmont-hs.dk/focus93470605891185’>|
|Apr 01 19:26:33 jcp561b71cefb50|info|Incoming Jabber component connection|
|Apr 01 19:26:33 focus.jitsi.egmont-hs.dk:component|info|External component successfully authenticated|
|Apr 01 19:26:33 c2s561b71ccdf70|info|Client connected|
|Apr 01 19:26:33 c2s561b71ccdf70|info|Stream encrypted (TLSv1.2 with ECDHE-RSA-AES256-GCM-SHA384)|
|Apr 01 19:26:33 c2s561b71ccdf70|info|Authenticated as jvb@auth.jitsi.egmont-hs.dk|
|Apr 01 19:27:02 jitsi-videobridge.jitsi.egmont-hs.dk:component|warn|Component not connected, bouncing error for: |
----------------------
Then this “bouncing” error simply repeats every 30 seconds. But it doesn’t seem to impact the servers operation. It works just fine, it seems.
Has anyone got a clue about what causes this error?