Hello Franklin,
There is very little information about ModSec on IIS. From the scarce number
of questions we are getting about it here and from what I can tell after 15
years of consulting around ModSecurity, this is a road rarely travelled.
So I reckon you are mostly on your own.
The easier approach would probably be to put an Apache in front of the IIS.
Possibly on the same machine. This adds another system to the setup, but
it is known to work on Windows and no annoying surprises.
Just my 2 cents.
Christian
On Wed, Apr 27, 2022 at 03:44:26PM +0800, Franklin Weng wrote:
> Hi,
>
>
> A problem has bothered us for several weeks and would like to get help here.
>
> We installed a fresh Windows 2019 (Datacenter) server with a whole new IIS
> server. Then we installed ModSecurity 2.9.5 WIndows version. It was
> installed successfully. The installer file was downloaded from
> https://sourceforge.net/projects/modsecurity.mirror/files/v2.9.5/
>
> But when we tried to connect to http://localhost what we got is 503 error.
> And the log in IIS showed "Can not load
> C:\Windows\System32\inetsrv\ModSecurityIIS.dll, data is the error"
> (translated back from Chinese).
>
> We tried to installed 64 bit only which seemed to work (at least no 503
> error), but the test rule we set did not work. No logs were generated
> either.
>
> We've searched plenty of pages on Internet, including github issues, but no
> luck.
>
> Any help would be appreciated. If you need more info feel free to tell me.
>
>
> Thanks, Franklin
> _______________________________________________
> 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/
|