Re: Reverse proxy stalling forever (Apache Users)

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 <galex-713@xxxxxxxxxxxx> 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:root@xxxxxxxxxxxxxxxxxxxxx:/etc/prosody/prosody.cfg.lua" disposition=attachment> <#/part> <#part type="application/octet-stream" filename="/sudo:root@xxxxxxxxxxxxxxxxxxxxx:/etc/apache2/sites-enabled/meet.galex-713.eu.conf" disposition=attachment> <#/part>