Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Is the issue in fetching the update information (drush refresh), or in downloading the actual update tarballs themselves? If the former then it is an update_status/core issue - if the latter, then we can help.
To sort out the problems with the downloading of tarballs via wget with drush from behind a proxy, you need to add the proxy server settings to your .wgetrc file.
On Windows, create a new file in your HOME path named "%HOMEDRIVE%%HOMEPATH%\.wgetrc"
On Linux/Cygwin create a new file in your home path named ~/.wgetrc
and add the following lines, where {PORT} is the port number of your proxy server:
Windows 10 user here behind a corporate firewall. Besides obtaining a wget.exe(google wget for windows), adding it to my PATH (system environment variables) I also had to to edit the .wgetrc located at C:/Users/YOURNAME/.wgetrc and add the following lines. (if you don't have a .wgetrc visit gnu.org)
Comments
Comment #1
moshe weitzman CreditAttribution: moshe weitzman commenteddrush_pm just uses update_status module for communicating with drupal.org. please ask there.
Comment #2
Anonymous (not verified) CreditAttribution: Anonymous commentedremoved
Comment #3
Owen Barton CreditAttribution: Owen Barton commentedIs the issue in fetching the update information (drush refresh), or in downloading the actual update tarballs themselves? If the former then it is an update_status/core issue - if the latter, then we can help.
Comment #4
Anonymous (not verified) CreditAttribution: Anonymous commentedremoved
Comment #5
chOP CreditAttribution: chOP commentedTo sort out the problems with the downloading of tarballs via wget with drush from behind a proxy, you need to add the proxy server settings to your .wgetrc file.
and add the following lines, where {PORT} is the port number of your proxy server:
Comment #6
anarcat CreditAttribution: anarcat commentedI think proxy settings could be considered as being outside the scope of Drush, @jacobwg - would that be sufficient for you?
(Does curl or php-curl support such configurations?)
Comment #7
Anonymous (not verified) CreditAttribution: Anonymous commentedremoved
Comment #8
moshe weitzman CreditAttribution: moshe weitzman commentedanother technique - http://reluctanthacker.rollett.org/node/114
Comment #9
decibel.places CreditAttribution: decibel.places commentedIn my case I do not need the username:password this works as my .wgetrc
where IP_ADDRESS is the IP number; and the port is 80
I also had to create C:\tmp for Drush and make it writeable
(Windows 7 32 bit behind a corporate firewall)
Comment #10
Anonymous (not verified) CreditAttribution: Anonymous commentedComment #11
NicholasSWindows 10 user here behind a corporate firewall. Besides obtaining a wget.exe(google wget for windows), adding it to my PATH (system environment variables) I also had to to edit the .wgetrc located at C:/Users/YOURNAME/.wgetrc and add the following lines. (if you don't have a .wgetrc visit gnu.org)