Marketplace error when upgrading Concrete to newest version

I’ve just tried upgrading a local installation of Concrete V9.2.6 to the latest (9.3.2) and get a “Curl error 60” (full screenshot attached) when viewing the “update concrete” page in the Dashboard. Anyone else getting this as well?


The upgrade seemed to work after that.

Many sites I have updated have not been connected to the marketplace. As the issue appears to be related to the MP connection with the old marketplace, perhaps disconnecting from the marketplace would allow the update to complete.

This error occurred before running the update. The site had not been connected to the marketplace until that point.
After the upgrade completed, I tried connecting to the new marketplace for the first time and it worked.

I´m in the same sh… tested CURL from outside, and it is running smoothly…
Any one knowing any thing ?

I haven’t received any feedback from the core team, so no idea unfortunately.

@jb1 thanks for bringing this up and apologies for the delay. I was away for holiday for a while, but actively investigating this now

@jb1 I have a work around for now.

Look in concrete/config/concrete.php around line 794 and you’ll see something like this:

    'updates' => [
        // ...
        'services' => [
            'get_available_updates' => 'https://marketplace.concretecms.com/tools/update_core',
            'inspect_update' => 'https://marketplace.concretecms.com/tools/inspect_update',
        ],
        // ...
    ],

Change those two endpoints to the following:

    'updates' => [
        // ...
        'services' => [
            'get_available_updates' => 'https://www.concretecms.com/api/remote_update/update_core',
            'inspect_update' => 'https://www.concretecms.com/api/remote_update/inspect_update',
        ],
        // ...
    ],

I’m working on getting the server to redirect those endpoints correctly, but if you can’t wait for that, the above should work.

@jb1 @christensenagency I believe that should be redirecting correctly now. Could you try again and let me know if you are still experiencing any issues?

Thanks for the update. It looks like the original error no longer occurs when trying to run the core update. The changes to the “/dashboard/system/update/” page definitely make it easier to see what has changed. It would be super useful to display under the new version numbers the date it was released. It will give a better sense of progression and let users know what they’ve missed in between updates.

I’ve noticed 2 other issues now relating to the update routine:

  1. Older versions of Concrete (I’m running 9.2.6 on one install) only provide upgrades 1 point at a time (to 9.2.7 and then 9.2.8) - not a single jump to the newest version (9.3.3 in this case). That means multiple downloads and running the update routine multiple times (with a little downtime for users each time). Did I miss something, or shouldn’t that be just a single upgrade to the newest available version?

  1. While I was able to run an update ok one one installation (running 9.2.x), another install (running 9.3.2) says that the upgrade folder (for 9.3.3) already exists when it doesn’t.


Any ideas why?

Nope…

And also the code you mention looks the same as your suggestion.

In your updates/concrete-cms-9.3.2 folder find the concrete/controllers/single_page/dashboard/system/update/update.php file and make the changes as seen in this image.

Thanks for the tips. I modified that file and tried running the update again and it worked as expected. Thank you! Here’s a screenshot for anyone else following along.

1 Like

Okay, the updates should be able to jump to the latest version now, avoiding the problematic 9.3.1 version (which gives the error about the directory already existing when upgrading to 9.3.2).

Below is an example of upgrading from 9.2.6 directly to 9.3.3

Let me know if you run into any issues!

@christensenagency can you try again with the changes to the server that went out today?

Awesome! Looks great, thank you :pray:

I have no change, still unable to connect, get this message:
Error establishing connection to the Concrete community. Please check that curl and other required libraries are enabled.
But curl is running fine.

Found a way to jump to 9.3.3 All is now working as expected!
Thanks.

1 Like

@christensenagency I think this is a different issue. Connecting to the community is now only supported in Concrete 9.3+. Older versions report that error because that was typically the cause when having issues connecting to the older marketplace.