24x7serversecurity

Active Member
Aug 31, 2015
39
6
8
India
cPanel Access Level
Root Administrator
Is there any issue currently with cPanel mirrors? I am trying to install cPanel/WHM on a server and the process is too slow than usual. Sometimes I get errors like below:

(FATAL): The system could not fetch the updatenow.static.asc file.

Any cPanel Admin online?
 

BasicLink SA

Member
Aug 30, 2011
13
0
51
cPanel Access Level
DataCenter Provider
Last edited by a moderator:

Kailash1

Well-Known Member
Nov 27, 2006
259
6
168
cPanel Access Level
Root Administrator
Twitter
I am having same problem. Got a message that cPanel update was failed. Running manual upcp remains at:

[2016-06-09 01:09:15 -0600] Retrieving and staging /cpanelsync/11.56.0.24/cpanel/scripts/updatenow.static.bz2
[2016-06-09 01:09:15 -0600] Using mirror '72.29.88.74' for host 'httpupdate.cpanel.net'.

No output after last line.
 

Brooky A

Member
Sep 16, 2015
24
5
53
UK
cPanel Access Level
Root Administrator
The upgrade tool in WHM is failing too hanging at 2%..

Server is in London Data Center.

[2016-06-09 03:16:19 -0400] Detected version '11.56.0.22' from version file.
[2016-06-09 03:16:19 -0400] Running version '11.56.0.24' of updatenow.
[2016-06-09 03:16:19 -0400] Using mirror '216.38.56.98' for host 'httpupdate.cpanel.net'.
[2016-06-09 03:16:19 -0400] Using mirror '208.43.129.162' for host 'httpupdate.cpanel.net'.
[2016-06-09 03:16:37 -0400] Using mirror '206.130.99.76' for host 'httpupdate.cpanel.net'.
[2016-06-09 03:16:52 -0400] Using mirror '67.159.2.2' for host 'httpupdate.cpanel.net'.
[2016-06-09 03:16:53 -0400] Using mirror '69.72.212.11' for host 'httpupdate.cpanel.net'.
[2016-06-09 03:20:04 -0400] Using mirror '67.159.2.2' for host 'httpupdate.cpanel.net'.
[2016-06-09 08:23:24 +0100] Using mirror '208.43.129.162' for host 'httpupdate.cpanel.net'.
[2016-06-09 08:23:25 +0100] Using mirror '72.29.88.74' for host 'httpupdate.cpanel.net'.
...
 
Last edited:

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,884
2,254
463
Hello,

A temporary issue with our mirrors was addressed by our system administration team on June 9th, 2016 to address this issue. Thank you to everyone who took the time to report this on our forums.