I cannot wiggle

Martin Dann said:

I cannot access the Wiggle web site, It is the only web site that is
causing me problems, I have tried with various browsers on both my
computers.

The only thing that has changed since I last used them is going from
single computer dial-up to home network broadband. Does anyone have any
suggestions?

Martin.

If you are on BT broadband there is a lot of problems accessing some web
pages at the moment, but BT have not admitted the fault yet.

--
Regards, Kenneth.
www.kmiles.co.uk

Kenneth Miles said:

Martin Dann said:

I cannot access the Wiggle web site, It is the only web site that is
causing me problems, I have tried with various browsers on both my

Quoted message said:

If you are on BT broadband there is a lot of problems accessing some web
pages at the moment, but BT have not admitted the fault yet.

I am on virgin.net, when I try to load a wiggle page, a browser takes a
few minutes then delivers an empty page which it believe is just text.
This happens on both my windows PC and my other computer.

Martin.

"Kenneth Miles" <[email hidden]> wrote in message
news:[email hidden]...

Quoted message said:

Martin Dann said:

I cannot access the Wiggle web site, It is the only web site that is
causing me problems, I have tried with various browsers on both my
computers.
Martin.

If you are on BT broadband there is a lot of problems accessing some web
pages at the moment, but BT have not admitted the fault yet.

I can access Wiggle through BT Broadbnad with no problems.

-=V=-

Martin Dann said:

Quoted message said:

I am on virgin.net, when I try to load a wiggle page, a browser takes a
few minutes then delivers an empty page which it believe is just text.
This happens on both my windows PC and my other computer.

No problems getting Wiggle on NTL.
Iain

In article <[email hidden]>

Martin Dann said:

I cannot access the Wiggle web site, It is the only web site that is
causing me problems, I have tried with various browsers on both my
computers.

The only thing that has changed since I last used them is going from
single computer dial-up to home network broadband. Does anyone have any
suggestions?

http://www.openproxies.com/

Pick a proxy that's not on port 80, plug it into your browser and try
again - if it works then the problem is with your ISP's webcache
servers.
I just tried 201.17.148.34 port 3128 and it worked (slowly - it is in
Brazil after all :-).

I see you're with ntl, who are known to have webcache problems, to the
extent that someone has written a website about it:

http://homepage.ntlworld.com/robin.d.h.walker/cmtips/trancache.html

See the bit about "How to sidestep the transparent web caches".

Martin Dann said:

Kenneth Miles said:

Martin Dann said:

I cannot access the Wiggle web site, It is the only web site that is
causing me problems, I have tried with various browsers on both my

Quoted message said:

If you are on BT broadband there is a lot of problems accessing some
web pages at the moment, but BT have not admitted the fault yet.

I am on virgin.net, when I try to load a wiggle page, a browser takes
a few minutes then delivers an empty page which it believe is just
text. This happens on both my windows PC and my other computer.

I'm on virgin.net and the Wiggle site is working for me now.

~PB

"Kenneth Miles" <[email hidden]> wrote in message
news:[email hidden]...

Quoted message said:

Martin Dann said:

I cannot access the Wiggle web site, It is the only web site that is
causing me problems, I have tried with various browsers on both my
computers.

The only thing that has changed since I last used them is going from
single computer dial-up to home network broadband. Does anyone have any
suggestions?

Martin.

If you are on BT broadband there is a lot of problems accessing some web
pages at the moment, but BT have not admitted the fault yet.

I'm on BT broadbean and (frantically looks for lump of wood to pet) have no
problem. Wiggle is fine for me.

In article <[email hidden]>, wafflycat

w*a*ff£y£cat*@£btco*nn£ect.com said:

Wiggle is fine for me.

Works fine here on Pipex Homecall 8mb on an ancient Risc PC with
Oregano as the browser.

hth

vernon said:

"Kenneth Miles" <[email hidden]> wrote in message
news:[email hidden]...

Quoted message said:

Martin Dann said:

I cannot access the Wiggle web site, It is the only web site that is
causing me problems, I have tried with various browsers on both my
computers.
Martin.

If you are on BT broadband there is a lot of problems accessing some web
pages at the moment, but BT have not admitted the fault yet.

I can access Wiggle through BT Broadbnad with no problems.

-=V=-

