I managed to Setup a new Jitsi Server on a hosted VM (Ubuntu 18.0.4), following this Guide,
Meeting-Url is meet.dr-bit-online.de https://www.digitalocean.com/community/tutorials/how-to-install-jitsi-meet-on-ubuntu-18-04-de
Certificates (Let’s Encrypt) seem to be fine.
Participants from same Wifi Network can connect flawlessly, but trying to Join a meeting from other Network (different Provider) makes the participant showing up with no audio or video.
For them it’s the same thing vice-versa. the only see their own audio/video information, but nothing from the moderator.
stream:error>This server does not serve auth.meet.dr-bit-online.de</stream:error>
at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader.parsePackets(XMPPTCPConnection.java:1064)
at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader.access$300(XMPPTCPConnection.java:1000)
at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader$1.run(XMPPTCPConnection.java:1016)
at java.lang.Thread.run(Thread.java:748)
2020-11-02 22:23:27.729 INFO: [20] HealthChecker.run#170: Performed a successful health check in PT0S. Sticky failure: false
2020-11-02 22:23:28.268 INFO: [15] [hostname=localhost id=shard] MucClient$1.connected#271: Connected.
2020-11-02 22:23:28.268 INFO: [15] [hostname=localhost id=shard] MucClient.lambda$getConnectAndLoginCallable$7#680: Logging in.
2020-11-02 22:23:28.412 INFO: [15] [hostname=localhost id=shard] MucClient$MucWrapper.join#788: Joined MUC: jvbbrewery@internal.auth.meet.dr-bit-online.de
2020-11-02 22:23:37.727 INFO: [20] HealthChecker.run#170: Performed a successful health check in PT0S. Sticky failure: false
2020-11-02 22:23:47.727 INFO: [20] HealthChecker.run#170: Performed a successful health check in PT0S. Sticky failure: false
2020-11-02 22:23:57.727 INFO: [20] HealthChecker.run#170: Performed a successful health check in PT0S. Sticky failure: false
2020-11-02 22:24:07.727 INFO: [20] HealthChecker.run#170: Performed a successful health check in PT0S. Sticky failure: false
2020-11-02 22:24:17.727 INFO: [20] HealthChecker.run#170: Performed a successful health check in PT0S. Sticky failure: false
2020-11-02 22:24:17.796 INFO: [19] VideobridgeExpireThread.expire#140: Running expire()
Hey, I checked this, but it didn’t solve it.
It’s always the same. Clients from the same network can sucessfully join the meeting with working audio/video, clients from different IP-Ranges can’t.
Besides, my hosts file looks like this. Is this alright?:
I have the same problem also. I have port forward - 80, 443, 10000 - on router and dns linked to home ip address but nobody can connect through android app or web browser!!
I just installed latest jitsi-meet on a digital ocean droplet and opened the UDP port 10000, and tested with three participants video call without any issues.
I have all those ports open on server and I have port forwarded on the router for 80, 443, and 10000 but nobody can join. Do you think it could be the use of ubuntu on rpi as opposed to using debian arm edition?
# Directory where all configuration will be stored
CONFIG=~/.jitsi-meet-cfg
# Exposed HTTP port
HTTP_PORT=8000
# Exposed HTTPS port
HTTPS_PORT=443
# System time zone
TZ=Europe/Amsterdam
# Public URL for the web service (required)
PUBLIC_URL=https://dev89.aarenet.com
# IP address of the Docker host
# See the "Running behind NAT or on a LAN environment" section in the Handbook:
# https://jitsi.github.io/handbook/docs/devops-guide/devops-guide-docker#running-behind-nat-or-on-a-lan-environment
DOCKER_HOST_ADDRESS=185.150.4.89
My problem was a classic mistake, tcp open instead of udp, sorry for bothering everyone, without this mistake I would have had an amazingly smooth setup!
Hey guys, sorry for the late reply.
No, i was not able to solve the problem.
In my case it was no matter of open ports.
As far as I know it was a matter of certification.
In first place I tried to use my own certs to deploy.
It didn’t work as described above.
Later on I canceled it to make it run on this provider’s platform (ionos) and changed to another (netcup) to make a fresh new start in new environment.
Furthermore I didn’t use my own certs (though I think it should work too) and used the letsencrypt thing which worked flawlessly.
So in conclusion I really don’t know what exactly was the problem.
To me it was an unsatisfying turn of events but in the end it was working.
