Skip to main content

Domain with Cloudflare

hmaddy
i added one domain on cloudflare. hosting is with wordpress. when proxy is enable, then home page will work and inner pages will not work. How to solve this when proxy enable.

Comments

6 comments

Date Votes
  • cPRex Jurassic Moderator
    @hmaddy - you have to provide us with more information for your questions. What does "not work" mean - do you get an error? Is the page blank? Do you see anything in the Apache logs on the server side? Have you already reached out to Cloudflare to see what their recommendation is for this setting?
    0
  • hmaddy
    When we enable proxies on Cloudflare, then WordPress inner pages will throw a white page or timeout error. When we disable the proxy and enable dns only, then no issues everything will be fine.
    0
  • cPRex Jurassic Moderator
    Thanks for the additional details. Since the issue only happens with the Cloudflare proxy enabled, it would be best to reach out to them directly for additional details, since nothing is changing on the cPanel side or server side.
    0
  • hmaddy
    Thats correct. But my doubt is the same script and configuration is working on another server with proxy
    0
  • hmaddy
    got the following reply from cloudflare. Error 524 indicates that Cloudflare successfully connected to the origin web server, but the origin did not provide an HTTP response before the default 100 second connection timed out. This can happen if the origin server is simply taking too long because it has too much work to do - e.g. a large data query, or because the server is struggling for resources and cannot return any data in time. Resolution Here are the options we'd suggest to work around this issue:
    • Implement status polling of large HTTP processes to avoid hitting this error.
    • Apache or proxy_read_timeout API endpoint.
    • If you regularly run HTTP requests that take over 100 seconds to complete (for example large data exports), move those processes behind a subdomain not proxied (grey clouded) in the Cloudflare DNS app.
    • If error 524 occurs for a domain using Cloudflare Railgun, ensure the lan.timeout is set higher than the default of 30 seconds and restart the railgun service.
    0
  • rbairwell
    Can you try the following command from your computer: curl -vk --resolve www.example.com:80:192.0.2.127; http://www.example.com
    (replacing www.example.com with your domain name and 192.0.2.127 with the IP address of your server). If you haven't got access to curl on your computer (say you are running Windows without having WSL2 setup with a local Linux install), running it on the server should be okay. That'll emulate - to a degree - what Cloudlfare is trying to do when it fetches the page from your site. If you notice it timing out, the problem is 100% on the "server side" (it could be an Apache redirect looping, it could be a long running PHP script etc: just as the Cloudflare resolution bit says). If it works quickly and returns the correct page, then the problem is most likely somewhere between Cloudflare and your site (perhaps the server firewall is blocking their IP address? - it'll be worth tail
    ing the Apache/Nginx logs and the var/log/messages file when you make the request through Cloudflare to see if anything is being triggered.
    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post