Hi @andrewarthurdawson
Could you please post your site URL here so that we can have a look?
If you want it to remain private, you can also contact us via this contact form. If you choose to reach out directly, please include a link to this thread.
@bizanimesh i really didn’t want to open this thread but I’m trying to see if @jdembowski will restore the full part of the other thread I had on this. He closed it but also removed all my research. There really is nothing more that plug-in support can do as it’s not plug-in related. It’s either Godaddy server related or ISP/IP hop related. I just would like my prior forum full restored and kept closed for new comments so I have it for my own support. Can you do that? Once that’s done this can be closed.
The other forum that my research was archived is:
https://ww.wp.xz.cn/support/topic/curl-error-35-ssl_connect_error/
Hi @andrewarthurdawson
From the forum guidelines:
Posts can be closed by a moderator if they’ve become non-productive to the community. By this we mean if someone’s violating the guidelines (using the forums as a blog, arguing about world politics, vulgarity, attacking people, etc), we may close the post to prevent further escalation. We also will close posts that have gone too far off topic to be recovered.
This forum is specifically intended for Jetpack users to get help with Jetpack issues, and as you mentioned, that thread was not plugin related. Most of the comments had nothing to do with Jetpack. I believe that is why the thread was closed and archived.
I’ll leave this open for now in case @jdembowski wants to comment further, but I’m afraid we have no way to restore the comments from your other thread.
@drawmyface That makes sense Dan. Bummer on the loss of comments. Yes, indeed it’s not precisely Jetpack related but does involve the use of jetpack with managed WordPress with Godaddy. I just wanted to get to the root of why the issue exists as I and many others spent countless hours with support from Godaddy getting nowhere. I probably racked up 15 or more hours on support time with them. Regardless, the issue is hit or miss, it’s not constant, it deals with the meta data that is meant to carry over by jetpack (or yoast for some) where it times out and never even makes it. Why the timeout happens where godaddy can’t see it no one seems to know. They say it’s ISP/IP related, I believe it related to their caching environment and too many on their servers at times. Either way, I keep hoping someone out there will provide a solution or at least definitive proof of why this happens in Godaddy managed WordPress accounts using jetpack or yoast. Regrettably as you and Jan pointed out the other forum became a blog of people just reporting the error with no solution.
Moderator
Jan Dembowski
(@jdembowski)
Forum Moderator and Brute Squad
I’m sorry, but that topic’s many comments will not be restored. I archived it for the reasons I wrote. There were 5 pages of comments there and people jumping on was not good.
Especially since that was not even about the Jetpack plugin.
What I wrote there was this.
I am closing this 7 month old support topic as it has become a running blog post and that’s why I archived the pile on comments.
If anyone need support for this plugin then per the forum guidelines please start your own topic.
https://ww.wp.xz.cn/support/forum-user-guide/faq/#i-have-the-same-problem-can-i-just-reply-to-someone-elses-post-with-me-too
You can do so here.
https://ww.wp.xz.cn/support/plugin/jetpack/#new-post
That still applies. Everyone should create their own support topic to address their situation. That’s how these forums work and all of those replies were all over the place.
@jdembowski thank you for explaining. I understand. Hopefully anyone who writes in this one will be relevant to the actual problem.
Moderator
Jan Dembowski
(@jdembowski)
Forum Moderator and Brute Squad
Literally no one should write in this topic. You’re trying to restart your blog post again and that’s not for this site.
The only people who should answer this topic are either trying to explain (like I am) or are trying to directly help the original poster (that’s you). Anyone else piling on will be informed to start their own topic with their own problem.
That’s how these support forums work.
https://ww.wp.xz.cn/support/forum-user-guide/faq/#i-have-the-same-problem-can-i-just-reply-to-someone-elses-post-with-me-too
@jdembowski That’s what I mean, I agree with you. I am looking for someone who has a solution as to the actual source of this problem not people just saying they have the problem too. Please for anyone who reads this, if you know the solution, then please do share. All I know is it’s either server related with Managed WordPress on Godaddy or ISP/IP related. Either way it’s a timeout issue that is hit or miss with metadata either sometimes coming through and sometimes timing out before it has a chance too. Jan, do you have any other suggestions for me on this error?
