One known cause is a DNS problem on the server either due to misconfiguration or a recent DNS change not fully propagating to the site, resulting in the site attempting to connect back to its own URL but inadvertently connecting to the old site since DNS has not propagated fully yet. A host may block these connections back to themselves intentionally or through misconfiguration. If it is unable to do this then the simulated cron cannot function. Basically the site connects back onto itself. For instance, if your site is WordPress will access via Curl. What are they? PHP needs to be able to use Curl to load your site via its public URL. WordPress' simulated cron works by having the site connect back to itself via curl (or other available fallback connection method if curl in unavailable) to trigger actions to take place behind the scene.
0 Comments
Leave a Reply. |