Hello Turkel, do you have mod_proxy_wstunnel configured at your Apache server?
On Thu, May 10, 2018 at 10:46 AM, Coscend@OM <om.insig...@coscend.com> wrote: > Hello Turkel, > > Further, to isolate the issue, you might want to test run your installation > without the proxy server and with only firewall router. Some firewall > routers do not support WebSockets in default setting. > > To bypass proxy server, you can use > IP address (within LAN, either in local network or through VPN) > Server / domain name. > > Thank you. > > Sincerely, > > Hemant K. Sabat > ------------------------------------------------------------------ > Real-time, Interactive Video Collaboration, Tele-healthcare, Tele-education, > Telepresence Services, on the fly… > ------------------------------------------------------------------ > CONFIDENTIALITY NOTICE: See 'Confidentiality Notice Regarding E-mail Messages > from Coscend Communications Solutions' posted at: > http://www.Coscend.com/Anchor/Common/Terms_and_Conditions.html > > > > -----Original Message----- > From: Coscend@OM <om.insig...@coscend.com> > Sent: Wednesday, May 9, 2018 5:43 PM > To: 'Turkel Alizadeh' <tur...@gmx.com>; user@openmeetings.apache.org > Cc: user@openmeetings.apache.org > Subject: Apache websocket 404 > > Hello Tukrel, > > So that I understand your setup to be able to provide any additional vectors, > could you share the following: > Is your setup: Reverse proxy HTTPD + HTTP OM? > Are you converting HTTPS --> HTTP in front of reverse proxy HTTPD? > > If so, did you happen to review the log files of your OM installation? And > the access log files of your HTTPD installation? > > Thank you. > > Sincerely, > > Hemant K. Sabat > ------------------------------------------------------------------ > Real-time, Interactive Video Collaboration, Tele-healthcare, Tele-education, > Telepresence Services, on the fly… > ------------------------------------------------------------------ > CONFIDENTIALITY NOTICE: See 'Confidentiality Notice Regarding E-mail Messages > from Coscend Communications Solutions' posted at: > http://www.Coscend.com/Anchor/Common/Terms_and_Conditions.html > > > -----Original Message----- > From: Turkel Alizadeh <tur...@gmx.com> > Sent: Wednesday, May 9, 2018 1:57 PM > To: user@openmeetings.apache.org; om.insig...@coscend.com > Cc: user@openmeetings.apache.org > Subject: Re: RE: Apache websocket 404 > > Hi Hemant, > > I am resending same message because web mailing shows improper format of > content. > http proxy works OK as it redirects domain root requests / to server internal > port localhost:5080. This is also same with ws redirection to internal > localhost ws link with port 5080. Login page works ok which gets redirected > with http proxy: > ProxyPass / http://localhost:5080/ > ProxyPassReverse / http://localhost:5080/ > > > Regards, > Turkel. > > > > > Sent: Wednesday, May 09, 2018 at 6:53 AM > From: "Coscend@OM" <om.insig...@coscend.com> > To: user@openmeetings.apache.org > Subject: RE: Apache websocket 404 > > Hello Turkel, > > Here is a vector to investigate. Should the URLs below point to the same > domain? Without this, how would the WebSocket request not find the resource > to display? > ServerName con.domain.com > … > ProxyPass / http://localhost:5080/ > > Thank you. > > Sincerely, > > Hemant K. Sabat > > Coscend Communications Solutions > www.Coscend.com[http://www.coscend.com/] > ------------------------------------------------------------------ > Real-time, Interactive Video Collaboration, Tele-healthcare, Tele-education, > Telepresence Services, on the fly… > ------------------------------------------------------------------ > CONFIDENTIALITY NOTICE: See 'Confidentiality Notice Regarding E-mail Messages > from Coscend Communications Solutions' posted at: > http://www.Coscend.com/Anchor/Common/Terms_and_Conditions.html[http://www.Coscend.com/Anchor/Common/Terms_and_Conditions.html] > > > > > From: Turkel Alizadeh <tur...@gmx.com> > Sent: Tuesday, May 8, 2018 3:03 PM > To: user@openmeetings.apache.org > Subject: Apache websocket 404 > > > Hi, > > > > I am trying to install openmeetings 4.0.3 application into my debian server > by attached tutorial which I got from official openmeetings website. I have > followed every step and got to login page successfully, but I got problem > after login as client cant reach server websocket protocol. I am getting > following error on my browser console: > > > > WebSocket connection to > 'ws://domain.com/openmeetings/wicket/websocket?pageId=2&wicket-ajax-baseurl=.&wicket-app-name=OpenmeetingsApplication' > failed: Error during WebSocket handshake: Unexpected response code: 404 > > > > My apache2 domain configurration is below: > > > > <VirtualHost *:80> > > ServerAdmin m...@domain.com[mailto:m...@domain.com] > > ServerName con.domain.com > > ProxyPreserveHost On > > ProxyRequests Off > > ProxyPass /ws2/ ws://localhost:5080/ > > ProxyPassReverse /ws2/ ws://localhost:5080/ > > ProxyPass /wss2/ ws://YOUR_DOMAIN:WS_PORT/ > > ProxyPass / http://localhost:5080/[http://localhost:5080/] > > ProxyPassReverse / http://localhost:5080/[http://localhost:5080/] > > ErrorLog /var/log/apache2/red5-error_log > > CustomLog /var/log/apache2/red5-access_log common > > </VirtualHost> > > > > > > Please advise possible troublshooting and solution for this issue. > > > > > > Best Regards, > > Turkel. > > > ------------------------------------------------------------ > > [http://www.avg.com/internet-security] > This email has been checked for viruses by AVG antivirus software. > www.avg.com[http://www.avg.com/internet-security] > > > --- > This email has been checked for viruses by AVG. > http://www.avg.com > -- WBR Maxim aka solomax
