View Single Post
Old 06-13-2024, 02:15 PM   #9680
JimmXinu
Plugin Developer
JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.
 
JimmXinu's Avatar
 
Posts: 7,043
Karma: 4604637
Join Date: Dec 2011
Location: Midwest USA
Device: Kobo Clara Colour running KOReader
Quote:
Originally Posted by MorbPtact View Post
Apparently this is windows 10, my bad
Here's the log without adding use_ssl_unverified_context:
Even with use_ssl_unverified_context you are apparently not getting a valid story page. FFF is failing to find the story title.

I checked and royalroad's SSL cert comes back valid for me. Considering you are getting reports of an invalid self-signed cert first, it looks like you may have a network proxy or even a man-in-the-middle malware situation.

We've seen SSL with FFF fail before with intrusive network proxy servers. Some people have had better success using a VPN.

You might try using FFF's Proxy Feature or Browser Cache Feature. However, I don't recall ever trying them with royalroad.

FYI, wrapping logs with [code] tags helps readability. And long logs with [spoiler] for people on mobile.
JimmXinu is online now   Reply With Quote