![]() Rewrite ^/api/(.*)$ /apirest.php/$1 last įastcgi_pass unix:/run/php/ Ssl_ciphers HIGH:!aNULL:!eNULL:!EXPORT:!CAMELLIA:!DES:!MD5:!PSK:!RC4 Īdd_header Expect-CT "enforce, max-age=300, report-uri=''" Īdd_header X-Content-Type-Options nosniff Īdd_header X-XSS-Protection "1 mode=block" Īdd_header Strict-Transport-Security "max-age=31536000 includeSubDomains preload" Ssl_session_cache builtin:1000 shared:SSL:10m I wonder why it is looking for the inc directory in public, since it is normally not there.įailed opening '/var/Įrror_log /var/log/nginx/.error.log Run "php bin/console dependencies install" in the glpi tree to fix this. Another attempt to open and.Īpplication dependencies are not up to date. I copied the bin directory from glpi to glpi/public. PHP Fatal error: Uncaught Error: Class 'Session' not found in /var/on line 59 ![]() ![]() PHP Warning: Use of undefined constant GLPI_CONFIG_DIR - assumed 'GLPI_CONFIG_DIR' (this will throw an Error in a future version of PHP) in /var/www/html/glpi/public/index.php on line 54 PHP Warning: include(): Failed opening '/var/in /var/www/html/glpi/public/index.php on line 51 Is /var/Are there other enabled vhosts? "sudo apachectl -S" can be used to show all enabled vhosts SSLCertificateKeyFile /etc/ssl/private/glpi.keyġ. SSLCertificateFile /etc/ssl/certs/glpi.crt Unnecessary? I disagree.ĬustomLog $/access.log combined If you spend enough time on the forums, you will see plenty of people just giving 777 rights on the GLPI folder (everyone can read, write and execute) leaving it very vulnerable.Įnforcing it so GLPI installations can only expose the "public" folder to the web helps ensure security even if someone messed up permissions on purpose or accidentally.Īdding a new vhost isn't complicated in general and there are multiple examples in the installation documentation now including how to make these changes in the ".htaccess" file rather than a vhost in cases where you may not be able to do so like on a hosted server.Ī headache? For some, yes. ![]() Just because you could just install WordPress without setting up a vhost, doesn't mean you should. But now you have to reconfigure the whole webserver. It was really simple to install it, just like WordPress. Yeah I think this change will generate a lot of unnecessary headache among the GLPI community. # Redirect all requests to GLPI router, unless file exists.Īpache starts, but the page doesn't open. The job identifier is 1337 and the job result is failed.Īpr 07 12:25:23 glpi sudo: pam_unix(sudo:session): session closed for user rootĪpr 07 12:26:01 glpi CRON: pam_unix(cron:session): session opened for user root by (uid=0)Īpr 07 12:26:01 glpi CRON: (root) CMD (/usr/bin/php7.4 /var/www/html/glpi/front/cron.php &>/dev/null) A start job for unit rvice has finished with a failure. Subject: A start job for unit rvice has failed The unit rvice has entered the 'failed' state with result 'exit-code'.Īpr 07 12:25:23 glpi systemd: Failed to start The Apache HTTP Server. I thought - nothing simpler, I'll add /var/www/glpi/public still don't udnerstand it I changed the configuration to not use but So my current DocumentRoot setting is /var/www/glpi According to this, one has to change the vhost config in apache as follows: Since the security requirement is added now but not mandatory until 10.1, the fact that 10.0 will be supported for a time after 10.1 is released, and this is just a one-time change that needs made by the web server administrators, there isn't any change from the end-user point of view.Īll previously saved URLs would still function.ġ0.1 would include bigger features or ones that could wait and may benefit from a beta period.ġ1.0 could conceivably be released at a time when there are major changes to GLPI from the end-user perspective like there was with the UI rework in 10.0.Īll right, I found the corresponding change in github. Allow using rules to add computers as VMs Such new features from the 10.0 versions included: I know this was put in the developer documentation, but this was discussed among the GLPI developers a few months ago and the majority opinion was to treat major and minor versions similarly to match the customer's point of view.įor bug-fix versions like 10.0.6 and 10.0.7, expect fixes, some smaller features/changes that don't break code compatibility for plugins, but no removed features.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |