search

luvolondon / fvtt-module-jitsiwebrtc

Jitsi WebRTC client for FVTT
32 stars 7 forks source link

http-bind request error #81

Open Kayne opened 3 years ago

Kayne commented 3 years ago

Hi there!

I run Jitsi as docker container. After some initial issues with configuratio, I finally setup it like this:

Server Settings

Jitsi WEBRTC settings

I had to enable XMPP_CROSS_DOMAIN=true in jitsi configuration to make CORS works.

And it finally worked. Audio/Video looks good (I was testing with few private sessions in browser). However, I see at least two issues in console and under network tab.

First, the /http-bind request is working, as in connecting to jitsi, but the answer doesn't look "good":

http-bind response

Also, I see frequently in console this error:

ping error

And I think they are linked to each other, because when I cleared out the console & network tab, the console error pops up the same time the request to http-bind is made.

So in general everything seems to work but I really don't like these errors which pops up in console every so often, spamming like crazy. What could I miss?

bekriebel commented 3 years ago

Sorry, I haven't been available the last couple of weeks due to some family emergencies. I hope to take a look at things later this week. Is this still an issue?

Kayne commented 3 years ago

No problem! Yes, the issue is still on. I couldn't track it down to be more helpful :(

scooper4711 commented 2 years ago

I'm having a similar issue. I have set up jitsi and foundry as docker containers on the same host. It's sending /http-bind to the wrong server though. I have two reverse proxies - vtt.mydomain goes to foundry, and meet.mydomain goes to jitsi. In the network panel of developer tools, I see a call to /http-bind going to the wrong server. It's going to vtt instead of meet. They have the same IP address, but I'm using reverse proxy based on server name, so the /http-bind isn't working in foundry.

scooper4711 commented 2 years ago

enabling "use custom jitsi urls" got me past this problem. Now I just have to fight CORS. The allow-origin has multiple values and should only have one. sigh.

bekriebel commented 2 years ago

Unfortunately, the way Jitsi handles these routes leaves a lot to be desired. To be honest, I've stopped using Jitsi due to a number of issues. I'd recommend trying out a new module that I have just launched, it uses LiveKit for the AV server, which has been much more reliable and easier to configure: https://foundryvtt.com/packages/avclient-livekit

Does anyone have specific questions regarding this issue? I don't believe it is a module issue, but is being caused by the complexity of configuring Jitsi. I wish I could help, but fixing issues like this normally require me to ask for access to your Jitsi server to debug the specific issue, and that's not something I'm really able to provide at this time.