[GUI Plugin] FanFicFare

[ownedbycats]

Id think some sort of browser fingerprinting. The other FFDL uses a built-in browser and doesn't run into same issues as FFF on Cloudflare'd sites.

[bpothier]

Looks like maybe SOL made a change to login page/URL? (redirects under WLPC, but it has for a while so maybe something else login page/URL/Cookie/CF related?).

Looks to break FFF with a 404 not found error when going from story URL to "login.wlpc.com/?r=xxxx........xxxxxxxxx" and then failing.

Was able to continue by (eventually) installing/running/enabling the nsapa proxy (github.com/JimmXinu/FanFicFare/wiki/ProxyFeatures) and logging in to the web browser it opens, then running FFF request again.

[JimmXinu]

I'm not seeing any issues with SOL downloading. Anyone else seeing this?

[bpothier]

Ok, then likely a Cloudflare issue/"feature". tried 1 story today and it worked fine without any FFF proxy setting... It actually worked for 90% of the list I put in yesterday, only 1 failed then repeated failing with any story after that.. SOL is new to the CF multiverse, so so user re-training might be needed to properly set expectations.. (but also good to know 1 temp workaround functions...for now...)

[MrKonan]

Originally Posted by JimmXinu

I'm not seeing any issues with SOL downloading. Anyone else seeing this?

Pretty strange error.. I've updated a few stories/different authors. Ran in to the 503 error, skipped to a different story update and went back to the 503 error title.. it worked afterwards

here's the quick log..

Status: Error

Title: A Captain Decision

Author: Pars001

Comment: HTTP Error in FFF '503 Server Error: Service Unavailable for url: sol/sol-secure/login.php'(503)

URL: sol/s/30263/a-captain-decision

Thanks

[julo]

Originally Posted by MrKonan

Comment: HTTP Error in FFF '503 Server Error: Service Unavailable for url: sol/sol-secure/login.php'(503)

I believe I saw the same thing today. In my case I think I had 2 requests open (not two files in one request). On redoing I got it fine.

[julo]

Say I list 5 files in FFF to download and after a while get "FFF found 3 good and 2 bad updates". So I click on Proceed, get my 3 good books but which books failed?
Can there be an option, another button say "Write fails to log", where failed downloads with appropriate information get written to a file so can be tried again? Maybe even make that the default for fails and write it right to Calibre?

[ownedbycats]

Originally Posted by julo

Say I list 5 files in FFF to download and after a while get "FFF found 3 good and 2 bad updates". So I click on Proceed, get my 3 good books but which books failed?

[Elaine T]

Originally Posted by julo

Say I list 5 files in FFF to download and after a while get "FFF found 3 good and 2 bad updates". So I click on Proceed, get my 3 good books but which books failed?
Can there be an option, another button say "Write fails to log", where failed downloads with appropriate information get written to a file so can be tried again? Maybe even make that the default for fails and write it right to Calibre?

Don't you get a choice to view log? I just had a similar failure (except they all failed) and chose view log, then copy to clipboard, and pasted it all into a document. The log shows the URLs and which of them failed. I'll be extremely glad when Ao3 stops having these problems. Has anyone seen any updates from them about it? Their tumblr hasn't had anything - if they're using the other social media they have listed I can't see it, as I don't have accounts on any of them.

[julo]

Originally Posted by ownedbycats

Attachment 215079

I have that checked but what does it give me?
However I had not checked the "Mark..." check box. Is that what was missing

[julo]

Originally Posted by Elaine T

Don't you get a choice to view log?

Yes I do get the log but more often than not I click on "Proceed" and then realize I shouldn't have done so but that is too late. Why not add it to FFF, it probably happens often enough and not to me alone?

[ownedbycats]

Originally Posted by julo

I have that checked but what does it give me?

You can view marked books, and the labels on pins identify failed.

[JimmXinu]

Originally Posted by julo

Say I list 5 files in FFF to download and after a while get "FFF found 3 good and 2 bad updates". So I click on Proceed, get my 3 good books but which books failed?
Can there be an option, another button say "Write fails to log", where failed downloads with appropriate information get written to a file so can be tried again? Maybe even make that the default for fails and write it right to Calibre?

Click View Log in the Proceed dialog before clicking 'Yes' to update library.

Or, open the Jobs list by clicking where it says 'Jobs' in the lower right corner, then double click on the last 'Download X Fanfiction Books' job to see the full log. At the bottom, it will tell you what failed and the log will tell you why.

As pointed out, there's also options to 'mark' both successful and failed books--which admittedly doesn't help with new downloads.

[applegaa]

Originally Posted by julo

Say I list 5 files in FFF to download and after a while get "FFF found 3 good and 2 bad updates". So I click on Proceed, get my 3 good books but which books failed?
Can there be an option, another button say "Write fails to log", where failed downloads with appropriate information get written to a file so can be tried again? Maybe even make that the default for fails and write it right to Calibre?

You can create a custom column for those errors if you want to retain them.

On the "Custom Columns" tab, there is a section at the bottom labeled "Special column:" and you want to create a column and add it to "Update/Overwrite Error Column:". I don't check the "Save All Errors" box, so I only see error messages if the last run failed. Granted, stories with no updates are listed as bad but have no error message, so you will only see them if you use the "View Log" button others have mentioned.

I wish that it had Good/Bad/No instead of just Good/Bad, but the current system works.

- Andrew

[julo]

Originally Posted by JimmXinu

Click View Log in the Proceed dialog before clicking 'Yes' to update library.

I have to admit I usually click on the "Proceed" button as soon as the little window pops up. I guess I have to change my ways. But I still think it would be a good option??