SETI, Cannot connect to smokeball.dns2go.com

[EglsFly]

I have my SETI@Home proxy to connect to: smokeball.dns2go.com, on port: 5517
Connection seems to be lost to this server?

 

[minendo]

Able to connect just fine here.

 

[Smoke]

EglsFly,

The Q is working but I don't see a "queue" with your account's name? I had to disable the way NEW ACCOUNTS are handled due to hackers (read cheaters dumping their duplicate WUs through my Q).

I, now due to this cheating, have to clear each new user for them to gain access.

I believe your account was already established ... I wonder what happened? Has it been a long time since you sent in WUs? I think after some period of inactivity, SetiQueue automatically drops CLIENTS. I see your last submitted WU was on: Wed Jul 7 23:24:18 2004

Send me a PM and I'll work it out for you.

 

[Rattledagger]

The queue has a setting of "Obsolete clients & pending WU after" 7 days...
If you not manually sets one client for every queue as permanent the queue is deleted if haven't been accessed for 8 days...

Anyway, it seems Berkeley now has flat-lined around 9 Mbit, since the BOINC-version still is up and running this is probably the current usage without "classic"...
The "server status page" seems to be stuck also.

 

[Freewolf]

the seti 1 servers seems to be having a problem, results are starting to backup in our q.

 

[Dalephi]

I am not able send anything either. Glad it is not just me.

 

[jdiddy]

Originally posted by: Dalephi
I am not able send anything either. Glad it is not just me.

Ditto I did'nt see anything else about this on the first page right away.