[wp-trac] [WordPress Trac] #39594: Multisite Upgrade Network - cURL Attempting Port 443 on HTTP

[WordPress Trac]

#39594: Multisite Upgrade Network - cURL Attempting Port 443 on HTTP
--------------------------------+-----------------------------
 Reporter:  michael.ecklund     |      Owner:
     Type:  defect (bug)        |     Status:  new
 Priority:  normal              |  Milestone:  Awaiting Review
Component:  Networks and Sites  |    Version:  4.7.1
 Severity:  normal              |   Keywords:
  Focuses:  multisite           |
--------------------------------+-----------------------------
 The "Upgrade Network" utility fails to perform it's tasks correctly in
 `4.7.1`. cURL is connecting to each subsite through HTTP, however, the
 port it's attempting to use is 443 and not 80.

 All sites in this network are HTTP, so everything should be done through
 port 80.

 '''Here's how I discovered this:'''

 Update from `4.7` -> `4.7.1` through the admin interface.
 Immediately there after, Upgrade Network.

 {{{
 Warning! Problem updating http://domain.com. Your server may not be able
 to connect to sites running on it. Error message: cURL error 7: Failed to
 connect to domain.com port 443: Connection refused
 }}}


 I'm aware of connections refused on port 443. (Firewall rules) The problem
 is: It shouldn't even be attempting to connect to port 443. All the sites
 in the network are HTTP.

 I've tested the "Upgrade Network" utility on `4.7` using another copy of
 the SAME exact network on the SAME exact server. It upgrades all the sites
 just fine.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/39594>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform