-
-
Notifications
You must be signed in to change notification settings - Fork 281
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] Unable to Fetch Pre-Season Testing Data (403 & 404 Errors) #688
Comments
There is no replay available at the F1 Oficial App. Has it any relation to the problem? |
I ran into the same issue while trying to fetch the testing data. |
Facing the same issue. If you get a fix please do help. |
Thanks for the report. At this stage I cannot tell what is going on. Though, I have to say that there hasn't always been replay data available in recent years. Therefore, the data might simply be missing. |
@theOehrly I think they just changed the URL a bit:
But from Specifically, it's "Day_1" instead of the expected "Practice_1" |
@pesaventofilippo i've got a few minutes right now... hacky fix incoming |
Yes @pesaventofilippo you are correct |
Should be working now. Please upgrade to v3.4.5. I hope it keeps working for the next two days as well, and that I didn't mess anything up. |
I upgraded the FastF1 library to version 3.4.5, but I’m still getting the same error. I’ve tried using "Pre-Season Testing" and "FP1" as inputs, as well as "Day_1" and "Practice_1," but the error keeps appearing. Any ideas on what might be causing this? |
@patadeganzo Are you using |
It ran smoothly without any issues. It’s not the prettiest solution, but it gets the job done. Appreciate it, mate! |
@theOehrly thanks for the fix. It works now! |
Describe the issue:
I'm trying to fetch Pre-Season Testing data for 2025 using fastf1.get_testing_session(), but the request fails due to 403 Forbidden and 404 Not Found errors when attempting to retrieve session data from livetiming.formula1.com and the FastF1 mirror.
Reproduce the code example:
Error message:
The text was updated successfully, but these errors were encountered: