On Tue, 15 Dec 2020, Guennadi Liakhovetski wrote: > Hi, > > I'm trying to set up a ws -> wss proxy to my.webhookrelay.com : > > <VirtualHost 192.168.x.y:80> > ServerName local.name > SSLProxyEngine On > RewriteEngine on > ProxyRequests Off > ProxyPass /wsrelay wss://my.webhookrelay.com/v1/socket > ProxyPassReverse /wsrelay wss://my.webhookrelay.com/v1/socket > </VirtualHost> > > and the server seems to close connection, this is what I'm getting in the > log: The problem was, that the server was only accepting TLSv1.3 and my version of apache didn't support it yet. A newer one solved the issue. Thanks Guennadi > > [Tue Dec 15 19:25:02.337455 2020] [rewrite:trace2] [pid 11759:tid 3056597824] mod_rewrite.c(477): [client 192.168.x.y:29429] 192.168.x.y - - [local.name/sid#b70da9e8][rid#b6438058/initial] init rewrite engine with requested uri /wsrelay > [Tue Dec 15 19:25:02.337681 2020] [rewrite:trace1] [pid 11759:tid 3056597824] mod_rewrite.c(477): [client 192.168.x.y:29429] 192.168.x.y - - [local.name/sid#b70da9e8][rid#b6438058/initial] pass through /wsrelay > [Tue Dec 15 19:25:02.337711 2020] [proxy:trace2] [pid 11759:tid 3056597824] mod_proxy.c(656): [client 192.168.x.y:29429] AH03461: attempting to match URI path '/wsrelay' against prefix '/wsrelay' for proxying > [Tue Dec 15 19:25:02.337742 2020] [proxy:trace1] [pid 11759:tid 3056597824] mod_proxy.c(741): [client 192.168.x.y:29429] AH03464: URI path '/wsrelay' matches proxy handler 'proxy:wss://my.webhookrelay.com/v1/socket' > [Tue Dec 15 19:25:02.337815 2020] [proxy_wstunnel:trace1] [pid 11759:tid 3056597824] mod_proxy_wstunnel.c(51): [client 192.168.x.y:29429] canonicalising URL //my.webhookrelay.com/v1/socket > [Tue Dec 15 19:25:02.337901 2020] [proxy:trace2] [pid 11759:tid 3056597824] proxy_util.c(1982): [client 192.168.x.y:29429] *: using default reverse proxy worker for wss://my.webhookrelay.com:443/v1/socket (no keepalive) > [Tue Dec 15 19:25:02.337936 2020] [proxy:debug] [pid 11759:tid 3056597824] mod_proxy.c(1229): [client 192.168.x.y:29429] AH01143: Running scheme wss handler (attempt 0) > [Tue Dec 15 19:25:02.338008 2020] [proxy_wstunnel:debug] [pid 11759:tid 3056597824] mod_proxy_wstunnel.c(305): [client 192.168.x.y:29429] AH02451: serving URL wss://my.webhookrelay.com:443/v1/socket > [Tue Dec 15 19:25:02.338094 2020] [proxy:debug] [pid 11759:tid 3056597824] proxy_util.c(2153): AH00942: WSS: has acquired connection for (*) > [Tue Dec 15 19:25:02.338147 2020] [proxy:debug] [pid 11759:tid 3056597824] proxy_util.c(2206): [client 192.168.x.y:29429] AH00944: connecting wss://my.webhookrelay.com:443/v1/socket to my.webhookrelay.com:443 > [Tue Dec 15 19:25:02.341044 2020] [proxy:debug] [pid 11759:tid 3056597824] proxy_util.c(2415): [client 192.168.x.y:29429] AH00947: connected /v1/socket to my.webhookrelay.com:443 > [Tue Dec 15 19:25:02.341212 2020] [proxy:trace2] [pid 11759:tid 3056597824] proxy_util.c(2847): WSS: fam 2 socket created to connect to * > [Tue Dec 15 19:25:02.357349 2020] [proxy:debug] [pid 11759:tid 3056597824] proxy_util.c(2881): AH02824: WSS: connection established with 104.155.59.108:443 (*) > [Tue Dec 15 19:25:02.357545 2020] [proxy:debug] [pid 11759:tid 3056597824] proxy_util.c(3048): AH00962: WSS: connection complete to 104.155.59.108:443 (my.webhookrelay.com) > [Tue Dec 15 19:25:02.358435 2020] [proxy_wstunnel:trace2] [pid 11759:tid 3056597824] mod_proxy_wstunnel.c(122): [client 192.168.x.y:29429] sending request > [Tue Dec 15 19:25:02.374855 2020] [proxy_wstunnel:trace2] [pid 11759:tid 3056597824] mod_proxy_wstunnel.c(142): [client 192.168.x.y:29429] setting up poll() > [Tue Dec 15 19:25:02.375026 2020] [proxy_wstunnel:trace1] [pid 11759:tid 3056597824] mod_proxy_wstunnel.c(188): [client 192.168.x.y:29429] AH02445: woke from poll(), i=1 > [Tue Dec 15 19:25:02.375053 2020] [proxy_wstunnel:trace1] [pid 11759:tid 3056597824] mod_proxy_wstunnel.c(197): [client 192.168.x.y:29429] AH02446: sock was readable > [Tue Dec 15 19:25:02.375078 2020] [proxy:debug] [pid 11759:tid 3056597824] proxy_util.c(3828): (103)Software caused connection abort: [client 192.168.x.y:29429] AH03308: ap_proxy_transfer_between_connections: error on sock - ap_get_brigade > [Tue Dec 15 19:25:02.375136 2020] [proxy:trace2] [pid 11759:tid 3056597824] proxy_util.c(3837): (103)Software caused connection abort: [client 192.168.x.y:29429] ap_proxy_transfer_between_connections complete > [Tue Dec 15 19:25:02.375161 2020] [proxy_wstunnel:trace2] [pid 11759:tid 3056597824] mod_proxy_wstunnel.c(255): [client 192.168.x.y:29429] finished with poll() - cleaning up > [Tue Dec 15 19:25:02.375185 2020] [proxy:debug] [pid 11759:tid 3056597824] proxy_util.c(2168): AH00943: WSS: has released connection for (*) > [Tue Dec 15 19:25:02.375215 2020] [proxy:debug] [pid 11759:tid 3056597824] proxy_util.c(2988): [remote 104.155.59.108:443] AH02642: proxy: connection shutdown > > Is there any way to get a more detailed log with an indication what > exactly it is that the server dislikes? And eventually how do I fix this? > > Thanks > Guennadi > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx > For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|