• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue IIS Rewrite Rules affecting Git repositories

TullariS

New Pleskian
Server operating system version
Windows Server 2022
Plesk version and microupdate number
18.0.68
Hi,
I have been having issues accessing Git repos hosted on Plesk (clone, push, pull, etc.). After much digging I realised that the Laravel Toolkit extension IIS rewrite rules were affecting the plesk-git application on IIS - rules are inherited from parent application.

It is an easy fix - on the plesk-git web.config file, add <clear /> inside the <rules> element, before the plesk-git <rule>:

XML:
<?xml version="1.0" encoding="UTF-8"?>
<configuration>
    <system.webServer>
        <rewrite>
            <rules>
                <clear/>
                <rule name="plesk-git" stopProcessing="true">
                    <match url="(^[^/]*)[^\?]*" />
                    <serverVariables>
                        <set name="PATH_INFO" value="/{R:0}" />
                    </serverVariables>
                    <action type="Rewrite" url="/plesk-git/{R:1}" />
                </rule>
            </rules>
        </rewrite>
    </system.webServer>
</configuration>

I have done it on my end and it solves it. Unfortunately this will be reverted on following updates.

Can I ask you include this change in the extension please?

Thank you.
 
Hello, @TullariS . Thank you for the input. Could you please provide us with more details on what issues you have experienced and step-by-steps introductions on how we can replicate those? Thank you in advance for your cooperation.
 
Hi,

Whenever I tried to do a push or a clone of a Plesk-hosted Git repo, I would get HTTP 403 errors.

Checking IIS Rewrite rules for the plesk-git Application within the domain we see:
1745019796224.png

You can see 4 inherited rules from the Domain - 2 from Plesk itself and 2 from the Laravel Toolkit extension. These are applied before the last one, which is the rule that really matters.

As, in my view, the rules set for the domain should not be used for plesk-git, which is its own application, so I added the <clear /> to the plesk-git web.config file. Rules on IIS are now:
1745020273954.png

Cloning the repo now works.

I suppose if you want to replicate it:
  1. Create a domain with a Laravel application and make sure the Laravel Toolkit extension is enabled and recognises the domain
  2. (optionally, I believe) enable non-www and HTTPS redirects
  3. Create a local Git repo on the site
  4. Attempt to push some code to it
Hope this helps.
 
Back
Top