bonjour tout le monde, j'ai suivi un tuto pour installer osticket sur IIS.
cependant a la fin j'ai ce message d'erreur

merci de m'iader s'il vous plait.

Please help us to help you by reading and following the posting guidelines located in this thread: Please read before requesting assistance. The more information you give us the better we will be able to assist you. Thank you.

Environment details?

  • Version of IIS?
  • version of PHP installed?
  • version of osTicket installing?

What tutorial did you follow?

merci pour votre reaction.

version of IIS

version of PHP

version of Osticket
osticket-v1.17.3

trainer

PHP 8.2 is not supported at this time. You need to downgrade to PHP 8.1 or 8.0 and retest.

Cheers.

    Hi,
    I had the same problem. I downgraded to 8.1 but stil didn´t work. The IIS doesn´t like the web.config file. A basic Web.config setup worked for me. This ist the config:

    I hope the Support would review their web.config file or tell us why it is not workinig. Because I couldn´t start neither 1.16.6, nor 1.17.3
    Here the config which was in the downloaded OsTicket.

      yivanov

      It’s working just fine for me and many others. You’d need to contact your server admin to see why it’s not working in your instance.

      Cheers.

        4 days later

        bonjour, merci pour vos retours.

        j'ai ramené la version du PHP a 7.4.33 cependant l'erreur persiste toujours.

        Bonjour Kevin,

        merci pour ton soutient.
        cependant j'ai pas compris ton dernier message.

        voici le contenu du fichier web.config d'osticket:
        <?xml version="1.0" encoding="UTF-8"?>
        <configuration>

        <system.webServer>
    <directoryBrowse enabled="true" />
    <rewrite>
        <rules>
            <rule name="HTTP api" stopProcessing="true">
                <match url="^(.*/)?api/(.*)$" ignoreCase="true"/>
                <conditions>
                    <add input="{REQUEST_FILENAME}" matchType="IsFile"
                        ignoreCase="false" negate="true" />
                    <add input="{REQUEST_FILENAME}" matchType="IsDirectory"
                        ignoreCase="false" negate="true" />
                </conditions>
                <action type="Rewrite" url="{R:1}api/http.php/{R:2}"/>
            </rule>
            <rule name="Site pages" stopProcessing="true">
                <match url="^(.*/)?pages/(.*)$" ignoreCase="true"/>
                <conditions>
                    <add input="{REQUEST_FILENAME}" matchType="IsFile"
                        ignoreCase="false" negate="true" />
                    <add input="{REQUEST_FILENAME}" matchType="IsDirectory"
                        ignoreCase="false" negate="true" />
                </conditions>
                <action type="Rewrite" url="{R:1}pages/index.php/{R:2}"/>
            </rule>
            <rule name="Staff applications" stopProcessing="true">
                <match url="^(.*/)?scp/apps/(.*)$" ignoreCase="true"/>
                <conditions>
                    <add input="{REQUEST_FILENAME}" matchType="IsFile"
                        ignoreCase="false" negate="true" />
                    <add input="{REQUEST_FILENAME}" matchType="IsDirectory"
                        ignoreCase="false" negate="true" />
                </conditions>
                <action type="Rewrite" url="{R:1}scp/apps/dispatcher.php/{R:2}"/>
            </rule>
        </rules>
    </rewrite>
    <defaultDocument>
        <files>
            <remove value="index.php" />
            <add value="index.php" />
        </files>
    </defaultDocument>
</system.webServer>

        </configuration>

          trainer

          As long as it matches the below you should be fine:

          If it still doesn't work then you need to contact your systems administrator to see why it's not working. It just says due to invalid config but there should be nothing invalid with it. This config has been working fine for years (still is working for me today). So there should be no issues with it.

          Cheers.

            11 days later
            Write a Reply...