-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Account Websocket closed, UNACCEPTABLE #319
Comments
I've gone to the URL noted above from the same machine, using Chrome, and Chrome pulls up the URL just fine. |
Please provide full system info, client info, network info and hardware used. Any special network set up? What type of connectivity, etc. the more info you can provide more chance we can get to the bottom of this and help you |
[cid:a4d27620-68cd-4154-a88c-840f15b67bdb]
Internet connection is 1Gbps direct, dedicated fiber. It's all managed by service provider using an on-site Cisco router that is bridged to a Fortinet firewall.
The machine is connected using ethernet. Video card is an NVidia P2000 w/6GB dedicated RAM, and 32GB shared RAM. The client information was all available from the logs, including all the specific capabilities of my hardware (CUDA, OpenCL, FLOPS, ...)
…________________________________
From: muziqaz ***@***.***>
Sent: Saturday, January 4, 2025 2:57 PM
To: FoldingAtHome/fah-client-bastet ***@***.***>
Cc: Daniel Lynes ***@***.***>; Author ***@***.***>
Subject: Re: [FoldingAtHome/fah-client-bastet] Account Websocket closed, UNACCEPTABLE (Issue #319)
You don't often get email from ***@***.*** Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>
Please provide full system info, client info, network info and hardware used. Any special network set up? What type of connectivity, etc. the more info you can provide more chance we can get to the bottom of this and help you
—
Reply to this email directly, view it on GitHub<#319 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAGNJVUSCJLMMC367EPT3332JA4LXAVCNFSM6AAAAABUTL5POWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNZRGM4TMOJVGA>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Getting spammed with the following logs:
19:48:49:I1:Account websocket closed: UNACCEPTABLE msg=
19:48:49:I1:OUT3579:> GET https://api.foldingathome.org/machine/................. HTTP/1.1
19:48:50:I1:OUT3579:< HTTP/1.1 200 HTTP_OK
19:48:50:I1:OUT2:> GET wss://node1.foldingathome.org/ws/client HTTP/1.1
19:48:50:I1:OUT2:< HTTP/1.1 101 HTTP_SWITCHING_PROTOCOLS
19:48:50:I1:Logging into node account
19:48:50:I1:Account websocket closed: UNACCEPTABLE msg=
19:48:50:I1:OUT3580:> GET https://api.foldingathome.org/machine/................. HTTP/1.1
19:48:51:I1:OUT3580:< HTTP/1.1 200 HTTP_OK
19:48:51:I1:OUT2:> GET wss://node1.foldingathome.org/ws/client HTTP/1.1
19:48:51:I1:OUT2:< HTTP/1.1 101 HTTP_SWITCHING_PROTOCOLS
19:48:51:I1:Logging into node account
19:48:51:I1:Account websocket closed: UNACCEPTABLE msg=
19:48:51:I1:OUT3581:> GET https://api.foldingathome.org/machine/................. HTTP/1.1
19:48:52:I1:OUT3581:< HTTP/1.1 200 HTTP_OK
19:48:52:I1:OUT2:> GET wss://node1.foldingathome.org/ws/client HTTP/1.1
19:48:52:I1:OUT2:< HTTP/1.1 101 HTTP_SWITCHING_PROTOCOLS
19:48:52:I1:Logging into node account
19:48:52:I1:Account websocket closed: UNACCEPTABLE msg=
19:48:52:I1:OUT3582:> GET https://api.foldingathome.org/machine/................. HTTP/1.1
19:48:53:I1:OUT3582:< HTTP/1.1 200 HTTP_OK
19:48:53:I1:OUT2:> GET wss://node1.foldingathome.org/ws/client HTTP/1.1
19:48:53:I1:OUT2:< HTTP/1.1 101 HTTP_SWITCHING_PROTOCOLS
19:48:53:I1:Logging into node account
19:48:53:I1:Account websocket closed: UNACCEPTABLE msg=
19:48:53:I1:OUT3583:> GET https://api.foldingathome.org/machine/................. HTTP/1.1
19:48:54:I1:OUT3583:< HTTP/1.1 200 HTTP_OK
19:48:54:I1:OUT2:> GET wss://node1.foldingathome.org/ws/client HTTP/1.1
19:48:54:I1:OUT2:< HTTP/1.1 101 HTTP_SWITCHING_PROTOCOLS
Does this mean that it's not actually uploading my proofs of work?
The text was updated successfully, but these errors were encountered: