Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

1and1 white page (conflict with Cloudflare) #8792

Closed
Tombost opened this issue Aug 9, 2018 · 4 comments
Closed

1and1 white page (conflict with Cloudflare) #8792

Tombost opened this issue Aug 9, 2018 · 4 comments
Labels
[Status] Duplicate Used to indicate that a current issue matches an existing one and can be closed [Type] Plugin Interoperability Incompatibilities between a specific plugin and the block editor. Close with workaround notes.

Comments

@Tombost
Copy link

Tombost commented Aug 9, 2018

Describe the bug
Hello,
I have just install a wordpress to my 1and1 webspace, but add page or add article page is blank.
I use cloudflare for the SSL, I have try to desactivate cache (js, css and html)

You can see :
https://ibb.co/mn7fRU

@designsimply designsimply added [Type] Bug An existing feature does not function as intended [Feature] UI Components Impacts or related to the UI component system [Status] Duplicate Used to indicate that a current issue matches an existing one and can be closed labels Aug 9, 2018
@designsimply
Copy link
Member

Thank you for the report!

Sometimes blank pages were appearing when a race condition happened. This was reported in #8455 and fixed in #8578 and shipped in version 3.5. Can you make sure you have updated to the latest version of Gutenberg?

Cloudflare has also shipped an update on 8-Aug-2018 to prevent some problems with saving (ref) and you should update to the latest version to take advantage of that change.

@Tombost
Copy link
Author

Tombost commented Aug 13, 2018

Hi,

I have update to 3.5, same problem...
How i can update clouflare ? This is not automatic ?

@Tombost
Copy link
Author

Tombost commented Aug 13, 2018

I have remove cloudlfare and it work again so the problem is cloudflare, any idea ?

@designsimply
Copy link
Member

#2704 (comment) says that Cloudflare implemented a fix before 8-Aug-2018 for problems with their WP0025B rule, and the #2704 issue has a some discussion about other possible causes (for errors such as "Prevent abuse against wp-json api Type B" and possibly the 100030 rule) which may also be affecting the WordPress editor. Good next steps would be to:

  1. Find out if your Cloudflare WAF log indicates which rule is causing requests to be blocked.
  2. Contact Cloudflare to let them know that you're having trouble, what WordPress and Gutenberg and Cloudflare versions you are using, which rule in the Cloudflare WAF logs are causing trouble, and you could also link them to CloudFlare blocking REST API PUT Request (Draft Doesn't Get Saved) (solved by an update from Cloudflare) #2704 in case it helps them with context.
  3. Add a comment to CloudFlare blocking REST API PUT Request (Draft Doesn't Get Saved) (solved by an update from Cloudflare) #2704 noting that you're still having trouble with Cloudflare and noting what you found in the logs and mention whether you've contacted Cloudflare about the problem.

Thank you for being willing to troubleshoot and work through the issue!

@designsimply designsimply added [Type] Plugin Interoperability Incompatibilities between a specific plugin and the block editor. Close with workaround notes. and removed [Feature] UI Components Impacts or related to the UI component system [Type] Bug An existing feature does not function as intended labels Aug 17, 2018
@designsimply designsimply changed the title 1and1 white page 1and1 white page (conflict with Cloudflare) Aug 17, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Status] Duplicate Used to indicate that a current issue matches an existing one and can be closed [Type] Plugin Interoperability Incompatibilities between a specific plugin and the block editor. Close with workaround notes.
Projects
None yet
Development

No branches or pull requests

2 participants