Search found 3 matches
- May 4th, 2024, 3:20 am
- Forum: Bug Reports
- Topic: "Fatal error" requiring restart on ver 4.2.3
- Replies: 4
- Views: 885
Re: "Fatal error" requiring restart on ver 4.2.3
Update on this issue: Finally upgraded to 4.3 and the problem changed to the 221 status code error. There's a github issue (#2822: fatal error in downloader with giganews ) that reflects exactly the issue I had (Soz, can't post links yet). The proposed solution of turning off pre-check seems to have...
- April 1st, 2024, 11:28 am
- Forum: Bug Reports
- Topic: "Fatal error" requiring restart on ver 4.2.3
- Replies: 4
- Views: 885
Re: "Fatal error" requiring restart on ver 4.2.3
Issue replicated on both giganews and highwinds backbones (on exact same nzbs). Will try and test 4.3b when I can and get back to report. To clarify: reported this issue as FYI because I'm sure it's/will be wide-spread. Not because I require support. I'm good with 4.2.2 for the moment. I probably sh...
- April 1st, 2024, 9:54 am
- Forum: Bug Reports
- Topic: "Fatal error" requiring restart on ver 4.2.3
- Replies: 4
- Views: 885
"Fatal error" requiring restart on ver 4.2.3
Running 64bit version 4.2.3 on Windows 10 pro. Getting an following unrecoverable error on MOST downloads mandating a full application kill and restart . Log entry: ::INFO::[notifier:142] Sending notification: Error - Fatal error in Downloader (type=error, job_cat=None) ::ERROR::[downloader:697] Fat...