Skip Navigation

[Resolved] cURL error 7: Failed to connect to api . toolset . com port 443:

This support ticket is created 6 years, 7 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- - 14:00 – 20:00 14:00 – 20:00 14:00 – 20:00 14:00 – 20:00 14:00 – 20:00
- - - - - - -

Supporter timezone: Asia/Ho_Chi_Minh (GMT+07:00)

This topic contains 7 replies, has 2 voices.

Last updated by Valeriia 6 years, 7 months ago.

Assisted by: Beda.

Author
Posts
#905490

Could not update to the last version. It says I need to register the plugin (although it was registered), and when I do, gives and error: cURL error 7: Failed to connect to api.toolset.com port 443: Connection timed out.

I deleted the site from the list of registered sites, but it didn't help.

Btw, lately I had to re-register all of the sites, but this is the first time I can't actually do it.

Please advise. Thanks.

#905496

I had no issues today updating unless one glitch in Toolset Types which was resolved as soon I re-tried.

I assume the easiest here would be to try once on your site directly with a code of ours, and if that brings no results, on a Duplicate.

Is it possible to gain both access and a copy of the site?https://toolset.com/faq/provide-supporters-copy-site/

#905577

Your PHP version 5.6 should not be an issue.
I am not sure the issue is related to this, and we should not present issues with PHP 5.6:
https://toolset.com/toolset-requirements/

Could you nonetheless submit me a copy of the site, so I could try this locally with the PHP 5.3 you used?
Maybe there is a glitch.

For the other issues please could you add new tickets?
- Custom Fields.
Here I see no created fields in your install. Did you create Fields during the Beta releases? Could you add as many steps you can recall to the new ticket so we can handle this as soon and effectively as possible?
- WooCommerce Views should not update but I see that you still use 2.7.6
Eventually, this issue can for now be solved by manually downloading the current release and uploading it to the FTP?
If this is not resolved after cache-purge, please can you as well open a new ticket for it?

#905594

Thanks.

The link for the duplicator package you already have.
For the database, the link is the same, the file name is "20180529_joolah_f1f3f2e4b8d044bd5735180529133032_database.sql".
Installer : "20180529_joolah_f1f3f2e4b8d044bd5735180529133032_installer.php?get=1&file=20180529_joolah_f1f3f2e4b8d044bd5735180529133032_installer.php"

If you need something else, let me know.

I'll create new tickets for the other things, thanks.

#906100

Thanks, I have escalated this and we will look into it.

#906147

Well, but this duplicate has the updated Plugins installed.

However, I replaced the updated versions with outdated versions and registered the copy of your site on my own account.
I made sure to run my local server using PHP 5.6.32

I was able to register, Update and activate Types, but then an error occurred in /wp-admin/admin-ajax.php:

Failed to load resource: the server responded with a status of 400 (Bad Request) 

It is because it updates to Types 2.3 instead of 3.0 thru the installer.

I escalated this.

#906760

We may have found the reason for the cURL issues.

- outdated cURL library on the hosting server, my suggestion would be to check on this with the hosting provider and upgrade to a version of cURL that has TLS if not done.
- Increase timeout limit

We are investigating as well with other users if this helps.

#906766

Hi Beda,

Thanks, I'll talk to the hosting provider. Closing the ticket.