- This topic has 4 replies, 3 voices, and was last updated 1 year ago by Tom.
March 24, 2020 at 8:11 am #1208618Nick
The Generate Press Premium plugin is causing a cURL Error 28: Connection timed out after 10001 milliseconds. This is causing my site to be unable to update plugins, and is constantly causing 504 errors.
My web host has confirmed that it isn’t anything listed in this article and has carried out the steps listed below, and the issue still persists unless GP Premium is disabled.
Make sure your server is running a recent version of PHP and the cURL library.
Try to increase your Server Memory Limits settings.
The cURL error can be a dns related issue. Your hosting company might need to switch dns configuration to OpenDNS : https://www.howtogeek.com/164981/how-to-switch-to-opendns-or-google-dns-to-speed-up-web-browsing/
Ask your host if there is some limitation with wp-cron, or if loopback is disabled.
Ask your host if there a firewall or security modules (e.g. mod_security ) that could block the outgoing cURL requests.
The screenshot is from is Query Monitor.
My server IP address is: http://220.127.116.11/
I’m not using a CDN or Cloudflare.
Could you please look into this? thanksMarch 24, 2020 at 8:15 am #1208619March 24, 2020 at 9:36 am #1208687LeoStaffCustomer Support
Just to confirm, your host has made sure that they are allowing communication to generatepress.com?
https://generatepress.com/forums/topic/curl-error-28-connect-timed-out/#post-518326March 26, 2020 at 12:51 pm #1211170Nick
Hi Leo, this is the reply from my host, InMotion:
I looked into the connection error and I was unable to find a block in place for generatepress.com, or their aws server in general. I did find a couple of forum posts about the connection errors with connecting the plugin, and some of there were due to the host being on an nginx server, just like you are. I would reach out to the plugin developer and confirm if they support connections with an nginx server, and if they do not we can help get you on a non nginx server.March 26, 2020 at 5:55 pm #1211355TomLead DeveloperLead Developer
I just checked with our server admins and they have confirmed that
18.104.22.168is not blocked on our end of things.
Perhaps one of your other plugins is causing a conflict?
If the updated is causing issues right now, you can tell it to stop running:
remove_action( 'admin_init', 'generate_premium_updater', 0 );
Does that prevent the errors?
- You must be logged in to reply to this topic.