It seems to be where you are in the country, the support newsgroup is
busy with people who have this problem. I can get wiggle but have
trouble with metcheck and google search.

--
Regards, Kenneth.
www.kmiles.co.uk

Rob Morley said:

http://www.openproxies.com/

Fine for looking at a site but I'd rather stick hot pins in my eyes
than login, or enter credit card details, when I'm going through some
random open proxy.

-Alex

In article <[email hidden]>

Alex said:

Rob Morley said:

http://www.openproxies.com/

Fine for looking at a site but I'd rather stick hot pins in my eyes
than login, or enter credit card details, when I'm going through some
random open proxy.

Absolutely, I only offered it as a quick way of checking whether the
problem was proxy related - the open proxies listed are generally too
slow for normal use anyway. The other link I gave has instructions on
how to select a working proxy within ntl or Blueyonder when the
automatic one fails.

Kenneth Miles said:

vernon said:

"Kenneth Miles" <[email hidden]> wrote in message
news:[email hidden]...

Quoted message said:

Martin Dann wrote:
> I cannot access the Wiggle web site, It is the only web site that is
> causing me problems, I have tried with various browsers on both my
> computers.
> Martin.
If you are on BT broadband there is a lot of problems accessing some web
pages at the moment, but BT have not admitted the fault yet.

I can access Wiggle through BT Broadbnad with no problems.

-=V=-

It seems to be where you are in the country, the support newsgroup is
busy with people who have this problem. I can get wiggle but have
trouble with metcheck and google search.

I helped a friend out the other night with his BT connection. It was all
down to DNS. I think they are retiring/consolidating their DNS
servers.

If this takes you to Wiggle: http://80.243.188.35/ but you cannot go to
http://www.wiggle.co.uk then you have to change your DNS servers!

HTH

Noel

On 30 Nov 2006 07:35:04 -0800

Alex said:

Rob Morley said:

http://www.openproxies.com/

Fine for looking at a site but I'd rather stick hot pins in my eyes
than login, or enter credit card details, when I'm going through some
random open proxy.

Open proxies are bad. But not for that reason. They *cannot*
decrypt secure (https) traffic passing through. That's what SSL
certificates are all about. That's also why you should always
check the certificate thoroughly when supplying sensitive data
to any site: it's the one thing that can't be forged.

--
Nick Kew

Application Development with Apache - the Apache Modules Book
http://www.apachetutor.org/

Nick Kew said:

On 30 Nov 2006 07:35:04 -0800

Alex said:

Rob Morley said:

http://www.openproxies.com/

Fine for looking at a site but I'd rather stick hot pins in my eyes
than login, or enter credit card details, when I'm going through some
random open proxy.

Open proxies are bad. But not for that reason. They *cannot*
decrypt secure (https) traffic passing through. That's what SSL
certificates are all about. That's also why you should always
check the certificate thoroughly when supplying sensitive data
to any site: it's the one thing that can't be forged.

True, but badly implemented sites often return the cookie over HTTP
after login, rather than HTTPS. And require subsequent submission of
that cookie over HTTP.

Sure you may pass your login credentials over the HTTPS link, after
you've checked that the SSL certificate does belong to the real site,
but if they can snoop the cookie that's passed over the insecure HTTP
link then they may have access to that very same information on the
site.

So, even by checking the validity of the SSL certificate you can still
get bitten in the [censored].

-Alex

"Pete Biggs" <[email hidden]> wrote in
message news:[email hidden]...

Quoted message said:

Martin Dann said:

Kenneth Miles said:

Martin Dann wrote:
> I cannot access the Wiggle web site, It is the only web site that is
> causing me problems, I have tried with various browsers on both my

Quoted message said:

If you are on BT broadband there is a lot of problems accessing some
web pages at the moment, but BT have not admitted the fault yet.

I am on virgin.net, when I try to load a wiggle page, a browser takes
a few minutes then delivers an empty page which it believe is just
text. This happens on both my windows PC and my other computer.

I'm on virgin.net and the Wiggle site is working for me now.

ditto
peter

Noel said:

Kenneth Miles said:

vernon said:

"Kenneth Miles" <[email hidden]> wrote in message
news:[email hidden]...
> Martin Dann wrote:
>> I cannot access the Wiggle web site, It is the only web site that is
>> causing me problems, I have tried with various browsers on both my
>> computers.
>> Martin.
> If you are on BT broadband there is a lot of problems accessing some web
> pages at the moment, but BT have not admitted the fault yet.
>
I can access Wiggle through BT Broadbnad with no problems.

