the latest version of lufah added a history command : https://github.com/kbernhagen/lufah
maybe that will meet your needs ?
Search found 25 matches
- Sun Oct 12, 2025 7:14 pm
- Forum: New Donors start here
- Topic: Logging of WUs / statistics
- Replies: 5
- Views: 2288
- Wed Aug 27, 2025 2:52 pm
- Forum: v8.4.9 Public Release for Windows / Linux / macOS
- Topic: "DB:1040: Too many connections"
- Replies: 7
- Views: 2286
Re: "DB:1040: Too many connections"
Yes same error here
Cannot login to web client
Stats are down
"Recent CPU" page gives the same error
(as expected with this error...)
Cannot login to web client
Stats are down
"Recent CPU" page gives the same error
(as expected with this error...)
- Mon Aug 25, 2025 10:34 am
- Forum: v8.4.9 Public Release for Windows / Linux / macOS
- Topic: 500 (HTTP_INTERNAL_SERVER_ERROR)
- Replies: 56
- Views: 13577
Re: 500 (HTTP_INTERNAL_SERVER_ERROR)
It works, thanks 

- Mon Aug 25, 2025 7:58 am
- Forum: v8.4.9 Public Release for Windows / Linux / macOS
- Topic: 500 (HTTP_INTERNAL_SERVER_ERROR)
- Replies: 56
- Views: 13577
Re: 500 (HTTP_INTERNAL_SERVER_ERROR)
F@h V7 will work, since it's not using API and the /machine endpoint F@h V8 works also, but , for new installation, you won't be able to monitor it with the F@h V8 web client and : - if you're using a token to auto-configure it, it won't use it and you will fold as Anonymous - if you're configuring ...
- Sat Aug 23, 2025 12:26 pm
- Forum: v8.4.9 Public Release for Windows / Linux / macOS
- Topic: 500 (HTTP_INTERNAL_SERVER_ERROR)
- Replies: 56
- Views: 13577
Re: 500 (HTTP_INTERNAL_SERVER_ERROR)
Still KO


- Sat Aug 23, 2025 11:17 am
- Forum: v8.4.9 Public Release for Windows / Linux / macOS
- Topic: 500 (HTTP_INTERNAL_SERVER_ERROR)
- Replies: 56
- Views: 13577
Re: 500 (HTTP_INTERNAL_SERVER_ERROR)
APIs are back but the /machine endpoint is still giving HTTP500 error for new installation (this issue happened before the SSL certificates expired) GETting the /gpus works fine, but PUTing the new /machine gives an HTTP500 error. https://i.ibb.co/ds3gtjBQ/HTTP500.png Can someone look into this too ...
- Sat Aug 23, 2025 10:56 am
- Forum: Issues with a specific server
- Topic: api.foldingathome.org certificate expired Sat, 23 Aug 2025 02:33:48 GMT
- Replies: 2
- Views: 2526
Re: api.foldingathome.org certificate expired Sat, 23 Aug 2025 02:33:48 GMT
Certificate has been renewed a few moments ago.
Certificate for api2.foldingathome.org is still expired, though...
edit: api2 has been renewed too, so stats are back.
Certificate for api2.foldingathome.org is still expired, though...
edit: api2 has been renewed too, so stats are back.
- Sat Aug 23, 2025 5:21 am
- Forum: v8.4.9 Public Release for Windows / Linux / macOS
- Topic: 500 (HTTP_INTERNAL_SERVER_ERROR)
- Replies: 56
- Views: 13577
Re: 500 (HTTP_INTERNAL_SERVER_ERROR)
It's a different issue, I think.
Yesterday, api.foldingathome.org was working fine (no expired certificate) when we had these HTTP500 errors.
Of course now, everything is borked with this expired certificate
Yesterday, api.foldingathome.org was working fine (no expired certificate) when we had these HTTP500 errors.
Of course now, everything is borked with this expired certificate

- Fri Aug 22, 2025 8:09 pm
- Forum: Discussions of General-FAH topics
- Topic: [Bonus] Account not found
- Replies: 35
- Views: 19958
Re: [Bonus] Account not found
It looks ok on https://apps.foldingathome.org/cpu
with your account : [AF>Libristes]Maeda
with your account : [AF>Libristes]Maeda
- Fri Aug 22, 2025 7:55 pm
- Forum: v8.4.9 Public Release for Windows / Linux / macOS
- Topic: 500 (HTTP_INTERNAL_SERVER_ERROR)
- Replies: 56
- Views: 13577
Re: 500 (HTTP_INTERNAL_SERVER_ERROR)
Same error here, I posted about it on the Discord server.
Fresh ubuntu install , with a brand new f@h V8 installation (same result with official .deb or tar.bz2)
Behaviour also confirmed by one of our team member who did the same thing (new installation of f@h client from official site)
Fresh ubuntu install , with a brand new f@h V8 installation (same result with official .deb or tar.bz2)
Behaviour also confirmed by one of our team member who did the same thing (new installation of f@h client from official site)
- Thu Aug 21, 2025 5:30 pm
- Forum: Discussions of General-FAH topics
- Topic: Detailed individual donor stats?
- Replies: 4
- Views: 2627
Re: Detailed individual donor stats?
Hello, If you only want your own stats, maybe go the API way : https://api2.foldingathome.org/user/JWhy and https://api2.foldingathome.org/cpus?query=JWhy ? I think Jason is using the huge file with all (?) users available in https://foldingathome.org/statistics/ (item menu "Donor list (txt)&qu...
- Fri Jul 25, 2025 8:07 am
- Forum: v8.4.9 Public Release for Windows / Linux / macOS
- Topic: EOC Stats
- Replies: 5
- Views: 6259
Re: EOC Stats
Hi all, I just sent this to Jason : Hello Jason, Just saw your message on F@h Stats :( I wanted to let you know that your website is one of the ones I visit every day, several times a day! It is an integral, indispensable, and virtually unmatched part of the Folding@home experience. Would it be poss...
- Fri Apr 09, 2021 1:01 pm
- Forum: Issues with a specific server
- Topic: (Solved) Timestamp and update times
- Replies: 9
- Views: 12752
Re: (Solved) Timestamp and update times
Thanks Joe_H , and sorry for posting in this thread (maybe it can be split ?)
- Thu Apr 08, 2021 8:18 am
- Forum: Issues with a specific server
- Topic: (Solved) Timestamp and update times
- Replies: 9
- Views: 12752
Re: (Solved) Timestamp and update times
Hi, There seem to be problems, still, with the "Last Returned" / "PRCG" information in the CPU page. (it seems related to this issue, that's why I'm posting here and not in a new topic.) https://apps.foldingathome.org/cpu?q=JWhy shows that my FAHClients returned WU today ("L...
- Mon May 11, 2020 7:22 am
- Forum: 3rd party contributed software
- Topic: HFM.NET - Monitoring Application for Folding@Home v7
- Replies: 770
- Views: 1224682
Re: HFM.NET - Monitoring Application for Folding@Home v7
Thank you , Harlam :) Since I cannot do much on my side, I googled a bit and found this issue in the Newtonsoft.Json GitHub : https://github.com/JamesNK/Newtonsoft.Json/issues/980 (you have probably already found it) There might be a workaround to handle these characters, even though it would be bet...