marenac

Okay then that should work. The only thing I can think of at this point is permission/ownership issues on the file or PHAR extensions is not installed/enabled for your PHP.

Cheers.

      KevinTheJedi

      PHAR extension is enable

      but there is some other error that I can't find.
      The error log report this:

      [proxy_fcgi:error] [pid 32397:tid 139768444716800] [client 93.**.**.**:0] AH01071: Got error 'PHP message: PHP Fatal error: Uncaught RuntimeException: is_file(): open_basedir restriction in effect. File(/home/------/web/------/public_html/include/plugins/storage-fs.phar/plugin.php) is not within the allowed path(s): (/home/------/.composer:/home/------/web/------/public_html:/home/------/web/------/private:/home/------/web/------/public_shtml:/home/------/tmp:/tmp:/var/www/html:/bin:/usr/bin:/usr/local/bin:/usr/share:/opt) in /home/------/web/------/public_html/include/class.plugin.php:257\nStack trace:\n#0 [internal function]: PluginManager::throwException()\n#1 /home/------/web/------/public_html/include/class.plugin.php(299): is_file()\n#2 /home/------/web/------/public_html/include/staff/plugin-add.inc.php(15): PluginManager::allInfos()\n#3 /home/------/web/------/public_html/scp/plugins.php(136): require('...')\n#4 {main}\n thrown in /home/------/web/------/public_html/include/class.plugin.php on line 257', referer: https://www.------/scp/plugins.php

          marenac

          Ahhh that’s why. Your host has some PHP restrictions which is preventing the plugins from being loaded. You’ll need to contact your hosting provider for further assistance.

          Cheers.

              KevinTheJedi
              I'm testing OsTicket on my own virtual server, but I haven't set any restrictions. In the same server I have installed the 1.16 version, and the plugins are loaded regularly.
              I don't understand why it wont work with 1.17

                  marenac
                  I don’t know what to tell you the error says PHP Fatal error: Uncaught RuntimeException: is_file(): open_basedir restriction in effect so you have some sort of PHP restrictions. Upon googling the error it appears you can update your php.ini to include open_basedir = none, restart PHP-FPM if you’re running it, restart your webserver and retry.

                  Cheers.

                      KevinTheJedi
                      Thank you for support, I have already try to include open_basedir = none on my php.ini but the problem still remain unsolved.
                      For now I got around the problem by installing the previous version 1.16 and activating the storage-fs.phar, and then I updated the installation to 1.17.

                      Cheers

                        a year later

                        The location of your error logs depends on your OS, webserver software, and versions.

                        For Apache
                        consult your httpd.conf or apache2.conf

                        For PHP
                        You could create a temp.php and in it put
                        <?php phpinfo(); ?>
                        and then browse to it, and it should display a listing of tyour PHP's configuration.
                        Which includes the error_log location for PHP.

                        For IIS you would look in your IIS Management panel to see where the logs are and open them.

                        10 months later

                        Using osTicket v1.18.1 instance on Debian GNU/Linux 12 (Stable) with Apache2 and PHP 8.2.26
                        I've achieved to enable plugins only by setting this directive temporarily in virtualhost:
                        php_admin_value open_basedir none
                        After enabling them, I could restore secure open_basedir and osTicket works well with plugins.
                        php_admin_value open_basedir /srv/www/mysite.net/

                        THEN I think something is wrong in osTicket around this; Normal server with normal securities (such as open_basedir restricted to website's directory) should be fine for this CMS. I run other software perfectly there without this problem (Wordpress, private MediaWiki, Moodle, etc.) and all of them with private and public file referencing.
                        .phar files seem to be closed-source software because they are in a compiled form.
                        What do they need from my entire filesystem??

                        Bad policy to system administrators trust to this software.

                        Write a Reply...