Replies: 2 comments
-
Out of 212 challenges resolved since April 6th, I have a response rate of less than 10 seconds for 44% of them. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Unless the host device is underpowered (e.g. a cheap Pi/SBC), or resources are being limited to the container, see #1036. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Good evening, I'm using Flaresolverr on my dedicated server exclusively for the YGGTorrent tracker.
I believe I've checked all my configurations, but I'm still unable to achieve stability. Flaresolverr solves the challenge each time, but in times that are really too long.
Jackett therefore regularly errors out for this tracker because the response time exceeds 100 seconds.
""An error occurred while testing this indexer
Exception (yggtorrent): A task was canceled.: The request was canceled due to the configured HttpClient.Timeout of 100 seconds elapsing.""
I've extracted data from my logs to share the server's performance with you. You'll notice that the average response time is 136 seconds, and there are few instances where I'm below 100. Can you please help me? I'm at a loss for what to do."
Data since 6 april 2024
100 seconde deadling in green
Average in yellow
Beta Was this translation helpful? Give feedback.
All reactions