Forums

Installation C5 Ver.8.5.2 fail during checking required items "Supports concrete5 request URLs"

Permalink
Dear guys,

I would like to instal C5 v.8.5.2 on my Centos 7 Linux Server.

I always receive the same error during the required items check:
Supports concrete5 request URLs - concrete5 cannot parse the PATH_INFO or ORIG_PATH_INFO information provided by your server.

I spent 3 days looking for some solution on your forum and on internet, without any success.

My .htaccess contains the following directives:
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{THE_REQUEST} \s(.+?)/+[?\s]
RewriteRule ^ %1 [R=302,L]
RewriteCond %{THE_REQUEST} /index\.php[\s?/] [NC]
RewriteRule ^(.*?)index\.php(/.*)?/?$ /$1$2 [L,R=301,NC,NE]
RewriteCond $1 !^(index\.php)
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ index.php?cURL=$1 [L,QSA]
</IfModule>


My phpinfo() returns:
--- cgi-fcgi ---
cgi.fix_pathinfo   1   1
--- PHP Variables ---
 $_SERVER['PATH_INFO']   /test
$_SERVER['SCRIPT_NAME']   /phpinfo.php
$_SERVER['REQUEST_URI']   /phpinfo.php/test


I cannot understand what fails the requirements check.
Please can you help me?
 
pilot222 replied on at Permalink Reply
I had exactly the same problem with CentOS 7 + Plesk
The solution was to have the following in my PHP settings


open_basedir {WEBSPACEROOT}{/}{:}{TMP}{/}{:}/var/lib/php/session

Good luck
pilot222 replied on at Permalink Reply
I had exactly the same problem with CentOS 7 + Plesk
The solution was to have the following in my PHP settings


open_basedir {WEBSPACEROOT}{/}{:}{TMP}{/}{:}/var/lib/php/session

Good luck
Myq replied on at Permalink Reply
Myq
Check the request in the browser's developer tools. It's possible that the server is responding with a 500 status due to something completely unrelated. Unfortunately, the error message on the front-end is exactly the same in this scenario, which can send you down the wrong path. There's an open pull request to fix this situation:https://github.com/concrete5/concrete5/pull/9504/files...

In my case, I had not configured my session storage directory correctly, so it was failing to create a session but it was not obvious without inspecting the actual request, status code, and the response in the browser's developer tools.

Another alternative is to install using the command line tool which will bypass this check (there are a few checks which are only performed when installing through a browser and this is one of them).