httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From gkk gb <modjkl...@comcast.net>
Subject Re: [users@httpd] How to convert mod_jk to mod_proxy_ajp on CentOS?
Date Sun, 03 Nov 2019 16:58:04 GMT
I realize the reason httpd didn't restart is because EasyApache automatically inserts listens
to port 0.0.0.0:80 and 0.0.0.0:443, so including additional listens in the Pre Main Include
section causes Apache not to start (can't use more than one listen for the same port in httpd.conf).

Everything seems to work fine using the default ports above. However, I'm not sure if 0.0.0.0
is achieving the same thing (e.g. as efficient) as 192.168.0.2. So, I tried to use WHM's Tweak
Settings, System panel to change EasyApache's default ports to 192.168.0.2:80 and 192.168.0.2:443
(respectively). If I then stop and start httpd, the webpages no longer load.

Can anyone explain why listening on these ports no longer works, when it used to before EasyApache
4?

> On November 2, 2019 at 4:28 PM gkk gb <modjklist@comcast.net> wrote:
> 
>     I was able to get things to work with 1 remaining issue.
> 
>     First, installed mod_proxy_ajp. Then, I modified the server.xml file to include:
> 
>     <Connector port="8009" enableLookups="false" protocol="AJP/1.3" redirectPort="8443"
URIEncoding="UTF-8"/>
> 
>     Then, I commented out all the previous mod_jk configuration settings in the Pre Main
Include in httpd.conf file, and inserted the following:
> 
>     ProxyPassMatch ^/(nameOfMyApp)(.*) ajp://localhost:8009/$1$2 ttl=120 ping=1
> 
>     Restarting Tomcat and Apache gave successful results. However, I previously also
had the following 2 lines of code inside the include file:
> 
>     # Ensure Apache will listen on the local IP address for the cross-over cable:
>     Listen 192.168.0.2:80
>     Listen 192.168.0.2:443
> 
>     To make things work, I had to comment these 2 lines out, otherwise Apache would not
start. My application and database servers sit next to each other in the datacenter, connected
by a cross-connect cable, so that their traffic doesn't need to cross the world to find each
other through the Internet. Anyone know why this gets broken going to EasyApache 4, and how
to resolve?
> 
> 
>         > > On November 2, 2019 at 2:06 PM gkk gb <modjklist@comcast.net>
wrote:
> > 
> >         I had a CentOS 7.7 with Tomcat 8.5.9 and mod_jk working fine, but after
updating to the latest Cpanel, which required installing EasyApache 4, mod_jk no longer works
(appears it is not compatible with EasyApache 4).
> > 
> >         I believe my next best option (correct me if wrong) is installing mod_proxy_ajp.
Can someone summarize what I need to do to get mod_proxy_ajp installed and working in place
of mod_jk?
> > 
> >         I'm a newbie, so please be explicit.
> > 
> > 
> >     > 
>      
> 



Mime
View raw message