2

I'm struggling to do a composer update, everytime I try to I get the following error:

[Composer\Downloader\TransportException]
The "https://packagist.org/p/provider-2013%24442e1d5fa0fdbf77855cc363b02499 4a3e92a2f5099e5138b9c5777ae486703c.json" file could not be downloaded: failed to open stream: HTTP request failed!

I am in a new location so it may be an issue with the wifi connection or a firewall on the router, although I do not have control over these things, nor do I know how to confirm if this is the case. I've suggested it here just as a possibility.

One thing I have found is that it does NOT seem to be related to using composer, merely loading the packagist.org url in the browser is very slow.

To try and investigate this further I did a verbose curl, the output of which is here:

curl -Ov "https://packagist.org/p/provider-2016%24e91d8a4de280998eb052b8c02ed0533b247e992c67ab15cfcb3f5aee95f4839d.json" 
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
*   Trying 144.217.203.53...
*   Trying 2607:5300:60:7113::3...
* Immediate connect fail for 2607:5300:60:7113::3: No route to host
* Connected to packagist.org (144.217.203.53) port 443 (#0)
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
* TLS 1.2 connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
* Server certificate: packagist.org
* Server certificate: DigiCert SHA2 Secure Server CA
* Server certificate: DigiCert Global Root CA
> GET /p/provider-2016%24e91d8a4de280998eb052b8c02ed0533b247e992c67ab15cfcb3f5aee95f4839d.json HTTP/1.1
> Host: packagist.org
> User-Agent: curl/7.49.1
> Accept: */*
> 
  0     0    0     0    0     0      0      0 --:--:--  0:00:01 --:--:--     0< HTTP/1.1 200 OK
< Server: nginx
< Date: Tue, 23 May 2017 12:31:47 GMT
< Content-Type: application/json
< Content-Length: 2080782
< Connection: keep-alive
< Vary: Accept-Encoding
< Last-Modified: Tue, 23 May 2017 12:12:30 GMT
< Vary: Accept-Encoding
< ETag: "5924272e-1fc00e"
< Accept-Ranges: bytes
< 
{ [16093 bytes data]
 39 2032k   39  799k    0     0   7677      0  0:04:31  0:01:46  0:02:45  6267^C

It seems to fail a few times and then finally starts working, although estimated time is 4 minutes and 31 seconds which is obviously not what you would expect for a 2MB file.

I've done alot of Googling and there are examples of this error and similar all over the place, but none of them seem relevant.

I was originally using this within Vagrant and have been debugging on the assumption that it was Vagrant related for ages. But the slow connection via Curl and the browser has ruled this out and left me at a loss. Hopefully someone can shed some light.

Incase it makes any difference the two repositories i've been testing this on are both Laravel, 5.1 and 5.4 respectively.

John Mellor
  • 2,351
  • 8
  • 45
  • 79
  • it appears as though packagist is having major problems this morning. https://twitter.com/packagist/status/866952618349920257 – Jeff Puckett May 23 '17 at 16:03
  • Ah thanks, I looked through Twitter at the time but didn't see anything, maybe everyone was still asleep – John Mellor May 24 '17 at 02:16

0 Answers0