Question

Problem with Wordpress updater and Jetpack connection (register_http_request_failed)

Posted October 17, 2014 5.4k views

Three days ago I uploaded new version of my blog, and when I was activate Jetpack plugin on Wordpress API, I always receive a message about http_headers. Below, the message that I’m getting: 

Jetpack could not contact WordPress.com: register_http_request_failed. This usually means something is incorrectly configured on your web host.
name lookup timed out

I don’t change any configurations in my droplet, iptables or file permissions....yesterday (10/16/2014) I received a mail from Digital Ocean talking about SSL v3, and I think this can be the root of problem (or not).

Is there any change or lock on datacenter that could block Wordpress authentication with Wordpress API ?

More info

-Admin interface is so slow because wordpress always checks for updates of his core (5-10 seconds to get response for a request avg).

Add a comment
carlos.spohr
By:
carlos.spohr

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
2 answers
carlos.spohr October 17, 2014

I found the problem on my DNS config. Here (in Brazil) we always use Google’s DNS (8.8.8.8 or 8.8.4.4), my droplet has these ones on resolv.conf.

I looking for NY public DNS and replaced current DNSs by this new one (66.93.87.2).

My /etc/resolv.conf:

#nameserver 4.2.2.2
#nameserver 8.8.8.8

nameserver 66.93.87.2

All internal requests from Wordpress are working perfectly.

Reply Report
  • st8ofmindz79 November 5, 2014

    I’ll verify that this works. Thanks for the leg work carlos.spohr!

    I don’t remember specifically setting google nameservers in my resolv.conf file so perhaps it’s a default somehow? I’d be interested in knowing.

    I’m very inexperienced at server admin and I followed guides here on DO to set up my Ubuntu server. Couldn’t find a step setting up resolv.conf.

    In any case, thanks again.

    Reply Report
st8ofmindz79 November 5, 2014
[deleted]
Reply Report
st8ofmindz79 November 5, 2014

I just found this answer (read the comment to the answer by davidkomer).

Only having one nameserver in resolv.conf fixed it.

I removed 4.2.2.2 and all seems copacetic. In case one wants to continue using Google DNS.

Reply Report
  • carlos.spohr November 5, 2014

    Hi @st8ofmindz79,

    Always is a good idea have more than one nameserver. Here in Brazil, sometimes the main DNS go down :/, bacause this, here a lot of people use Google’s DNS.

    Is your problem also solved with my solution ? ..anything I can try to help you with it.

    att. carlos.spohr

    Reply Report
  • st8ofmindz79 November 5, 2014

    Good point!
    Interestingly enough it’s nameserver 4.2.2.2 which seems to be the culprit.
    When that is first in the list the request fails but if it’s second after 8.8.8.8 everything is good (obviously because it never gets to it).

    I removed 4.2.2.2 and replaced it with the one you listed 66.93.87.2 as those both seem to work.

    nameserver 8.8.8.8
nameserver 66.93.87.2

    Thanks!

    Reply Report
Submit an Answer

Looking for something else?

Ask a new question Search for more help