• 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.

URLScan Blocking Plesk Images

G

GarretMott

Guest
Hi -

I freely admit to knowing little about Plesk. Bit more about IIS, but I digress.

We have a site where we've enabled URLScan (from MS) as a global filter - to keep PCI folks happier.

Problem is, URLScan is blocking any URL with a colon, so https://localahost:8443 (the shortcut to run Plesk) has issues with getting any images, so - while Plesk will run - it's got about the ugliest interface I've ever see & is largely unusable.

I have tried adding //localhost:8443 to AlwaysAllowedURLs in URLScan.ini, but no joy.

Has anyone configured URLScan to allow Plesk to be happy - or does anyone know of another way to run Plesk so it comes up as it should?

Many thanks -

Garret
 
Back
Top