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?
