SuiteCrm 8.7.x installation failure

SuiteCrm 8.7.x installation failure

An error message “LBL_ACTION_ERROR” appears during the first installation

Other notes: I successfully installed version 7.14 on this Linux server. If there is any difference in the installation logic between version 7.14 and version 8.7.x, will it cause the installation of 8.7.x to fail?

The log feedback I got is:
Mon Dec 30 11:15:39 2024 [3602][1][SECURITY] OutboundEmail::checkSavePermissions - not logged in - skipping check
Mon Dec 30 11:15:39 2024 [3602][1][FATAL] User update error: Temp User is not retrieved at ID 1, boolean given
Mon Dec 30 11:15:39 2024 [3602][1][FATAL] Email address save error
Mon Dec 30 11:15:43 2024 [3602][1][SECURITY] Invalid ext logger_file_ext : ‘’.
Mon Dec 30 11:15:43 2024 [3602][1][SECURITY] Setting logger_file_ext to ‘.log’.
Mon Dec 30 11:15:43 2024 [3602][1][SECURITY] Setting logger_file_name to ‘’.
Mon Dec 30 11:15:43 2024 [3602][1][SECURITY] Log file extension can’t be blank.
Mon Dec 30 11:25:34 2024 [3606][-none-][FATAL] Mysqli_query failed.

Operating environment: php8.1 mysql5.7 nginx1.18 CentOS 7.9

permissions:
find /www/wwwroot/xx/SuiteCRM_New -type d -not -perm 2755 -exec chmod 2775 {} ;
find /www/wwwroot/xx/SuiteCRM_New -type f -not -perm 0644 -exec chmod 0664 {} ;
sudo find /www/wwwroot/xx/SuiteCRM_New ! -user www -exec chown www:www {} ;
chmod +x bin/console

1 Like

Hi @Scott5
I followed this video tutorial for the installation, which provides a step-by-step guide. You can check it out here: Installation Video. It might help resolve the issues you’re facing.

@Scott5 are you sure that your web server is running under a user called www?

Hello Scott,

Suite7 is very different in tech / installation from Suite8.
I tend to prefer Apache over NGINX since I had more issues with NGINX - mostly php / fpm routes and rewrite issues.

Usually, if the error label appears early / during & right after installation, I’d stop and restart with the server / webserver setup.

  • Do you have all modules loaded?
  • How do permissions look like?
  • Is rewrite working properly?

And then wipe the CRM folder & DB clean and retry.

I have solved it,

location / {
# try to serve file directly, fallback to index.php
try_files $uri /index.php$is_args$args;

    # optionally disable falling back to PHP script for the asset directories;
    # nginx will return a 404 error when files are not found instead of passing the
    # request to Symfony (improves performance but Symfony's 404 page is not displayed)
    # location /bundles {
    #     try_files $uri =404;
    # }

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

        fastcgi_split_path_info ^(.+\.php)(/.*)$;
        include fastcgi_params;
        fastcgi_pass unix:/tmp/php-cgi-81.sock;
        fastcgi_intercept_errors on;
        fastcgi_temp_file_write_size 10m;
        fastcgi_busy_buffers_size    512k;
        fastcgi_buffer_size          512k;
        fastcgi_buffers           16 512k;
        fastcgi_read_timeout 1200;
        fastcgi_param HTTP_AUTHORIZATION $http_authorization;

        # optionally set the value of the environment variables used in the application
        # fastcgi_param APP_ENV prod;
        # fastcgi_param APP_SECRET <app-secret-id>;
        # fastcgi_param DATABASE_URL "mysql://db_user:db_pass@host:3306/db_name";

        # When you are using symlinks to link the document root to the
        # current version of your application, you should pass the real
        # application path instead of the path to the symlink to PHP
        # FPM.
        # Otherwise, PHP's OPcache may not properly detect changes to
        # your PHP files (see https://github.com/zendtech/ZendOptimizerPlus/issues/126
        # for more information).
        fastcgi_param SCRIPT_FILENAME $realpath_root$fastcgi_script_name;
        fastcgi_param DOCUMENT_ROOT $realpath_root;
        # Prevents URIs that include the front controller. This will 404:
        # http://domain.tld/index.php/some-path
        # Remove the internal directive to allow URIs like this
        internal;

    }

    # return 404 for all other php files not matching the front controller
    # this prevents access to other php files you don't want to be accessible.
    location ~ \.(php|key|log)$ {
        return 404;
    }
}

location ^~ /legacy/ {
    try_files $uri $uri/ /index.php?$args;
    location ~ \.(php|key|log)$ {
        try_files $uri =404;
        fastcgi_split_path_info ^(.+\.php)(/.*)$;
        include fastcgi_params;
        fastcgi_pass unix:/tmp/php-cgi-81.sock;
        fastcgi_param SCRIPT_FILENAME $realpath_root$fastcgi_script_name;
        fastcgi_param DOCUMENT_ROOT $realpath_root;
    }
}

location ~ /Api/(?!(graphql)) {
    # alias /var/www/html/local.newcrm.com/public/legacy; # !important
    alias /www/wwwroot/ClientWeb/SuiteCRM_New/public/legacy; # !important
    try_files $uri @rewrite_api;
    location ~ .php {
        fastcgi_split_path_info ^(.+\.php)(/.*)$;
        include fastcgi_params;
        fastcgi_pass unix:/tmp/php-cgi-81.sock;
        fastcgi_param SCRIPT_FILENAME $realpath_root$fastcgi_script_name;
        fastcgi_param DOCUMENT_ROOT $realpath_root;
    }
}

location @rewrite_api {
    rewrite ^/Api/(.*)?$ /Api/index.php/$1 last;
}
1 Like

@Scott5 wait, what file did you update and what code?

I have same log error, when I am trying to install add-on on the SuiteCRM 7.13

I have never encountered any errors in SuiteCRM 7.13. I think it is probably because your permissions are not configured properly and the cache is cleaned.