ConfigServer Community Forum

Posted: **14 Apr 2015, 01:13**

samething for me :

From OVH datacenter:

# traceroute download.configserver.com
traceroute to download.configserver.com (85.10.199.177), 30 hops max, 60 byte packets
 1  xxx.ip-192-99-168.net (192.99.168.xxx)  0.212 ms  0.118 ms  0.054 ms
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  * * *
 7  decix-gw.hetzner.de (80.81.192.164)  91.890 ms  91.931 ms  91.866 ms
 8  core1.hetzner.de (213.239.245.6)  94.258 ms  93.793 ms  92.385 ms
 9  core12.hetzner.de (213.239.245.253)  95.070 ms  94.964 ms core11.hetzner.de (213.239.245.249)  95.030 ms
10  juniper1.rz1.hetzner.de (213.239.245.50)  94.995 ms juniper2.rz1.hetzner.de (213.239.245.62)  94.973 ms juniper1.rz1.hetzner.de (213.239.245.182)  94.960 ms
11  hos-tr2.ex3k5.rz1.hetzner.de (213.239.255.38)  97.053 ms hos-tr1.ex3k5.rz1.hetzner.de (213.239.255.6)  96.933 ms hos-tr3.ex3k5.rz1.hetzner.de (213.239.237.134)  95.989 ms
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

From office:

Code: Select all

C:\Users\xxxxxxxxxxxxxxxxxxxxx-vous>tracert download.configserver.com

Détermination de l'itinéraire vers download.configserver.com [85.10.199.177]

  1     1 ms    <1 ms     1 ms  SVSHARE [xxxxxxxxxxxxxx]
  2     *        *        *     Délai d'attente de la demande dépassé.
  3    15 ms    23 ms    12 ms  10.170.177.33
  4    14 ms    18 ms    19 ms  216.113.122.149
  5     *       23 ms    18 ms  216.113.126.222
  6    19 ms    22 ms    20 ms  if-5-2.tcore2.NYY-New-York.as6453.net [216.6.99.29]
  7    24 ms    22 ms    28 ms  if-11-2.tcore1.NYY-New-York.as6453.net [216.6.99.2]
  8    29 ms    38 ms    42 ms  if-5-5.tcore1.NTO-New-York.as6453.net [216.6.90.6]
  9    58 ms    34 ms    40 ms  ae-9.r05.nycmny01.us.bb.gin.ntt.net [129.250.9.213]
 10     *        *        *     Délai d'attente de la demande dépassé.
 11   117 ms   105 ms   114 ms  ae-6.r21.frnkge03.de.bb.gin.ntt.net [129.250.3.181]
 12   103 ms   103 ms   105 ms  ae-2.r03.frnkge03.de.bb.gin.ntt.net [129.250.6.217]
 13   105 ms   102 ms   101 ms  hetzner-0.r03.frnkge03.de.ce.gin.ntt.net [213.198.72.230]
 14   101 ms   102 ms    99 ms  core4.hetzner.de [213.239.245.2]
 15   102 ms   106 ms   101 ms  core11.hetzner.de [213.239.245.34]
 16   111 ms   102 ms   103 ms  juniper1.rz1.hetzner.de [213.239.245.50]
 17   104 ms   105 ms   115 ms  hos-tr1.ex3k5.rz1.hetzner.de [213.239.255.6]
 18   105 ms   105 ms   104 ms  download.configserver.com [85.10.199.177]

thank you

Posted: **14 Apr 2015, 06:13**

Those of you whose traceroute gets as far as hetzner, have you actually tried disabling the ovh firewall on your server? We have had several people report that even though the traceroute showed the ping getting through to hetzner's network, disabling the ovh firewall allowed them to get all the way through to our server, which proved that it was ovh and not us or hetzner causing the issue in the first place.

Also be aware that doing a traceroute to the download server (if you are not blocked in any way in the first place) will get you temporarily blocked in our server's firewall.

If you want us to check whether we're blocking your IP address, please send a pm or email with your server's IP address.

Regards,
Sarah

Posted: **14 Apr 2015, 19:20**

Same problem to me !

I am using OVH server

Posted: **17 Apr 2015, 19:22**

today, the problem seems resolved.

it's working now.

Posted: **17 Apr 2015, 19:52**

Seems the problem is finally resolved as two of our servers running CSF that also had the OVH firewall active were able to update

Posted: **17 Apr 2015, 20:04**

I am still facing this issue from my singlehop server.

Unable to connect to https://download.configserver.com, retry in 300 seconds. An Upgrade button will appear here if new version is detected

Failed to determine the latest version of cmq

Failed to determine the latest version of cmc. An Upgrade button will appear here if new version is detected

I face this issue from SingleHop servers but fine with Softlayer Server.

Please help.

Posted: **17 Apr 2015, 23:44**

You'll need to whitelist 85.10.199.177 in whatever sort of firewall interface SingleHop offers you and then also submit to them a ticket requesting to have that IP unblocked.

For whatever reason, several server providers decided to add CSF's IP to their blocklists and the end result is this. You need to be the one to take action in order to speed up its resolution as SingleHop may not remove it otherwise.

Posted: **09 Nov 2016, 08:29**

I fixed it by setting URLGET = 1
"1" = HTTP::Tiny
"2" = LWP::UserAgent

If you have any reason to have LWP you coud set it back to your default after updating

ConfigServer Community Forum

update error last few days

Re: update error last few days

Re: update error last few days

Re: update error last few days

Re: update error last few days

Re: update error last few days

Re: update error last few days

Re: update error last few days

Re: update error last few days