• Resolved juliamb

    (@juliamb)


    Hi.

    I have installed JetPack on a website and I’m getting a 503 almost every day, the site goes down for a few seconds and then it works again. I’ve noticed in the browser dev tools console that when I’m navigating on the JetPack dashboard I get a lot of errors and then the site goes down. The error looks like these:

    ..../wp-json/jetpack/v4/rewind?_cacheBuster=1583249491707 400
    s @ admin.js?ver=8.2.3:1
    fetchRewindStatus @ admin.js?ver=8.2.3:1
    (anonymous) @ admin.js?ver=8.2.3:1
    (anonymous) @ admin.js?ver=8.2.3:1
    fetchRewind @ admin.js?ver=8.2.3:1
    value @ admin.js?ver=8.2.3:1
    de @ react-dom.min.b694e242.js?ver=16.9.0:3
    Vg @ react-dom.min.b694e242.js?ver=16.9.0:3
    ph @ react-dom.min.b694e242.js?ver=16.9.0:5
    lh @ react-dom.min.b694e242.js?ver=16.9.0:4
    O @ react-dom.min.b694e242.js?ver=16.9.0:4
    Sb @ react-dom.min.b694e242.js?ver=16.9.0:5
    wh @ react-dom.min.b694e242.js?ver=16.9.0:5
    fd @ react-dom.min.b694e242.js?ver=16.9.0:5
    (anonymous) @ react-dom.min.b694e242.js?ver=16.9.0:5
    kh @ react-dom.min.b694e242.js?ver=16.9.0:4
    id @ react-dom.min.b694e242.js?ver=16.9.0:5
    render @ react-dom.min.b694e242.js?ver=16.9.0:5
    (anonymous) @ admin.js?ver=8.2.3:1
    (anonymous) @ admin.js?ver=8.2.3:1
    n @ admin.js?ver=8.2.3:1
    (anonymous) @ admin.js?ver=8.2.3:1
    (anonymous) @ admin.js?ver=8.2.3:1
    
    GET .../wp-json/jetpack/v4/verify-site/google?_cacheBuster=1583249902040 503
    s	@	admin.js?ver=8.2.3:1
    fetchVerifySiteGoogleStatus	@	admin.js?ver=8.2.3:1
    (anonymous)	@	admin.js?ver=8.2.3:1
    (anonymous)	@	admin.js?ver=8.2.3:1
    (anonymous)	@	admin.js?ver=8.2.3:1
    value	@	admin.js?ver=8.2.3:1
    Ti	@	react-dom.min.b694e242.js?ver=16.9.0:5
    unstable_runWithPriority	@	react.min.0212dc62.js?ver=16.9.0:2
    Ma	@	react-dom.min.b694e242.js?ver=16.9.0:3
    Ia	@	react-dom.min.b694e242.js?ver=16.9.0:5
    ze	@	react-dom.min.b694e242.js?ver=16.9.0:4
    (anonymous)	@	react-dom.min.b694e242.js?ver=16.9.0:3
    unstable_runWithPriority	@	react.min.0212dc62.js?ver=16.9.0:2
    Ma	@	react-dom.min.b694e242.js?ver=16.9.0:3
    mg	@	react-dom.min.b694e242.js?ver=16.9.0:3
    V	@	react-dom.min.b694e242.js?ver=16.9.0:3
    Sb	@	react-dom.min.b694e242.js?ver=16.9.0:5
    enqueueSetState	@	react-dom.min.b694e242.js?ver=16.9.0:5
    q.setState	@	react.min.0212dc62.js?ver=16.9.0:2
    (anonymous)	@	admin.js?ver=8.2.3:1
    (anonymous)	@	admin.js?ver=8.2.3:1
    (anonymous)	@	admin.js?ver=8.2.3:1
    (anonymous)	@	admin.js?ver=8.2.3:1
    (anonymous)	@	admin.js?ver=8.2.3:1
    (anonymous)	@	admin.js?ver=8.2.3:1
    (anonymous)	@	admin.js?ver=8.2.3:1
    (anonymous)	@	admin.js?ver=8.2.3:1
    we	@	admin.js?ver=8.2.3:1
    xe	@	admin.js?ver=8.2.3:1
    u	@	admin.js?ver=8.2.3:1
    hashchange (async)		
    p	@	admin.js?ver=8.2.3:1
    r	@	admin.js?ver=8.2.3:1
    Show 28 more frames
    load-scripts.php?c=1…pointer&ver=5.3.2:4 
    
    GET .../wp-json/jetpack/v4/jitm?message_path=wp%3Atoplev…jetpack_traffic%3Aadmin_notices&query=page%253Djetpack&_wpnonce=0bd253bbb0 503
    send	@	load-scripts.php?c=1…pointer&ver=5.3.2:4
    ajax	@	load-scripts.php?c=1…pointer&ver=5.3.2:4
    n.<computed>	@	load-scripts.php?c=1…pointer&ver=5.3.2:4
    (anonymous)	@	jetpack-jitm.min.js?ver=1.0:2
    each	@	load-scripts.php?c=1…pointer&ver=5.3.2:2
    each	@	load-scripts.php?c=1…pointer&ver=5.3.2:2
    e	@	jetpack-jitm.min.js?ver=1.0:2
    (anonymous)	@	jetpack-jitm.min.js?ver=1.0:2
    dispatch	@	load-scripts.php?c=1…pointer&ver=5.3.2:3
    r.handle	@	load-scripts.php?c=1…pointer&ver=5.3.2:3
    hashchange (async)		
    p	@	admin.js?ver=8.2.3:1
    r	@	admin.js?ver=8.2.3:1

    I don’t know if this is causing the 503 error, but I think is a weird coincidence. Could you tell me if this might be causing the problem?

    Thanks, regards!

    • This topic was modified 4 years, 8 months ago by juliamb.
Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support darnelldibbles

    (@darnelldibbles)

    Hey there,

    Is this in reference to juliamenndez.com? If so, I debugged your site and am receiving a Can not resolve your domain 'A record' message.

    https://jetpack.com/support/debug/?url=www.truenorthreports.com#async_get_sample_api_output

    It does appear the issue is related to the 403 block on the xmlrpc.php file. In order to resolve this, I’d suggest checking if you have any security plugins active first. If so, I’d recommend disabling them temporarily. If that does not help, you would then need to contact your hosting provider, and ask them to search into security logs for any blocked requests from our servers. Our requests look like the following:

    Please ask them to whitelist the IP addresses listed above. Note that these IP addresses could change (or more could be added) at any time, which could break your connection to Jetpack. For this reason, we actually discourage whitelisting specific IPs, although with some hosts it may be the only option.

    Hope that helps. Let us know if you have any questions. Thanks!

    Thread Starter juliamb

    (@juliamb)

    Thank you for your answer, @darnelldibbles!

    I’m having the problem on another website, not my personal one, sorry I did not specified that.
    I’ll check this solution, I hope it works!

    Thanks again

    Plugin Support darnelldibbles

    (@darnelldibbles)

    You’re welcome! if you still have issues, provide the like to the URL and we’ll take a look. Thanks!

    Thread Starter juliamb

    (@juliamb)

    Hi @darnelldibbles.

    Is there a way to test if there’s a problem with my security plugin and the xmlrp.php file without deactivating my security plugin? The plugin I’m using is Wordfence.

    Thank you so much!

    Plugin Support Fotis

    (@fstat)

    Hi there,

    I suggest contactin Wordfence. They’ll tell you how to set exceptions for both your XML-RPC file and Jetpack.

    Thread Starter juliamb

    (@juliamb)

    Thanks, @fstat, I think I will.
    Regards

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘JetPack and 503 error’ is closed to new replies.