171.64.65.105/171.67.108.142 Could't authent. AS response

Moderators: Site Moderators, FAHC Science Team

Post Reply
artoar_11
Posts: 657
Joined: Sun Nov 22, 2009 8:42 pm
Hardware configuration: AMD R7 3700X @ 4.0 GHz; ASUS ROG STRIX X470-F GAMING; DDR4 2x8GB @ 3.0 GHz; GByte RTX 3060 Ti @ 1890 MHz; Fortron-550W 80+ bronze; Win10 Pro/64
Location: Bulgaria/Team #224497/artoar11_ALL_....

171.64.65.105/171.67.108.142 Could't authent. AS response

Post by artoar_11 »

Old client - v.6.41r2 (GTX 460 + core_15).It worked well until this morning :)

Code: Select all

[06:03:12] + Attempting to get work packet
[06:03:12] Passkey found
[06:03:12] - Will indicate memory of 8168 MB
[06:03:12] Gpu type=3 species=20.
[06:03:12] - Connecting to assignment server
[06:03:12] Connecting to http://assign-GPU.stanford.edu:8080/
[06:03:13] Posted data.
[06:03:13] Initial: 0000; + Could not authenticate Assignment Server response
[06:03:13] Connecting to http://assign-GPU.stanford.edu:80/
[06:03:14] Posted data.
[06:03:14] Initial: 0000; + Could not authenticate Assignment Server 2 response
[06:03:14] + Couldn't get work instructions.
[06:03:14] - Attempt #8  to get work failed, and no other work to do.
Waiting before retry.
[06:04:53] ***** Got a SIGTERM signal (2)
[06:04:53] Killing all core threads
toTOW
Site Moderator
Posts: 6309
Joined: Sun Dec 02, 2007 10:38 am
Location: Bordeaux, France
Contact:

Re: 171.64.65.105/171.67.108.142 Could't authent. AS respons

Post by toTOW »

Last time I had this issue (v6 Linux client), I had to upgrade to v7 to get work again ...

This error is probably the v6 version of this one reported many times in this thread : viewtopic.php?f=18&t=27962
Image

Folding@Home beta tester since 2002. Folding Forum moderator since July 2008.
Post Reply