I have a Debian Buster system, not behind NAT, but acting with existing virtual apache and prosody names. I installed jitsi, following the quick install install document and it all seemed to go very smoothly, and I saw the the inital page, and can create a test meeting from a client, but when I try to join that meeting from another client, but client meetings show an ‘Unfortunately something went wrong’ message and try to reconnect
On the server I have, in jvb.loc, whether clients are connected or nor, a constant stream of
2020-03-28 19:02:47.887 INFO:  [hostname=localhost id=shard] MucClient.lambda$getConnectAndLoginCallable$7#648: Logging in.
2020-03-28 19:02:47.887 SEVERE:  RetryStrategy$TaskRunner.run#198: org.jivesoftware.smack.sasl.SASLErrorException: SASLError using SCRAM-SHA-1: not-authorized
org.jivesoftware.smack.sasl.SASLErrorException: SASLError using SCRAM-SHA-1: not-authorized
The prosody server log shows
callcontrol.jitsi.mydomain:component warn Component not connected, bouncing error for:
which I suspect is related.
The main thing where I differ from the instructions is that I have not changed /etc/hostname to match the jitsi alias of the machine, as I fear changing it will break a number of other things.
I would like to understand what that step really does before I try that.