We using Apache to serve HTTPS So it works as Apache+SSL <--> OM+HTTP :)
On Tue, 23 Apr 2019 at 11:26, Stefan Kühl <ste...@quatrekuehl.eu> wrote: > > Morning! > > Same to me. Using apache with multiple vHosts on a vps and the redirection > works with the port number (ssl at 5443). So, if you call > https:\\www.domain.com:5443 it will redirect you automatically to > openmeetings. > Wors well with OM 5.0. The quality is great and no delays ;-) > > Greetz > > Stefan > > > > > Am 23.04.2019 06:02, schrieb Maxim Solodovnik: > > Hello Aaron, > > our demo servers using Apache as front-end proxy, > I see no delays > > On Tue, 23 Apr 2019 at 02:22, Aaron Hepp <aaron.h...@gmail.com> wrote: > > > Question for the ones that moved to letting Apache2 be the web front end. Do > you experience long delay times when logging in and high CPU useage then when > you was going into Tomcat directly? > > On 4/21/19 12:14 AM, Maxim Solodovnik wrote: > > I guess you need something like this: > https://httpd.apache.org/docs/2.4/howto/access.html > > On Fri, 19 Apr 2019 at 22:35, Aaron Hepp <aaron.h...@gmail.com> wrote: > > Ok wanted to make sure nothing else was needed inside OM besides adding that > line. > > Yes in the install my openmeetings was renamed to trade-group. After > fumbling around for a few hours. just putting in a "generic" > ProxyPass / http://localhost:5080/ > ProxyPassReverse / http://localhost:5080/ > I was able to get it to redirect and work which is odd. But it is up and > passing like it is supposed to. > > Next step to see about is there a way restrict access, unless it comes from > specific referrers xyz.com or zbc.com deny/redirect rest. But looks like that > may not be an option > > On 4/19/19 10:33 AM, Maxim Solodovnik wrote: > > In OM you have to set `secure` property, 404 is weird :( > I guess you have renamed `openmeetings` to be `trade-group`? > > On Fri, 19 Apr 2019 at 16:54, Aaron Hepp <aaron.h...@gmail.com> wrote: > > 4.0.8 > > Few more attempts it is now redirecting but its now pulling a 404 error > The requested URL /trade-group was not found on this server. > > ### OpenMeetings ### > ## Custom fragment > RewriteEngine On > RewriteCond %{HTTP:Connection} Upgrade [NC] > RewriteCond %{HTTP:Upgrade} websocket [NC] > RewriteRule /(.*) ws://localhost:5080/$1 [P,L] > RedirectMatch ^/$ https://traderoom.amhcapitalgroup.com/trade-group > ProxyPreserveHost On > > Since apache2 is talking to tomcat over 5080 there is no other modification > you need to do inside the OM instance > > > On 4/18/19 11:05 PM, Maxim Solodovnik wrote: > > What version of OM do you have? > > On Fri, 19 Apr 2019 at 09:12, Aaron Hepp <aaron.h...@gmail.com> wrote: > > so looks like the errors were cause by proxy_module had not loaded. So I > loaded the need module (list of modules talked about in the article) > > root@traderoom:~# sudo apache2ctl -M > Loaded Modules: > proxy_module (shared) > proxy_http_module (shared) > proxy_wstunnel_module (shared) > rewrite_module (shared) > > And now no errors when running configtest. But also does not look like it is > doing any redirection. you go to the page and you just get the default > apache page. Never does forward you into the OM install. > > You can access it if you go straight to it using :5080, so looks like I'm > missing a step somewhere > > > > On 4/18/19 8:37 PM, Maxim Solodovnik wrote: > > I would recommend to check this answer: > https://stackoverflow.com/questions/51721771/apache-openmeetings-4-0-4-csrf-attack-when-using-apache2-as-proxypass > > On Fri, 19 Apr 2019 at 05:21, Aaron Hepp <aaron.h...@gmail.com> wrote: > > Finally putting an Apache front end on this install and was following the > directions on DO for this > > https://www.digitalocean.com/community/tutorials/how-to-encrypt-tomcat-8-connections-with-apache-or-nginx-on-ubuntu-16-04 > > They use mod_jk module to connect Apache to Tomcat. In their documentation > it has a setting for where the Tomcat home directory is located. > > Inside, find the workers.tomcat_home directive. Set this to your Tomcat > installation home directory. For our Tomcat installation, that would be > /opt/tomcat: > /etc/libapache2-mod-jk/workers.properties > > workers.tomcat_home=/opt/tomcat (their example) > > > In an OM4 install where is that home directory located? > > I pointed it to /opt/om4 (my directory name) as well as /opt/om4/conf as well > as /opt/om4/webapps but none of these seem > to work. Am I missing something here? > > > > > > > > > -- WBR Maxim aka solomax