-=V=-

It seems to be where you are in the country, the support newsgroup is
busy with people who have this problem. I can get wiggle but have
trouble with metcheck and google search.

I helped a friend out the other night with his BT connection. It was all
down to DNS. I think they are retiring/consolidating their DNS
servers.

If this takes you to Wiggle: http://80.243.188.35/ but you cannot go to
http://www.wiggle.co.uk then you have to change your DNS servers!

But I cannot find out how to change DNS servers on the BT home hub, from
what I can gather it is automatic.

--
Regards, Kenneth.
www.kmiles.co.uk

In article <[email hidden]>

Kenneth Miles said:

Noel said:

Kenneth Miles said:

vernon wrote:
> "Kenneth Miles" <[email hidden]> wrote in message
> news:[email hidden]...
>> Martin Dann wrote:
>>> I cannot access the Wiggle web site, It is the only web site that is
>>> causing me problems, I have tried with various browsers on both my
>>> computers.
>>> Martin.
>> If you are on BT broadband there is a lot of problems accessing some web
>> pages at the moment, but BT have not admitted the fault yet.
>>
> I can access Wiggle through BT Broadbnad with no problems.
>
> -=V=-
>
>
It seems to be where you are in the country, the support newsgroup is
busy with people who have this problem. I can get wiggle but have
trouble with metcheck and google search.

I helped a friend out the other night with his BT connection. It was all
down to DNS. I think they are retiring/consolidating their DNS
servers.

If this takes you to Wiggle: http://80.243.188.35/ but you cannot go to
http://www.wiggle.co.uk then you have to change your DNS servers!

But I cannot find out how to change DNS servers on the BT home hub, from
what I can gather it is automatic.

If the hub runs a DNS proxy and you can't change the servers at the hub
you should be able to set them manually on each PC.

Rob Morley wrote:
[wiggle problems]

Quoted message said:

I just tried 201.17.148.34 port 3128 and it worked (slowly - it is in
Brazil after all :-).

Ok this works now.

Quoted message said:

I see you're with ntl, who are known to have webcache problems, to the
extent that someone has written a website about it:

http://homepage.ntlworld.com/robin.d.h.walker/cmtips/trancache.html

See the bit about "How to sidestep the transparent web caches".

I tried his, the first proxy failed with the same symptons as no proxy,
the second worked perfectly. (I assume the no proxy uses the first proxy
server or similar).

Also as per Noel's suggestion, and a reply from wiggle, using the
numeric address 80.243.188.35 (without proxies) also works perfectly.

Wiggle recently changed ISPs, and the new numeric IP has not filtered
through to some of my DNSes.

Martin.

In article <[email hidden]>
Martin Dann <[email hidden]> wrote:
<snip>

Quoted message said:

I tried his, the first proxy failed with the same symptons as no proxy,
the second worked perfectly. (I assume the no proxy uses the first proxy
server or similar).

If you don't select a non-port-80 proxy your connection will go through
the default proxy for your area, because all port 80 traffic does -
that's why they're called transparent proxies. If there are multiple
proxies running under a balancing scheme you may find that you get a
connection or not depending on which server your request is routed
through - the obvious way to split the load on caching proxies puts all
traffic for a particular site through the same server, so websites
served by one proxy can be working fine while those served by another
will be inaccessible. If one of your ISP's local proxies goes down you
can reroute through another local one by setting its non-port-80 port
(e.g. 3128, 8080) explicitly in your proxy settings - it should connect
OK but won't have anything pre-cached because that server doesn't
normally serve that bit of internet.

Quoted message said:

Also as per Noel's suggestion, and a reply from wiggle, using the
numeric address 80.243.188.35 (without proxies) also works perfectly.

Wiggle recently changed ISPs, and the new numeric IP has not filtered
through to some of my DNSes.

That can be a problem if you're behind a caching DNS proxy that doesn't
refresh frequently. It can be worth switching DNS servers to get around
the problem until your regular servers catch up. These are the DNS
servers of Level 3 Inc., a major US network provider, that appear to be
open for general use:

4.2.2.1
4.2.2.2
4.2.2.3
4.2.2.4
4.2.2.5
4.2.2.6