Thread: [mod-security-users] Modsecurity Reverse proxy
Brought to you by:
victorhora,
zimmerletw
Menu
▾
▴
mod-security-users
|
From: Monah B. <mon...@gm...> - 2019-04-01 00:37:35
|
Hi all, I have 2 servers running on AWS, server one has Apache/Modsecurity and server two running Apache only which also is our www domain server. I modified our DNS entry at our registrar to point our www IP address to server one, and on server one I added the following: ProxyPass "/" "http://www.<domain.com>" ProxyPassReverse "/" "http://www.<domain.com>" I get a This site can’t be reached when accessing the website on my browser. Thanks |
|
From: Manuel S. <spa...@gm...> - 2019-04-01 01:58:18
|
Hi Baki, You need to provide more info and context, can you provide the apache error log related to this and the logs on the other server. This issue can have multiple causes, depending on what the other server is expecting, for example proxypreservehost may cause this issue if you are getting to the wrong vhost http://httpd.apache.org/docs/2.4/mod/mod_proxy.html#proxypreservehost Cheers! Sent from my iPhone > On 31 Mar 2019, at 20:37, Monah Baki <mon...@gm...> wrote: > > Hi all, > > I have 2 servers running on AWS, server one has Apache/Modsecurity and server two running Apache only which also is our www domain server. > > I modified our DNS entry at our registrar to point our www IP address to server one, and on server one I added the following: > > ProxyPass "/" "http://www.<domain.com>" > ProxyPassReverse "/" "http://www.<domain.com>" > > I get a This site can’t be reached when accessing the website on my browser. > > Thanks > _______________________________________________ > mod-security-users mailing list > mod...@li... > https://lists.sourceforge.net/lists/listinfo/mod-security-users > Commercial ModSecurity Rules and Support from Trustwave's SpiderLabs: > http://www.modsecurity.org/projects/commercial/rules/ > http://www.modsecurity.org/projects/commercial/support/ |
|
From: Monah B. <mon...@gm...> - 2019-04-01 02:10:33
|
Hi Manuel, Both servers do not fire any alerts in error_log On Sun, Mar 31, 2019 at 10:02 PM Manuel Spartan <spa...@gm...> wrote: > Hi Baki, > > You need to provide more info and context, can you provide the apache > error log related to this and the logs on the other server. > > This issue can have multiple causes, depending on what the other server is > expecting, for example proxypreservehost may cause this issue if you are > getting to the wrong vhost > http://httpd.apache.org/docs/2.4/mod/mod_proxy.html#proxypreservehost > > Cheers! > Sent from my iPhone > > On 31 Mar 2019, at 20:37, Monah Baki <mon...@gm...> wrote: > > Hi all, > > I have 2 servers running on AWS, server one has Apache/Modsecurity and > server two running Apache only which also is our www domain server. > > I modified our DNS entry at our registrar to point our www IP address to > server one, and on server one I added the following: > > ProxyPass "/" "http://www.<domain.com>" > ProxyPassReverse "/" "http://www.<domain.com>" > > I get a This site can’t be reached when accessing the website on my > browser. > > Thanks > > _______________________________________________ > mod-security-users mailing list > mod...@li... > https://lists.sourceforge.net/lists/listinfo/mod-security-users > Commercial ModSecurity Rules and Support from Trustwave's SpiderLabs: > http://www.modsecurity.org/projects/commercial/rules/ > http://www.modsecurity.org/projects/commercial/support/ > > _______________________________________________ > mod-security-users mailing list > mod...@li... > https://lists.sourceforge.net/lists/listinfo/mod-security-users > Commercial ModSecurity Rules and Support from Trustwave's SpiderLabs: > http://www.modsecurity.org/projects/commercial/rules/ > http://www.modsecurity.org/projects/commercial/support/ > |
|
From: Monah B. <mon...@gm...> - 2019-04-01 11:42:38
|
Hi Manuel, It was a simple fix, all I had to do was change to: ProxyPreserveHost On ProxyPass / http://54.156.228.101/ ProxyPassReverse / http://54.156.228.101/ Guess it needed the IP rather then the FQDN Thanks On Sun, Mar 31, 2019 at 10:02 PM Manuel Spartan <spa...@gm...> wrote: > Hi Baki, > > You need to provide more info and context, can you provide the apache > error log related to this and the logs on the other server. > > This issue can have multiple causes, depending on what the other server is > expecting, for example proxypreservehost may cause this issue if you are > getting to the wrong vhost > http://httpd.apache.org/docs/2.4/mod/mod_proxy.html#proxypreservehost > > Cheers! > Sent from my iPhone > > On 31 Mar 2019, at 20:37, Monah Baki <mon...@gm...> wrote: > > Hi all, > > I have 2 servers running on AWS, server one has Apache/Modsecurity and > server two running Apache only which also is our www domain server. > > I modified our DNS entry at our registrar to point our www IP address to > server one, and on server one I added the following: > > ProxyPass "/" "http://www.<domain.com>" > ProxyPassReverse "/" "http://www.<domain.com>" > > I get a This site can’t be reached when accessing the website on my > browser. > > Thanks > > _______________________________________________ > mod-security-users mailing list > mod...@li... > https://lists.sourceforge.net/lists/listinfo/mod-security-users > Commercial ModSecurity Rules and Support from Trustwave's SpiderLabs: > http://www.modsecurity.org/projects/commercial/rules/ > http://www.modsecurity.org/projects/commercial/support/ > > _______________________________________________ > mod-security-users mailing list > mod...@li... > https://lists.sourceforge.net/lists/listinfo/mod-security-users > Commercial ModSecurity Rules and Support from Trustwave's SpiderLabs: > http://www.modsecurity.org/projects/commercial/rules/ > http://www.modsecurity.org/projects/commercial/support/ > |
Thanks for helping keep SourceForge clean.
X