|
Ticket ID: SIXXS #1186262 Ticket Status: User PoP: (not applicable)
www.sixxs.net connection issues to 193.109.122.244
![[us]](/s/countries/us.gif) Shadow Hawkins on Thursday, 27 August 2009 00:57:55
This has nothing to do with the SixXS service, but the website itself.
I'm having difficulties connecting to www.sixxs.net (over IPv4). Receiving an apparently blank page, though further investigation shows a HTTP 503 (Service Unavailable) being returned, along with "Server: WebProxy/5.0". Successfully reproduced on separate client computers and networks.
nslookup on www.sixxs.net returned 2 IPv4 addresses, along with 1 IPv6:
Non-authoritative answer:
Name: www.m.sixxs.net
Addresses: 2001:838:1:1:210:dcff:fe20:7c7c
193.109.122.244
213.204.193.2
Aliases: www.sixxs.net
Directly connecting to 213.204.193.2 works. (It returns a "is not an official SixXS domain" message.) However, once assigned to the 193.109.122.244 address, I only receive the HTTP 503 responses.
Assuming there is a problem with one of the SixXS web servers, or the DNS entries need to be updated.
State change: user
The state of this ticket has been changed to user
www.sixxs.net connection issues to 193.109.122.244
Receiving an apparently blank page, though further investigation shows a HTTP 503 (Service Unavailable) being returned, along with "Server: WebProxy/5.0"
I can only assume you are running a local proxy which causes that.
Directly connecting to 213.204.193.2 works. (It returns a "is not an official SixXS domain" message.) However, once assigned to the 193.109.122.244 address, I only receive the HTTP 503 responses.
Which exact URL are you trying to contact?
www.sixxs.net connection issues to 193.109.122.244
Shadow Hawkins on Thursday, 27 August 2009 18:41:35
No, no local proxy. As mentioned, I was able to reproduce this on completely separate computers and networks.
The URL I was using was simply http://www.sixxs.net . Depending upon which IP was returned to my DNS request, sometimes it worked, and sometimes it didn't.
The issue does appear to be resolved, however. Both IPs are now returning valid results.
www.sixxs.net connection issues to 193.109.122.244
We really do not run any software that would return "Server: WebProxy/5.0", Apache does not do that. Googling a bit, reveals that there is a product called BlueCoat WebProxy which is already in version 6.0 (and there are various 5.x editions which have a vulnerability (CVE-2005-4085). It seems that the prime use of these proxies, and for that matter the sole existence for BlueCoat is "WAN Optimization & Secure Web Gateway", aka systems that get inserted into your network and hijack your TCP connections.
As such, contact your local network operators...
|
![[ch]](/s/countries/ch.gif)
on Thursday, 27 August 2009 09:14:36
Posting is only allowed when you are