• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Global ISAPI Filters do not work with Plesk

M

mtwalsh

Guest
Hi,

I've noticed an issue with Plesk whereby global level ISAPI filters simply do not work.

I've tried installing ISAPI Rewrite 3 and also IIS Password at the global level in IIS and neither will function.

When I add the filters to an individual website in IIS they suddenly spring into life.

Is there any way to get these ISAPI filters working at a global level?

I'm certain this is a Plesk issue rather than the fault of the individual ISAPI filters as I have them running at a global level on another server which doesn't have Plesk.

Thanks for looking.
 
Many thanks for the reply but I have seen that post before and it doesn't solve my problem.

It seems strange that ISAPI Rewrite works at the site level and not at the global level.

I have it set-up and working on another server at the global level but with Plesk 8.2.0 so it might be something isolated to 8.6.
 
It seems strange that ISAPI Rewrite works at the site level and not at the global level.

I have it set-up and working on another server at the global level but with Plesk 8.2.0 so it might be something isolated to 8.6.

Same exact problem here in plesk 8.6..
The problem is worse when you have 300+ websites and after loading MAUNALLY the filter
you have to reconfigure them all with websrvmng --reconfigure-all .... :(
 
Make sure your permissions on the filter itself are such that the account/service that is accessing the filter for the web site has enough permissions to execute the ISAPI filter. I have seen before where the permissions were preventing access.
 
Back
Top