Hi there, @ariesgdim,
Can you confirm that you’re running the latest version of the plugins (both Jetpack and WooCommerce) and that the error completely goes away when you deactivate Jetpack?
What happens if you temporarily deactivate WooCommerce instead and keep Jetpack active? Did you get the same error?
We’d love to investigate further on this, and to do that we’ll need a working Jetpack connection, which is currently broken for your site with the following error: “cURL error 28: Operation timed out after 5000 milliseconds with 0 bytes received”.
This usually means that your web host is blocking some connections Jetpack needs in order to work correctly.
Could you please contact your web host and ask them to make sure that the connections to and from *.wordpress.com are whitelisted? In terms of IP ranges, the following ranges need to be fully whitelisted:
https://jetpack.com/support/hosting-faq/
Let me know how you get on and we’ll take it from there. Thanks!
Can you confirm that you’re running the latest version of the plugins (both Jetpack and WooCommerce) and that the error completely goes away when you deactivate Jetpack?
Yes we do have all our plugins up to date. We keep them all up to date. This issue has been going on for at least 10 mos or more.
What happens if you temporarily deactivate WooCommerce instead and keep Jetpack active? Did you get the same error?
No when we deactivate woocommerce we do not get the same error and we can edit pages when Woo is deactivated.
My host is Godaddy. They said there are no firewalls running on my site therefore nothing is blocking….
-
This reply was modified 4 years, 6 months ago by
ariesgdim.
Hi @ariesgdim
It seems that this issue isn’t related to WooCommerce itself, but that you’ve already gone ahead and edited the correct .htaccess file; however, could you confirm if you inserted this code:
# BEGIN Line too long fix
<IfModule mod_substitute.c>
SubstituteMaxLineLength 10M
</IfModule>
# END Line too long fix
You nay as well reach out to Godaddy, and tell them to implement this for you, so they can make sure you’ve correctly inserted that line.
Let us know how that goes.
Best,
The same thing is happening to me, I have the ERR_HTTP2_PROTOCOL_ERROR when adding new or modifying pages or posts, I have disabled jetpack and the error persists, my site is also an online store, in fact I have two domains for two different countries, with the same theme and in both the error happens to me.
I am also hosted with Godaddy and they insist that it is not a DNS error or theirs but that it is a code error, however I have not modified anything and I am really going crazy while looking for information trying to solve it.
I even thought that I should have some update to my store theme but I put a generic theme like twenty and the error persists.
Anything you can do to solve this problem will be of great help.
Greetings`
Hi @dianaemiguela
If the error persists with Jetpack disabled, then it doesn’t sound like the issue is related to Jetpack. You may need to add the same code to your .htaccess file as Mehdi mentioned above.
If you continue to have trouble I’d suggest posting in the general WordPress.org forums for further help:
Support Forums
This guide may also be helpful when posting in the forums:
http://www.wpbeginner.com/beginners-guide/how-to-properly-ask-for-wordpress-support-and-get-it/
Thank you for the confirmation of the solution to this problem, i inserted the code and all is going well.
I’m so glad! thanks a lot
I have tried
# BEGIN Line too long fix
<IfModule mod_substitute.c>
SubstituteMaxLineLength 10M
</IfModule>
# END Line too long fix
and it did not work for me. I also deactivated Jetpack today so I could make changes to my site. Now I can’t get it to connect. Every time I hit connect/set up jetpack I get “An error occurred. Please try again”
this is the full error I get on my site when I try to edit a page. Also finally got the jetpack plugin to connect.
This site can’t be reached
The webpage at https://earthandfire.shop/wp-admin/post.php?post=8626&action=edit might be temporarily down or it may have moved permanently to a new web address.
ERR_HTTP2_PROTOCOL_ERROR
maybe this helps?