golfloire
Forum Replies Created
-
Hi,
it’s working… with another plugin (webp express)
I didn’t try again with media webp since this thread
??It was a 500 error but it’s solved
Long story:
our provider offer the possibility to use a litespeed cache so I configured it and it worked flawlessly during 2 days. Note there was th need to change the server IP to allow the use of the litespeed cache.
And suddenly jetpak blocked a lot of things (access to the admin, publicize, etc… but there was some elements still working as the stats even if it was said there was non connxion…).
Removing the litespeed cache and coming back to our server original IP solve the problem with jetpack…Solved by deleting the site on my account on wordpress.com
But can’t connect it back
So I had to deactivate, delete and re-instal the jetpack plugin
And now configure it again…
And as 1 year ago, publicize don’t want to connect to facebook and twitter…Hi Steve,
Thanks for your help.
First, note that I’m not a server expert (far from that in fact ?? ).
So what I did:
– I checked in the cpanel the MIME types and there is “Image/webp .webp” by default in the host provider configuration
– For the firewall, I think there is one managed by the hosting company… but I don’t have the hand on it (and if it’s in the default MIME types it won’t make sense to block webp for them… but maybe I’m wrong)
– There is a varnish… I deactivated it to see if it was the problem and no change.Any other idea? ??
Our host forced the wordpress IP address in their white list (again) and would like to know if you can do another test.
Thanks for your patience.- This reply was modified 6 years, 7 months ago by golfloire.
Thanks.
I transmitted all the infos to our host.
I wait for their answer and will let you know.I just have the answer from our host:
Jetpack is on the white list but they will check if the IP address changed recently.
They would like you to do another request/test in order for them to check the errors logs and see what could be wrong.
Please, tell us the time you did the new test in order to find it easily in the logs.
Thanks for your helpJust a quick note about the Tags Plugin: after 4 successfull posts, the fifth is missing the featured image, excerpt, etc… so it’s not a tag problem…
I still wait for our host answer ??
Thanks for your answer.
I transmitted the infos to our host.
I will let you know what they will answer to me.Since my initial report, I installed the plugin you adviced me for the tags. And with the 2 posts we published there was no errors… but I will wait a few more posts before saying it’s repared…
For xmlrpc… there is no “more impact” on Facebook… All the impact is on Facebook…
The success rate on twitter is 100%. It NEVER happened to fail.
For Facebook, the success rate is 66%…
The problem is ONLY with Facebook.For the cURL error, our host would like to know what’s the request you sent to have the error. Do I have to contact you directly to have the procedure you use?
For the caching, it was one of my first suspect. At that time I was testing Comet Cache. I get back to WP Super Cache and it changed nothing. I’m think WP Super Cache is fully compatible with Jetpack ??
For the security, it’s mainly our host and they say nothing seems to block. But maybe if they know how you get these errors, they will find something.
Thanks for your help
- This reply was modified 6 years, 7 months ago by golfloire.
Correct me if I’m wrong but XML-RPC is used by Publicize, not only to post on Facebook but also on the other social networks, right?
As it works FLAWLESSLY with Twitter (https://twitter.com/golfloire), I don’t think the issue is related to XML-RPC.They answered me.
It seems there’s nothing wrong the server configuration.
However, they made a slight modification (maybe it could help).
They want to know what kind of procedure/diagnostic you did to have the cURL error in order to check on their side what could be the issue.Hi,
I asked them a few minutes ago. As soon as I have an answer I will let you know.
Thanks for your help.ok but, the problem is some parts of the publication are always ok (begining of the text/article, link to the post) and some are ramdom (feature image, excerpt…). Why half of a request would be executed sometimes? And sometimes fully executed…
I’m not a dev so maybe I’m wrong but not sure to understand the logic behind that.But if the plugin doesn’t work, I will ask for sure to my host.
- This reply was modified 6 years, 7 months ago by golfloire.
Hi,
Thanks for your help.
For the servers, I will ask (but it will not explain why it is random).
For the xmlrpc, I didn’t block or limit it.
For the theme, it’s Divi from Elegant Theme. Maybe it could be the cause… but I don’t remember an option to disable the tags. So I will use the plugin you suggested and see what happend next times I will published a post.
i will let you know.