[steveporkParticipant]

This reply has been marked as private.

[steveporkParticipant]

This reply has been marked as private.

[RahulModerator]

Hey There,

Thanks for writing back!

Try going to Dashboard > Updates and clicking Check again. There might be an issue where the package files may not being served correctly even on validated sites, but everything is resolved!

Let us know if this makes a difference.

Thanks for understanding!

[steveporkParticipant]

I don’t believe you’ve read the previous posts…. D

isabling CloudFlare was your original proposal – that did fix the issue temporarily, but that isn’t a long term solution. You suggested a CloudFlare filter and that didn’t work either – that’s when you asked for my site credentials.

[JoaoModerator]

Hi There,

Please access your site via FTP > access wp-content/plugins / delete layer slider.

Access ADDONS again and try to install it.

Let us know how it goes,

Joao

[steveporkParticipant]

Same issue after re-installing.
As I say, disabling CloudFlare solves the issue, however that isn’t a solution for me.

It looks as if it’s an authentication issue of some type that CloudFlare is restricting.

[RadModerator]

Hi there,

Then it’s due to Cloudflare’s cache, you have to purge everything. Unfortunately, we don’t have control over your CF’s setting. You can set your CF to development mode while doing the updates.

Thanks!

[steveporkParticipant]

I must apologise, I was mistaken. CloudFlare was disabled whilst I was attempting the update.

Plugins not-affiliated with Theme.co haven’t been experiencing the same issue.

[Paul RModerator]

Hi,

Please contact your webhost. Here is a form letter you may use:

Hello [provider],

My WordPress installation is having a hard time making outbound HTTP requests. I’m using X theme and it makes a request to community.theme.co for setting up automatic updates. Here is the error message I’m receiving:

[screenshot, or copy/paste the verbose error message (see above regarding the &x-verbose flag)]

Could you please do the following?

– Ensure my site can reach this domain: community.theme.co
– Ensure cURL is working, and allow_url_fopen is enabled.
– Ensure PHP is configured with the latest CA Root Certificates.
– Check into the error message above.

Please advise on anything you discover. Thank you.

Thanks

[steveporkParticipant]

I am the web host –
allow_url_fopen = On
cURL is enabled
SSL is successfully configured
I can ping community.theme.co:

PING community.theme.co (208.117.43.145) 56(84) bytes of data.
64 bytes from theservercompany.com.43.117.208.in-addr.arpa (208.117.43.145): icmp_seq=1 ttl=56 time=107 ms
64 bytes from theservercompany.com.43.117.208.in-addr.arpa (208.117.43.145): icmp_seq=2 ttl=56 time=107 ms
64 bytes from theservercompany.com.43.117.208.in-addr.arpa (208.117.43.145): icmp_seq=3 ttl=56 time=107 ms
64 bytes from theservercompany.com.43.117.208.in-addr.arpa (208.117.43.145): icmp_seq=4 ttl=56 time=107 ms
64 bytes from theservercompany.com.43.117.208.in-addr.arpa (208.117.43.145): icmp_seq=5 ttl=56 time=107 ms
^C
— community.theme.co ping statistics —
5 packets transmitted, 5 received, 0% packet loss, time 4002ms
rtt min/avg/max/mdev = 107.087/107.431/107.765/0.405 ms

[RadModerator]

Hi there,

I checked and your LayerSlider is the latest one, please check compatible versions here https://community.theme.co/kb/version-compatibility/

Please note that we’re the one who’ll provide updates for the bundled plugins. What you’re doing is updating it directly from the plugin author in which you don’t have the license. If you wish ty bypass our update and get their updates, then you’ll have to buy a license from them.

Thanks!

[steveporkParticipant]

My mistake, thank you for the help.

[JoaoModerator]

Glad to hear we managed to help,

Joao

[Author]

Posts