Folding Forum

PS The server auto reset itself on Dec 27 at 23:59 pacific time, so the problem should now be resolved.

Edited: Had listed wrong server in reject mode.

Thank Vijay, got three WU's in a row, then constant 403's for the last 5-6 hours...

Initial 40ab; - Successfull: assigned 171.64.65.106
News from...
Loaded Queue successfully
Connecting to 65.106:8080
Couldn't send HTTP request
got status 403...

and still no alternatives assigned, does this server not have alternates?

Thanks and happy new year according to the Hijra calendar,

regards

smcpoland wrote:Thank Vijay, got three WU's in a row, then constant 403's for the last 5-6 hours...

Initial 40ab; - Successfull: assigned 171.64.65.106
News from...
Loaded Queue successfully
Connecting to 65.106:8080
Couldn't send HTTP request
got status 403...

and still no alternatives assigned, does this server not have alternates?

Thanks and happy new year according to the Hijra calendar,

regards

Could you tell me what you see when you send your web browser to http://171.64.65.106:8080 ? That will help debug this.

Hi Vijay,

I clicked the link you gave 106:8080 and I get

ERROR
Access Denied

--------------------------------------------------------------------------------

Access Denied by security policy
The security policy for your network prevents your request from being allowed at this time. Please contact your administrator if you feel this is incorrect.

Pretty standard Http 403 error.

Regards
Sean

I see that you're from Middle East ... so I'm afraid that your ISP might block accesses to FAH ...

We've seen one or two similar reports from people in the region of the world ...

Humm, not sure I agree, after all I've submitted over 400 WU's in the last month or so and my CPU clients are working fine...

and I've just completed another one that comes in every now and then...the blocking we use here in Saudi is very clear when it fails. and this isn't it...

Having researched 403 it is very clearly a denial http://en.wikipedia.org/wiki/HTTP_403.

It would e nice to sort this out as I was just getting back into the swing of things...

Well, from here, both http://171.64.65.106/ and http://171.64.65.106:8080/ work so it's not something at Stanford, it's something somewhere on "your" network (whatever that means). Perhaps you've always used the former URL rather than the latter. Does it work for you?

There was a cable cut between Africa and Europe last week. Do you suppose that's blocking access? Try "tracert 171.64.65.106" (without the quotes).

Have you tried contacting one of your network's administrators?

Some countries block all access to port 8080. Others block explicit IP addresses.