Pre installation requirement shows rout access check warning

Hello [magussilikonski], did you find a solution? Same situation here (plesk). Fresh install of v8.8 under PHP 8.3.21

I doubleckecked filerights, owners/groups, compatibility matrix, Php modules, etc.

Apache2 webroot is httpdocs/crm/public but when i click on ā€œIGNORE WARNINGS AND PROCEEDā€ (with the curl erros (ā€œCurl Request on Main Page:ā€ and ā€œCurl Request on Apiā€ ) like above)

it points to /legacy/public/install.php#/install? Is ā€œpublicā€ wrong here? I’m very thankful for Ideas!

Ensure PHP’s curl module exists:

php -m | grep curl

You need to check .htacess hidden file in the below folder location:
Make sure you have correct rewrite base.

httpdocs/crm/public/legacy/

You need to restart apache2 server after the changes.

Let us know!

Thanks for your suggestions. There is no htaccess in the legacy folder (only in the public folder) and curl is installed (7.81.0) and enabled. I added a basic auth in the .htaccess in the public folder but it doesn’t matter if is active or commented out.

The thing is, I had a working 8.6 (with PHP 8.1) version to play/test with it. on the same server. Then I cleared the vhost and made it fresh. Unfortunately I’m running out of ideas.

I’ve made a quick test install on a shared host V8.8 (with PHP 8.3). At least this install step worked…

That’s weird! It is an hidden file.

.htaccess

Maybe you need to use this command:

ls -a

It will have this line:

RewriteBase /legacy

Check if you have that file in v8.8 and maybe you could copy code from it.

ChatGPT gave me the solution.

Several things could be the problem for Error 500:

  1. I had NGINX and Apache running. ā€œThis strongly suggests that Plesk has NGINX enabled as a reverse proxy and NGINX is returning the 500 error, not Apache directly. This is a very common pitfall with Symfony/SuiteCRM.ā€

Solution: in Plesk: Domain > Apache & nginx settings under ā€œNGINXā€:

Uncheck ā€œUse NGINX as reverse proxyā€.

or configure NGINX correctly:

Domain > Apache & nginx settings > Additional NGINX instructions:

location / {

try_files $uri /index.php$is_args$args;

}

location ~ ^/index.php(/|$) {

fastcgi_pass unix:/var/run/php/php8.3-fpm.sock;

fastcgi_split_path_info ^(.+.php)(/.*)$;

include fastcgi_params;

fastcgi_param SCRIPT_FILENAME $realpath_root$fastcgi_script_name;

fastcgi_param DOCUMENT_ROOT $realpath_root;

internal;

}

Also enter APP_DEBUG=1 in the .env in the root directory so that you can see Symfony error messages.

My problem: PHP open_basedir blocks access to session directory

Warning: is_dir(): open_basedir restriction in effect. File(/var/lib/php/sessions) is not within the allowed path(s): (/var/www/vhosts/dir/:/tmp/)

means: PHP tries to save session data in /var/lib/php/sessions. However, this is not allowed because open_basedir prohibits access to other paths outside your vhost. This causes Symfony/SuiteCRM to fail to start - → 500 Internal Server Error.

I have in Plesk under Domains > your-domain.com > PHP settings

at open_basedir: /var/www/vhosts/deine-domain.de/:/tmp/:/var/lib/php/sessions and restarted apache.

Then it worked.

1 Like

Hello Using Windows 11, Apache 2.4, MySQL, and localhost:9090, I am attempting to install SuiteCRM-8.9.1. I’m receiving two different kinds of Route Access Check alerts.

Curl Request on Main Page:

  • The SuiteCRM Title cannot be found. This is not a valid SuiteCRM Page.

  • The url used for the call was: http://localhost:9090/

  • The result of the call was:

  • It works!

Curl Request on Api:

  • The result of the curl call to the graphql page was empty.

  • The url used for the call was: http://localhost:9090/api/graphql

  • The result of the call was:

  • 404 Not Found

    Not Found

    The requested URL was not found on this server.

I am unable to continue. Please help me figure out how to remedy this. I appreciate your assistance.

– Muthu

Hello Muthuvel,

don’t try to get Suite 8.x running on Windows:

Here, I’d always assume, that it won’t work.

As for the host and port:
Best to setup a subdomain instead of just using the standard. Without a subdomain, one could run into additional issues.

Not found issue: After setting up your Linux server, make sure that you have all modules and details in place for your webserver / PHP: