-
Notifications
You must be signed in to change notification settings - Fork 23
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
[Bug] Handle certificate errors by moving to the next available provider #42
Comments
Errors occurred on a standard ubuntu installation as well as a standard raspbian installation (with OMV running alongside), and a SteamOS installation. Users should not have to deal with importing possibly-untrusted certs (if they even know how). I have not tested on Windows yet, but the same argument applies. There have also been times where domains change or certs simply needed to be renewed (gogo is the most recent [albeit currently-zombie] example). |
Will look at this next year. |
Though if you are willing to help will be happy to merge your pr's |
Sure, if I have time I can look for an actual and non-hacky solution, but I think we are all in the same boat due to the holidays. That being said, Happy holidays and new year! |
Hey, Though what would be an "actual and non-hacky solution" as mentioned by @serialjaywalker ? The naive solution suggested seems good to me? |
You are welcome to do so am personally taking a long break from fastanime it does everything i wanted it to do plus more and i think i deserve a break coding for 3mnths straight and writing 13k lines of code solo is no joke |
If a certificate is not accepted by the first chosen provider, the download will fail and failover goes to "completed".
The behaviour should be to retry with the next available provider until no providers are left, and then error out.
When doing a naive solution
I am able to download again (showing both naive and original).
The text was updated successfully, but these errors were encountered: