• Resolved mwarbinek

    (@mwarbinek)


    I believe the problem with the Widget and the Debug result of communication trouble are inter-related since they are existing at the same time and both refer to Jetpack.

    I set the sidebar and footer widgets up for the theme a long time ago, had some widgets appear in the sidebar for certain pages and not for others, etc.

    Somewhere along, the widget control (includes visibility controls) stopped working, where I can no longer change or modify the widgets. This says previous widget settings are locked. No matter what I delete, move, alter, or modify in the widget module, that change shows in the widget module area, but does Not show on the website. The website continues to show the widgets as previously set.

    Debug
    Debug said, “it looks like your site cannot communicate properly with Jetpack”

    Ok, it said that but the Dashboard says connected, even when I disconnected and reconnected, weird… (maybe I am in the Twilight Zone, waiting to hear the theme music and Rod Serling’s voice, haven’t heard that yet).

    I did some checks,

    • Browser cache cleared – Same Problem,
    • Different browser used, cache cleared – Same Problem,
    • Jetpack connection turned off then back on, showing connected, -Same problem,
    • Checked “https://domain name/xmlrpc.php – URL check Works fine
    • Deactivated plugins – Same problem,
    • Switched to WordPress default theme 20-15 – Same problem
    • Maybe a communication issue with WordPress?? – Don’t know, check results above say Yes and No at the same time. (Maybe this is something like a Mission Impossible trick, like a security feed in a loop using a previous recording and all looks fine but is not).

    The debug result that shows errors is as follows,

    SELF:
    							Array
    (
        [headers] => Requests_Utility_CaseInsensitiveDictionary Object
            (
                [data:protected] => Array
                    (
                        [server] => nginx
                        [date] => Tue, 14 Nov 2017 21:46:21 GMT
                        [content-type] => text/plain;charset=utf-8
                        [expires] => Wed, 11 Jan 1984 05:00:00 GMT
                        [cache-control] => no-cache, must-revalidate, max-age=60
                        [x-hacker] => Jetpack Test
                        [x-ac] => 3.ord _dca
                        [strict-transport-security] => max-age=15552000
                    )
    
            )
    
        [body] => {"error":"Could not fetch your site data","error_description":"We were unable to fetch the data from your Jetpack-powered site, the communication channel seems to be broken."}
        [response] => Array
            (
                [code] => 400
                [message] => Bad Request
            )
    
        [cookies] => Array
            (
            )
    
        [filename] => 
        [http_response] => WP_HTTP_Requests_Response Object
            (
                [response:protected] => Requests_Response Object
                    (
                        [body] => {"error":"Could not fetch your site data","error_description":"We were unable to fetch the data from your Jetpack-powered site, the communication channel seems to be broken."}
                        [raw] => HTTP/1.1 400 Bad Request
    Server: nginx
    Date: Tue, 14 Nov 2017 21:46:21 GMT
    Content-Type: text/plain;charset=utf-8
    Transfer-Encoding: chunked
    Connection: close
    Expires: Wed, 11 Jan 1984 05:00:00 GMT
    Cache-Control: no-cache, must-revalidate, max-age=60
    X-hacker: Jetpack Test
    X-ac: 3.ord _dca
    Strict-Transport-Security: max-age=15552000
    
    {"error":"Could not fetch your site data","error_description":"We were unable to fetch the data from your Jetpack-powered site, the communication channel seems to be broken."}
                        [headers] => Requests_Response_Headers Object
                            (
                                [data:protected] => Array
                                    (
                                        [server] => Array
                                            (
                                                [0] => nginx
                                            )
    
                                        [date] => Array
                                            (
                                                [0] => Tue, 14 Nov 2017 21:46:21 GMT
                                            )
    
                                        [content-type] => Array
                                            (
                                                [0] => text/plain;charset=utf-8
                                            )
    
                                        [expires] => Array
                                            (
                                                [0] => Wed, 11 Jan 1984 05:00:00 GMT
                                            )
    
                                        [cache-control] => Array
                                            (
                                                [0] => no-cache, must-revalidate, max-age=60
                                            )
    
                                        [x-hacker] => Array
                                            (
                                                [0] => Jetpack Test
                                            )
    
                                        [x-ac] => Array
                                            (
                                                [0] => 3.ord _dca
                                            )
    
                                        [strict-transport-security] => Array
                                            (
                                                [0] => max-age=15552000
                                            )
    
                                    )
    
                            )
    
                        [status_code] => 400
                        [protocol_version] => 1.1
                        [success] => 
                        [redirects] => 0
                        [url] => https://jetpack.wordpress.com/jetpack.testsite/1/?url=https://ae-market-consignment.com/xmlrpc.php
                        [history] => Array
                            (
                            )
    
                        [cookies] => Requests_Cookie_Jar Object
                            (
                                [cookies:protected] => Array
                                    (
                                    )
    
                            )
    
                    )
    
                [filename:protected] => 
                [data] => 
                [headers] => 
                [status] => 
            )
    
    )

    (This forum really needs the accordion feature, saves room and shortens these long posts due to code displays).

    I looked at the forum and Google, found nothing so far. I checked this forum and nothing helped, so far, but there are thousands of posts on this.

    I enjoy Nostalgia (Twilight Zone), but this problem is not entertaining.

    So where does this stand? What can be done?

    Thanks

    • This topic was modified 7 years ago by mwarbinek.
    • This topic was modified 7 years ago by mwarbinek.
Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Contributor Richard Archambault

    (@richardmtl)

    Could you post your site URL here, so I can have a look?

    If you want it to remain private, you can also contact us via this contact form:
    https://jetpack.com/contact-support/?rel=support

    If you contact us through our form, please make sure to include a link to this thread in your message.

    Thread Starter mwarbinek

    (@mwarbinek)

    Oh yea, sorry.

    Link: https://ae-market-consignment.com/

    Plugin Contributor Richard Archambault

    (@richardmtl)

    I would suggest contacting your host and explaining that we are unable to access your blog via cURL, which is needed in order to use Jetpack on your site.

    You can pass this information onto them:

    1. We checked for access to xmlrpc.php via browser:

    https://ae-market-consignment.com/xmlrpc.php

    That test returned “XML-RPC server accepts POST requests only.” which is a valid result.

    2. We checked via cURL by running the following command from the terminal:

    curl -A “Jetpack by WordPress.com” -is -H ‘Content-Type: text/xml’ –data ‘<?xml version=”1.0″?><methodCall><methodName>demo.sayHello</methodName><params></params></methodCall>’ ‘https://ae-market-consignment.com/xmlrpc.php&#8217; && echo

    The cURL test returned the following invalid result:

    —————
    HTTP/1.1 401 Unauthorized
    —————

    Please provide this information above to your host so they can correct the server settings and allow cURL access.

    Let me know what they say!

    Thread Starter mwarbinek

    (@mwarbinek)

    That’s a test I could not do.

    This is the second time cUrl issue has popped up. A website I manage on Shaw hosting (Hostopia) blocks cUrl or has it disabled, so JetPack is mostly useless there and Shaw Hosting does not care about the effect on clients using WordPress (lousy host).

    This current issue, again with cUrl, pops up. In this case, this client’s website is hosted by another hosting service. I spoke with their support agent who said they have to forward the ticket to a support team that handles server issues. I have to wait to see what happens there, hopefully they support cUrl. Will post the result here when I get it.

    Let’s hope this does not lead to 2 strikes against JetPack.

    • This reply was modified 7 years ago by mwarbinek.
    Thread Starter mwarbinek

    (@mwarbinek)

    Only 1 Strike, thankfully.

    I just got word from the current hosting service. They do support cUrl and their mod_security rule was triggered by a false positive that blocked JetPack.

    They fixed the issue and JetPack now works fine. I did a Debug check and all is green. (Hostopia should be green with envy on this one).

    I also worked with the widgets and viola, works perfectly.

    Your test of cUrl did provide the info needed and that was the problem.

    Solved! ??

    Thanks for your help.

    • This reply was modified 7 years ago by mwarbinek.
    • This reply was modified 7 years ago by mwarbinek.
    • This reply was modified 7 years ago by mwarbinek.
Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Widget Visibility Not Working | JetPack has trouble Communicating with WordPress’ is closed to new replies.