Jump to content
thirty bees forum
  • 0

Can't import localization pack, cURL error 60


Question

Posted

When I try to import localization pack (local) I get following error message in 30b BO:

"2 errors

  1. Language pack cannot be downloaded from thirtybees.com.
  2. Downloading https://translations.thirtybees.com/packs/1.3.0/fa.json failed (PHP message: cURL error 60: SSL certificate problem: certificate has expired (see https://curl.haxx.se/libcurl/c/libcurl-errors.html))."

Please help to fix this.

 

P.S. Also maybe for the same reason when I hit "Check for updates" on the List of modules page it's always gives message "Everything is up-to-date", which can't always be true. Or maybe it's unrelated to the topic.

3 answers to this question

Recommended Posts

  • 0
Posted

Your thirty bees store has "trust store" file that contains root certificates of all trusted certification authorities. This file is outdated in 1.3.0, and does not contain new root certificate that Lets Encrypt uses nowadays. Which causes your store to not trust any servers that are using certificates issued by Let's Encrypt. Including thirty bees api server.

To fix this, all you need to do is update to latest thirty bees 1.4.0.

If you can't do that, then you will have to manually download the truststore file: https://raw.githubusercontent.com/thirtybees/thirtybees/main/tools/cacert.pem

and save it as /tools/cacert.pem inside your thirty bees installation. There should already be this file, you have to overwrite it.

  • 0
Posted

Regarding the first 2 questions @datakick will help as soon as possible.

Regarding the modules updates. In general in order to update your system you have to have permanently installed the following 2 modules:
1. thirty bees updater - to update the native modules (this function will be moved to core soon, but as of now this module should be installed in order to make the connection between your site and TB modules list). Not to be confused with migration modules which can be removed after you moved to thirty bees (if you did so). After you install it, there's no configuration page, just click on the button you already see (Check for update) and it will show the most recent versions of all native modules. In order to update 3rd party module you should follow the developer's instructions, but in most of the cases you can simply upload the new version and it will overwrite all files, db tables as needed.

2. Core Updater - to update the system to stable or edge releases, update the DB, etc. After you install it you can quickly access it from Preferences -> Core updater. The module is very powerful and stable and I advise to set your chanel to stable 1.4 as of now, update your files, then click on Database and update all rows there (yes, one by one, and don't be bothered by the dangerous message - just plow ahead, nothing wrong). With time when you set your shop and become more comfortable with it you can switch to edge channel here and apply the most recent updates as they come in.

 

Before all that, please make a working backup of your files and DB!!!
 

  • 0
Posted
1 hour ago, datakick said:

Your thirty bees store has "trust store" file that contains root certificates of all trusted certification authorities. This file is outdated in 1.3.0, and does not contain new root certificate that Lets Encrypt uses nowadays. Which causes your store to not trust any servers that are using certificates issued by Let's Encrypt. Including thirty bees api server.

To fix this, all you need to do is update to latest thirty bees 1.4.0.

If you can't do that, then you will have to manually download the truststore file: https://raw.githubusercontent.com/thirtybees/thirtybees/main/tools/cacert.pem

and save it as /tools/cacert.pem inside your thirty bees installation. There should already be this file, you have to overwrite it.

Thank you very much, this helped with importing language pack and updating modules as well.

Although, language packs import without country flags. TB version 1.3.

image.thumb.png.d136972e83f31dfcf30ae766750f9d5f.png

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...