Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Apache 2.4 ProxyPass Configuration

See original GitHub issue

With 0.9 I was able to proxy our websockets through Apache 2.4 using the following config:

ProxyPass /socket.io/1/websocket ws://localhost:8082/socket.io/1/websocket
ProxyPassReverse /socket.io/1/websocket ws://localhost:8082/socket.io/1/websocket

ProxyPass /socket.io/ http://localhost:8082/socket.io/
ProxyPassReverse /socket.io/ http://localhost:8082/socket.io/

I’m attempting to migrate to 1.0.6 now and I immediately noticed that the socket endpoint changed, but updating the ProxyPass config like so does not seem to do the trick.

ProxyPass /socket.io/?EIO=2&transport=websocket ws://localhost:8082/socket.io/?EIO=2&transport=websocket
ProxyPassReverse /socket.io/?EIO=2&transport=websocket ws://localhost:8082/socket.io/?EIO=2&transport=websocket

ProxyPass /socket.io/ http://localhost:8082/socket.io/
ProxyPassReverse /socket.io/ http://localhost:8082/socket.io/

Chrome reports over and over again that it receives a 400 error when trying to open the websocket. There’s no output in the console on the server to indicate that any connection attempt was received (DEBUG=socket.io).

Is there some other configuration factor that I need for this to work?

Issue Analytics

State:
Created 9 years ago
Comments:37 (4 by maintainers)

Top GitHub Comments

14reactions

silasrmcommented, Jul 16, 2016

I’m using this config:

<VirtualHost *:80>
    ServerName ws.domain.com

    RewriteEngine On
    RewriteCond %{QUERY_STRING} transport=polling
    RewriteRule /(.*)$ http://localhost:3000/$1 [P]

    ProxyRequests off
    ProxyPass /socket.io/ ws://localhost:3000/socket.io/
    ProxyPassReverse /socket.io/ ws://localhost:3000/socket.io/

    ErrorLog /.../logs/nodejs_error_log
    CustomLog /.../logs/nodejs_access_log common
    LogLevel warn
</VirtualHost>

Before, install proxy modules:

sudo a2enmod proxy proxy_http proxy_wstunnel

Is ok on Apache/2.4.7

14reactions

lopezdonaquecommented, Jun 23, 2015

Hi,

I have used “Connection” header detection to resolve it.

<VirtualHost x.x.x.x:443>
  ServerName domain.local

  RewriteEngine On
  RewriteCond %{HTTP:Connection} Upgrade [NC]
  RewriteRule /(.*) ws://x.x.x.x:3000/$1 [P,L]

  ProxyPass / http://x.x.x.x:3000/

  SSLEngine on
  SSLCertificateFile /etc/apache2/ssl/STAR_x_com.crt
  SSLCertificateKeyFile /etc/apache2/ssl/STAR_x_com.key
  SSLCertificateChainFile /etc/apache2/ssl/STAR_x_com.ca-bundle

  CustomLog /var/log/apache2/access.x.log combined
  ErrorLog /var/log/apache2/error.x.log

 </VirtualHost>

See issue at: https://github.com/faye/faye/issues/387