Update problem [fixed]

Boen, Jan -- on Mar. 3 2006

I'm trying to update my servers to the latest version but get the following error:

Download updated scripts Purging old staging files...

Unable to get http://www.yetanothercommunitysystem.com/yacs/scripts/fetch.php?script=footprints.php. Please configure again.

All scripts

Any idea what's wrong? This happens on www.sbv54.net/sbv54 and www.sbv54.net/keva

Thanks

Jan

Page bottom

Fernand from Paris 1287 posts	on Mar. 4 2006 Hello Jan, Is it the first time you update YACS on this ISP ?
Bernard from nearby-an-airport Associate, 6796 posts	on Mar. 4 2006 Jan: your ISP has probably disabled access from your web server to other web servers, including the reference YACS site. The first thing to do is to check the security policy used by this ISP. Many of them prevent the creation of TCP sockets from within their data centers. Also, they may have installed a proxy to control outbound connections. If this is the case, provide related information (proxy address, account and password) to YACS in the main configuration panel. This should be enough to pass through. A number of YACS powerful features are relying on accessing outbound servers, including at least: automatic update of the software, gathering of RSS feeds, posting by e-mail
JBN 85 posts	inspired from Bernard on Mar. 6 2006 Bernard: This is the reply form my hosting service (siteground.com) Hello, Outbound connections to port 80 are allowed on the server, we had no problems connecting to a number of hosts that have a service running on port 80. Connecting to www.yetanothercommunitysystem.com is not possible indeed, however, this is not caused by us. You may want to contact the administrators of yetanothercommunitysystem.com and have them check if they have blocked traffic coming from 207.218.208.7 -- this is your IP address with SiteGround. Please do not hesitate to contact us again if you have any other questions or comments. Best Regards, Kenny Support Team Supervisor SiteGround.com
Bernard from nearby-an-airport Associate, 6796 posts	inspired from JBN on Mar. 6 2006 JBN: this is the most curious thing I have heard for a long time... Do you think we should add a traceroute facility to YACS?
JBN 85 posts	inspired from Bernard on Mar. 6 2006 Bernard: I can launch a lookup from my ISP control panel and the lookup gives the following result: DNS Results: www.yetanothercommunitysystem.com is an alias for yetanothercommunitysystem.com. yetanothercommunitysystem.com has address 213.186.33.2 Zone Information: Host www.yetanothercommunitysystem.com not found: 9(NOTAUTH) ; Transfer failed.
Bernard from nearby-an-airport Associate, 6796 posts	inspired from JBN on Mar. 6 2006 JBN: This means that your ISP knows the IP address of yetanother..., but cannot dump zone information from the DNS server. Everything seems normal up to there... The next step is probably to check that yetanother... is reachable from the console of the ISP. Anu ping or traceroute command?
JBN 85 posts	inspired from Bernard on Mar. 7 2006 Bernard: This is what Siteground says Hello, I have just flushed our firewall completely, to verify that all sorts of traffic are allowed. Here is the traceroute output from our server to the yetanothercommunitysystem.com host: traceroute to yetanothercommunitysystem.com (213.186.33.2), 30 hops max, 38 byte packets 1 207.218.208.1 (207.218.208.1) 0.238 ms 0.152 ms 0.188 ms 2 ivhou-207-218-245-8.ev1.net (207.218.245.8) 0.395 ms 1.775 ms 0.316 ms 3 ivhou-207-218-223-7.ev1.net (207.218.223.7) 0.521 ms 0.413 ms 0.441 ms 4 216.200.251.gate.mfnx.net (216.200.251.49) 1.273 ms 32.210 ms 1.235 ms 5 so-5-1-0.mpr1.atl6.us.above.net (64.125.29.61) 13.732 ms 13.844 ms 13.732 ms 6 so-0-0-0.mpr2.atl6.us.above.net (64.125.27.50) 13.854 ms 13.845 ms 13.733 ms 7 so-3-2-0.cr1.dca2.us.above.net (64.125.27.65) 24.849 ms 24.839 ms 25.100 ms 8 so-2-0-0.cr1.lhr3.uk.above.net (64.125.27.58) 96.557 ms 96.548 ms 96.685 ms 9 pos1-0.mpr1.lhr1.uk.above.net (208.184.231.173) 96.431 ms 96.548 ms 96.308 ms 10 pos0-0.pr1.lhr1.uk.above.net (208.184.231.70) 96.432 ms 96.546 ms 96.432 ms 11 sw1.tc.lon (195.66.224.220) 104.553 ms 104.541 ms 104.553 ms 12 p19-10-m1.routers.ovh.net (213.251.130.163) 105.428 ms 105.041 ms 105.053 ms 13 * * * It is visible, that traffic can reach 213.251.130.163, but cannot go any further. It seems ovh.com are blocking traffic from our IP address. Please have them double-check this, and ask for a traceroute output from their host to 207.218.208.7. Best Regards, Kenny Support Team Supervisor SiteGround.com
Bernard from nearby-an-airport Associate, 6796 posts	inspired from JBN on Mar. 7 2006 JBN: The issue has been forwarded to OVH support for further analysis.
JBN 85 posts	inspired from Bernard on Mar. 13 2006 Bernard: Any progress on OVH side?
Bernard from nearby-an-airport Associate, 6796 posts	inspired from JBN on Mar. 13 2006 JBN: I have received a side message related to solved issues on their ftp service. This is not directly related to your problem, but maybe it could help to check if the problem stil exists?

10 comments

Rate this page
Posted by JBN on Mar. 3 2006, commented by Bernard on Mar. 3 2006, (popular)