Absolute Nightmare Upgrading SuiteCRM

📦 Install & Upgrade Help
1

Hi, I’m trying to upgrade my SuiteCRM but I have had an absolute nightmare with Robo.

I have tried ./vendor/bin/robo upgrade:suite SuiteCRM-Upgrade-7.12.x-to-7.14.6.zip upgradeLog.log /home/admin/public_html/suitecrm . admin but I either get permission denied or that the command isn’t found.

I have tried in an Ubuntu v22 server with root access and on a cPanel server (running Cloud Linux) but I am getting precisely nowhere and it’s driving me up the wall.

Uploading the upgrade patch throws a 403 not authorised on both servers. I’ve ensured that the advanced settings limits are high enough and that the php values are high enough to entertain a 38mb upgrade package.

Any ideas please?

Thanks

2

For version 7 use the GUI upgrade in Admin. It works very well.

It does all the steps for you. Checks permissions, etc, etc.

Is there some reason you’re not using this?

(Also make sure you are using the upgrade file and not the 7.14.6zip, I’ve done this myself on several occassions wondering why it wasn’t working)

3

Hi and thanks for taking the time to reply. So i’ve used an upgrade patch - two to be precise. On one server i’m getting a 403 error thrown at me (Cloud Linux/cPanel with no root access) on the other i’m getting a 500 error (Ubuntu 22.04 and DirectAdmin with my own root access).

I can’t find anything meaningful in logs and I have ensured that values are hugh enough in settings → advanced settings and in PHP settings for the server.

I have ensured that permissions are correct too - at least as far as chmod - i’m not sure how to make sure owners/groups are right or what files/directories that I should be checking?

I have recently changed server/hosting account names- i’m not sure if there is anything beyond db user, dbname and password to change?

I have tried turning on Suite CRM debug but again, nothing that I can see but I am dyslexic and it doesn’t space out problems.

The 403/500 is being thrown after about 4 minutes whilst the patch is being uploaded. I tried a big patch (38mb) which is a valid upgrade route patch from my version further into the future and a patch to the next version from what i’m on which should be less taxing. Both had the same issue.

I suspect that I need to start on one version of PHP and as the upgrade happens to move forward a version to fulfill PHP version requirements - the version I am on will run, I think PHP 7.4 at max. I’m sure more modern versions will require a higher PHP version. This is one of the compelling reasons to upgrade - security but i’m not sure if the necessity to increase PHP Version as I gradually get more and more uptodate will be getting in the way.

I went to hosting support for the cPanel server- they couldnt find anything of note for the cPanel server - i’ve also tried this on a server where I have root access (I got 500 there).

I could not get composer to play ball for love nor money as, in cPanel terminal it said it couldn’t find the autoloader, told me to install composer, I did this and got can’t find the auto loader and to install composer again. I did the --nodev command that they recommended too.

On my root access server, it couldnt find the robo directory even though it exists within the path where it says it doesn’t.

With the upgrade from terminal route - I noticed that the suggested command versus the instructions above
/below do not match and have a different order - one suggests a period before the SuiteCRM username, above/below it suggests not using a period so I found this confusing and wondered if the command format is correct at all.

I did delete the temp file from cache as recommended on other threads and in between upgrade attempts.

I did run built in repairs including a .htaccess rebuild.

Thanks.

4

Ok for 500 errors that you can’t otherwise explain, here is what I generally try first (and it fixes like 90% of the problems).

  1. Make sure BOTH your install directory and at the server level you have at least 512MB of memory… this could be a good thing to check since you changed hosting.
  2. Make sure you have all the proper PHP extensions activated (check the documentation)… this could be a good thing to check since you changed hosting.
  3. Re-set file permissions and ownership, again a good thing to do since you just changed hosting:
    sudo chmod -R 755 .

sudo chmod -R 775 cache custom modules themes data upload config_override.php

sudo chown -R www-data:www-data .

It may not be exactly this. You need to figure out who owns the files and how your server handles file ownership. For example I’m on Godaddy VPS and the convention is the account name:
Example:

chown -R myaccountname:myaccountname .

If these simple steps don’t fix it, there is a log specific for the install process that gives specific info if you use the GUI upgrade process.

5

Using the Upgrade Wizard

6

Thanks for this but the issue was that I couldn’t upload the patch within the upgrade wizard.

7

I have resolved this now - it turned out modsecurity was blocking me (at least in terms of uploading the patch in the upgrade wizard)! Thank you for your help everybody. As for why I couldn’t do a silent upgrade, I am none the wiser and I guess I will explore whether this is fixed in my transition to the latest version of V8.

8

Congratulation to figure it out! Are you planning to jump from 7.14 to 8.x version?

9

Interesting! That’s a new one for me. I have mod security installed on all my sites and never had this issue. Maybe you have more restrictive rules than the default. Good to know this may be an issue if I’m stuck and my upgrade isn’t working. One more thing to try.