Re: [users@httpd] Reverse proxy stalling forever

[Alexandre Garreau]

The strange thing is whatever I’m changing the redirection destination
of the ProxyPass/RewriteRule/whatever, it’s stalling.  I’m unable to
proxy it to whatever.  I can put whatever IP or host,
wildebeest.gnu.org, google.com, etc. it always stalls.  The only
exception is when I forward it to a closed port, for example on my
machine.

How a proxy can stall forever like that? Why doesn’t it tell anything
about connection opening or something alike in the logs?

Re: [users@httpd] Reverse proxy stalling forever

[Alexandre Garreau]

Yes pretty everything works.  And localhost is 127.0.0.1 and ::.

netstat -ln says it listen on localnost, that is 0.0.0.0 and ::.  And
even using those it doesn’t work.

Re: [users@httpd] Reverse proxy stalling forever

[Yehuda Katz]

I see that I can access your config.js 
from my browser, so httpd is serving that vhost.

What does localhost resolve to and is prosody listening on that IP address.
For example, maybe it is resolving to IPv6.
Check with netstat -ln to see what IP prosody is listening on. You should
try using that IP explicitly in RewriteRule instead of localhost.

- Y

On Tue, Jan 22, 2019 at 10:47 PM Alexandre Garreau 
wrote:

> Normally I have no firewall, and what’s behind ports 5280/5281 are the
> standard RFC-defined xmpp bosh ports (xmpp over http), ran by prosody.
>
> I can attach my prosody configuration file but I supposed it wasn’t of
> much help.
>
> And normally I don’t run any firewall. At least I didn’t set up any, so
> unless debian (stable) managed to install one without bothering me (that is
> without having to bug me about which ports to open or not), it’s very
> unlikely.
>
> <#part type="application/octet-stream"
> filename="/sudo:r...@portable.galex-713.eu:/etc/prosody/prosody.cfg.lua"
> disposition=attachment> <#/part> <#part type="application/octet-stream"
> filename="/sudo:r...@portable.galex-713.eu:/etc/apache2/sites-enabled/meet.galex-713.eu.conf"
> disposition=attachment> <#/part>
>

Re: [users@httpd] Reverse proxy stalling forever

[Alexandre Garreau]

meet.galex-713.eu.conf
Description: Binary data

Re: [users@httpd] Reverse proxy stalling forever

[Yehuda Katz]

The configuration you sent doesn't show your server running on port
5280/5281, so we can't compare the configuration and see what might be
different.
My number one suspect would be your firewall.

- Y

On Tue, Jan 22, 2019 at 7:40 PM Alexandre Garreau 
wrote:

> Hi,
>
> I’m trying to make Jitsi Meet work. Initially it worked, but since the
> while it didn’t. So I’m investigating everything that could be going wrong.
>
> Here the VirtualHost Jitsi installation automatically created, with
> further additions by me (GnuTLS support, better rewritting supporting other
> alphabets): https://paste.debian.net/1062011/
>
> I was asked « apachectl -S » output on #httpd:
> http://paste.debian.net/1062013/
>
> So because HSTS, if you try http://meet.galex-713.eu:5280/http-bind it
> might not work, in which case try https://meet.galex-713.eu:5281/http-bind
>
> You can also try with curl: normally it should say “it works” and a link
> to prosody documentation.
>
> And that’s what should also be displayed by
> https://meet.galex-713.eu/http-bind but it stalls forever, any idea how’s
> this?
>
> Whenever I connect to this, all apache logs stay silent, why?
>

[users@httpd] Reverse proxy stalling forever

[Alexandre Garreau]

Hi,

I’m trying to make Jitsi Meet work.  Initially it worked, but since the
while it didn’t.  So I’m investigating everything that could be going
wrong.

Here the VirtualHost Jitsi installation automatically created, with
further additions by me (GnuTLS support, better rewritting supporting
other alphabets):
https://paste.debian.net/1062011/

I was asked « apachectl -S » output on #httpd:
http://paste.debian.net/1062013/

So because HSTS, if you try http://meet.galex-713.eu:5280/http-bind it
might not work, in which case try
https://meet.galex-713.eu:5281/http-bind

You can also try with curl: normally it should say “it works” and a link
to prosody documentation.

And that’s what should also be displayed by
https://meet.galex-713.eu/http-bind but it stalls forever, any idea
how’s this?

Whenever I connect to this, all apache logs stay silent, why?