Prosody HTTP request not responding on stable version


#1

Hello,

I’m facing a problem with prosody. After I updated Jitsi-Meet to the latest stable version, http requests suddenly stopped working

admin@gipsy-ida01:~$ curl -vv  'http://localhost:5280/room?domain=meet.gipsy-ida01.ida.melanie2.i2&room=hamzahamza123456&subdomain='
* Hostname was NOT found in DNS cache
*   Trying 127.0.0.1...
* Connected to localhost (127.0.0.1) port 5280 (#0)
> GET /room?domain=meet.gipsy-ida01.ida.melanie2.i2&room=hamzahamza123456&subdomain=     HTTP/1.1
> User-Agent: curl/7.38.0
> Host: localhost:5280
> Accept: */*
> 

These HTTP requests are very useful for my real-time stats apps… and they used to work on the previous stable versions.
Do you have any idea why it doesn’t work anymore ?

Regards
Hamza


#2

No idea why this would stop working. So there is no response to that? Can it be some firewall? Check the prosody logs do you see any errors?


#3

There are no errors in prosody logs when executing the request. I don’t think it’s firewall issue because I send the request to localhost from the same server.

I think the problem is this line : https://github.com/jitsi/jitsi-meet/blob/master/resources/prosody-plugins/mod_muc_size.lua#L186

I added the line below before the return statement and it displays the result in prosody log file as expected.

log("info", GET_response.body);
return GET_response;

This is weird…


#4

Which versions of those modules are you using?
We recently fixed(23 days ago) a problem with the async execution:


#5

Well that’s strange … I am using the modules provided with the latest stable version of Jitsi-Meet that was released on 2018-06-14
When I downgrade the package jitsi-meet-tokens to version 1.0.2740-1 it magically works.


#6

I will test it today and will update you. We had been modifying stuff around tokens, so it is possible to be broken.


#7

Ok, thanks for the quick answer


#8

I can confirm it is broken. We will fix it. Thanks for the report.
This commit broke it: https://github.com/jitsi/jitsi-meet/commit/fa9a4480e619c3d0b969225bbdc2a88e3c6072b6#diff-75511b8d0165812b9af3158f0df96774


#9

@hkhait You can apply this patch which I believe fixes it: https://github.com/jitsi/jitsi-meet/pull/3231


#10

Thanks for the patch. It works like a charm :ok_hand: