Roots Discourse

Error retrieving WP-CLI tab completions

Fresh Trellis/bedrock install. At vagrant up --provision.
Python 2.7.10

TASK [wp-cli : Retrieve WP-CLI tab completions] ********************************
System info:
  Ansible 2.7.13; Vagrant 2.2.6; Darwin
  Trellis Head
---------------------------------------------------
non-zero return code
fatal: [default]: FAILED! => {"changed": true, "cmd": ["curl", "-4Ls", "https://raw.githubusercontent.com/wp-cli/wp-cli/v2.3.0/utils/wp-completion.bash", "-o", "/tmp/wp-completion-2.3.0.bash"], "delta": "0:00:00.032848", "end": "2019-11-13 10:19:17.822026", "rc": 7, "start": "2019-11-13 10:19:17.789178", "stderr": "", "stderr_lines": [], "stdout": "", "stdout_lines": []}

Does it consistently happen?

The URL definitely exists so it could have been a network issue with you?

1 Like

Thank you for the answer!

I tried several times with Trellis/Bedrock from scratch and the error persist. Any petition to raw.githubusercontent.com from here is refused and my network seems to be OK (I have Internet with no problems. I have no proxies).

$ curl https://raw.githubusercontent.com/wp-cli/wp-cli/v2.3.0/utils/wp-completion.bash
curl: (7) Failed to connect to raw.githubusercontent.com port 443: Connection refused

52

Why does this happen? Any ideas?

For the moment, I found a workaround here: https://stackoverflow.com/a/18049842/2986401

So, I changed this line:

To

wp_cli_completion_url: "http://cdn.jsdelivr.net/gh/wp-cli/wp-cli/v{{ wp_cli_version }}/utils/wp-completion.bash"

It works.

1 Like

Ok, this is the situation: The Spanish government and the judicial system, as a result of the riots in Catalonia, ordered subverting the DNS to raw.githubusercontent.com, which from the Spanish ISPs resolves to 127.0.0.1

I have changed the DNS for those of cloudflare and everything works again. But everything is that my ISP, in a telephone consultation, told me that it was not his responsibility because the ping itself was returned.

I have lost days of work for this government fudge :face_with_symbols_over_mouth:

2 Likes

:slightly_frowning_face: that’s really frustrating. Thanks for the update

1 Like

Hi @aitor,

can you explain your solution a bit more? What was the change you applied after realizing the problem was the wrong 127.0.0.1 resolution?

Ojiplático me dejas…

Oh! I see, changing the DNS of my network connection. Ok, let’s try it.

Thank you!!

1 Like

Cloudflare’s DNSs did the trick

1.1.1.1
1.0.0.1
2606:4700:4700::1111
2606:4700:4700::1001
1 Like