Docker support

[MiranoVerhoef]

Hey,

Would you be able to integrate this project to have docker support? Would be amazing to have!

[adn8naiagent]

Hey, thanks for the suggestion. Now fully deployable with Docker in the latest version. Hope you enjoy it

[andreuinyu]

Hi!
Terribly sorry to bother, I've given it a shot, and since I am already running a few services I tried changing the frontend exposed port on the docker-compose.yml to 6050 instead of 3000 (left side only). I also made this change in the FRONTEND_URL variable of backend.
I can see the password box at :6050, so that's working, however I had set no password (and have AUTH_ENABLE to false). I also get a "Could not connect to server" when I try to log in with any text in the password field.
If anyone can help explain, how did I mess it up? My guess is frontend and backend can no longer talk to each other? thanks!

ps: Have the kind devs considered to get the docker images of the releases pushed to a registrar? I think it would simplify deployment with docker compose so users just need a block of yaml, but I am not aware of the work involved in doing that.

[MiranoVerhoef]

Hi! Terribly sorry to bother, I've given it a shot, and since I am already running a few services I tried changing the frontend exposed port on the docker-compose.yml to 6050 instead of 3000 (left side only). I also made this change in the FRONTEND_URL variable of backend. I can see the password box at :6050, so that's working, however I had set no password (and have AUTH_ENABLE to false). I also get a "Could not connect to server" when I try to log in with any text in the password field. If anyone can help explain, how did I mess it up? My guess is frontend and backend can no longer talk to each other? thanks!

ps: Have the kind devs considered to get the docker images of the releases pushed to a registrar? I think it would simplify deployment with docker compose so users just need a block of yaml, but I am not aware of the work involved in doing that.

I agree, @adn8naiagent its quite easy to auto publish to GHRC.io so we have it published on a docker registrar

[adn8naiagent]

Hi! Terribly sorry to bother, I've given it a shot, and since I am already running a few services I tried changing the frontend exposed port on the docker-compose.yml to 6050 instead of 3000 (left side only). I also made this change in the FRONTEND_URL variable of backend. I can see the password box at :6050, so that's working, however I had set no password (and have AUTH_ENABLE to false). I also get a "Could not connect to server" when I try to log in with any text in the password field. If anyone can help explain, how did I mess it up? My guess is frontend and backend can no longer talk to each other? thanks!

ps: Have the kind devs considered to get the docker images of the releases pushed to a registrar? I think it would simplify deployment with docker compose so users just need a block of yaml, but I am not aware of the work involved in doing that.

Thanks for reporting this. It sounds like the frontend can't reach the backend. A couple of things to check:

• FRONTEND_URL on the backend is used for CORS, so it should match where you access the frontend (so
  http://localhost:6050 in your case).
• NEXT_PUBLIC_API_URL on the frontend tells the browser where the backend is. If you didn't change the backend port, this
  should stay as http://localhost:8000. This value is baked in at build time, so you'll need to rebuild with docker
  compose up --build after changing it.

I've also added clearer comments to the docker-compose.yml to make port customisation easier. Let me know if that helps.

[adn8naiagent]

Good suggestion on GHRC.io. I'm planning to add automatic Docker image publishing to GitHub Container Registry in the next release (1.2.0).

[svillar]

Hi! Terribly sorry to bother, I've given it a shot, and since I am already running a few services I tried changing the frontend exposed port on the docker-compose.yml to 6050 instead of 3000 (left side only). I also made this change in the FRONTEND_URL variable of backend. I can see the password box at :6050, so that's working, however I had set no password (and have AUTH_ENABLE to false). I also get a "Could not connect to server" when I try to log in with any text in the password field. If anyone can help explain, how did I mess it up? My guess is frontend and backend can no longer talk to each other? thanks!
ps: Have the kind devs considered to get the docker images of the releases pushed to a registrar? I think it would simplify deployment with docker compose so users just need a block of yaml, but I am not aware of the work involved in doing that.

Thanks for reporting this. It sounds like the frontend can't reach the backend. A couple of things to check:

• FRONTEND_URL on the backend is used for CORS, so it should match where you access the frontend (so
  http://localhost:6050 in your case).
• NEXT_PUBLIC_API_URL on the frontend tells the browser where the backend is. If you didn't change the backend port, this
  should stay as http://localhost:8000. This value is baked in at build time, so you'll need to rebuild with docker
  compose up --build after changing it.

I've also added clearer comments to the docker-compose.yml to make port customisation easier. Let me know if that helps.

The thing is that if using the docker compose file from docs (not the one from the sources) the backend port cannot be changed right? Because as you mentioned is baked at build time. Maybe some clarification to the docs is needed

[snipem]

Why is the frontend and backend split into two images? It would be easier to deploy if there was just one service.

[matze939939]

Changing the backend port and update NEXT_PUBLIC_API_URL: http://localhost:xxxx does not work. After redeploying the dockder stack the Request URL is still http://localhost:8000/api/auth/status. I also get a "Could not connect to server" when I try to log in.

[e1w00db1ue5]

I think I am having a similar issue, but I think I've complicated mine by trying to run it in UnRaid using the docker compse add-on.

This is my docker compose

services:
  backend:
    image: ghcr.io/adn8naiagent/f1replaytiming-backend:latest
    ports:
      - "8000:8000"
    environment:
      - FRONTEND_URL=http://localhost:3000
      - DATA_DIR=/data
    volumes:
      - /mnt/cache/appdata/f1replay/data:/data
      - /mnt/cache/appdata/f1replay/cache:/data/fastf1-cache

  frontend:
    image: ghcr.io/adn8naiagent/f1replaytiming-frontend:latest
    ports:
      - "3000:3000"
    depends_on:
      - backend
    environment:
      - NEXT_PUBLIC_API_URL=http://localhost:8000

I get asked for a password when I go to the frontend and then get the same message as @matze939939 "Cound not connect to server", I am asked for a password and trying to set the authentication enviromental variables doesn't change this behaviour.

It looks like it's working :)

backend-1  | /usr/local/lib/python3.11/site-packages/fastf1/api.py:32: UserWarning: `fastf1.api` will be considered private in future releases and potentially be removed or changed!
backend-1  |   warnings.warn("`fastf1.api` will be considered private in future releases and "
frontend-1  |    ▲ Next.js 15.5.12
frontend-1  |    - Local:        http://localhost:3000
backend-1   | INFO:     Started server process [9]
frontend-1  |    - Network:      http://0.0.0.0:3000
frontend-1  | 
frontend-1  |  ✓ Starting...
backend-1   | INFO:     Waiting for application startup.
backend-1   | INFO:main:Auto-precompute background task scheduled
backend-1   | INFO:auto_precompute:Auto-precompute background task started
backend-1   | INFO:     Application startup complete.
backend-1   | INFO:     Uvicorn running on http://0.0.0.0:8000 (Press CTRL+C to quit)
frontend-1  |  ✓ Ready in 331ms
backend-1   | INFO:auto_precompute:[auto] Checking for new session data...
backend-1   | INFO:services.f1_data:Fetching schedule for 2026 from FastF1...
backend-1   | INFO:services.f1_data:Schedule for 2026 cached (24 events).
backend-1   | INFO:auto_precompute:[auto] New session detected: 2026 R1 FP3, attempting precompute...
backend-1   | INFO:services.process:[2026 R1 FP3] Loading session data from F1 API...
backend-1   | INFO:services.f1_data:Loading session 2026/1/FP3 from FastF1...
backend-1   | core           INFO       Loading data for Australian Grand Prix - Practice 3 [v3.8.1]
backend-1   | INFO:fastf1.fastf1.core:Loading data for Australian Grand Prix - Practice 3 [v3.8.1]
backend-1   | req            INFO       No cached data found for session_info. Loading data...
backend-1   | INFO:fastf1.fastf1.req:No cached data found for session_info. Loading data...
backend-1   | _api           INFO       Fetching session info data...
backend-1   | INFO:fastf1.api:Fetching session info data...
backend-1   | req            INFO       Data has been written to cache!
backend-1   | INFO:fastf1.fastf1.req:Data has been written to cache!
backend-1   | req            INFO       No cached data found for driver_info. Loading data...
backend-1   | INFO:fastf1.fastf1.req:No cached data found for driver_info. Loading data...
backend-1   | _api           INFO       Fetching driver list...
backend-1   | INFO:fastf1.api:Fetching driver list...
backend-1   | req            INFO       Data has been written to cache!
backend-1   | INFO:fastf1.fastf1.req:Data has been written to cache!
backend-1   | req            INFO       No cached data found for session_status_data. Loading data...
backend-1   | INFO:fastf1.fastf1.req:No cached data found for session_status_data. Loading data...
backend-1   | _api           INFO       Fetching session status data...
backend-1   | INFO:fastf1.api:Fetching session status data...
backend-1   | req            INFO       Data has been written to cache!
backend-1   | INFO:fastf1.fastf1.req:Data has been written to cache!
backend-1   | req            INFO       No cached data found for track_status_data. Loading data...
backend-1   | INFO:fastf1.fastf1.req:No cached data found for track_status_data. Loading data...
backend-1   | _api           INFO       Fetching track status data...
backend-1   | INFO:fastf1.api:Fetching track status data...
backend-1   | req            INFO       Data has been written to cache!
backend-1   | INFO:fastf1.fastf1.req:Data has been written to cache!
backend-1   | req            INFO       No cached data found for _extended_timing_data. Loading data...
backend-1   | INFO:fastf1.fastf1.req:No cached data found for _extended_timing_data. Loading data...
backend-1   | _api           INFO       Fetching timing data...
backend-1   | INFO:fastf1.api:Fetching timing data...
backend-1   | _api           INFO       Parsing timing data...
backend-1   | INFO:fastf1.api:Parsing timing data...
backend-1   | req            INFO       Data has been written to cache!
backend-1   | INFO:fastf1.fastf1.req:Data has been written to cache!
backend-1   | req            INFO       No cached data found for timing_app_data. Loading data...
backend-1   | INFO:fastf1.fastf1.req:No cached data found for timing_app_data. Loading data...
backend-1   | _api           INFO       Fetching timing app data...
backend-1   | INFO:fastf1.api:Fetching timing app data...
backend-1   | req            INFO       Data has been written to cache!
backend-1   | INFO:fastf1.fastf1.req:Data has been written to cache!
backend-1   | core           INFO       Processing timing data...
backend-1   | INFO:fastf1.fastf1.core:Processing timing data...
backend-1   | core        WARNING       No lap data for driver 18
backend-1   | WARNING:fastf1.fastf1.core:No lap data for driver 18
backend-1   | core        WARNING       Failed to perform lap accuracy check - all laps marked as inaccurate (driver 18)
backend-1   | WARNING:fastf1.fastf1.core:Failed to perform lap accuracy check - all laps marked as inaccurate (driver 18)
backend-1   | req            INFO       No cached data found for car_data. Loading data...
backend-1   | INFO:fastf1.fastf1.req:No cached data found for car_data. Loading data...
backend-1   | _api           INFO       Fetching car data...
backend-1   | INFO:fastf1.api:Fetching car data...
backend-1   | _api           INFO       Parsing car data...
backend-1   | INFO:fastf1.api:Parsing car data...
backend-1   | req            INFO       Data has been written to cache!
backend-1   | INFO:fastf1.fastf1.req:Data has been written to cache!
backend-1   | req            INFO       No cached data found for position_data. Loading data...
backend-1   | INFO:fastf1.fastf1.req:No cached data found for position_data. Loading data...
backend-1   | _api           INFO       Fetching position data...
backend-1   | INFO:fastf1.api:Fetching position data...
backend-1   | _api           INFO       Parsing position data...
backend-1   | INFO:fastf1.api:Parsing position data...
backend-1   | req            INFO       Data has been written to cache!
backend-1   | INFO:fastf1.fastf1.req:Data has been written to cache!
backend-1   | req            INFO       No cached data found for weather_data. Loading data...
backend-1   | INFO:fastf1.fastf1.req:No cached data found for weather_data. Loading data...
backend-1   | _api           INFO       Fetching weather data...
backend-1   | INFO:fastf1.api:Fetching weather data...
backend-1   | req            INFO       Data has been written to cache!
backend-1   | INFO:fastf1.fastf1.req:Data has been written to cache!
backend-1   | req            INFO       No cached data found for race_control_messages. Loading data...
backend-1   | INFO:fastf1.fastf1.req:No cached data found for race_control_messages. Loading data...
backend-1   | _api           INFO       Fetching race control messages...
backend-1   | INFO:fastf1.api:Fetching race control messages...
backend-1   | req            INFO       Data has been written to cache!
backend-1   | INFO:fastf1.fastf1.req:Data has been written to cache!
backend-1   | core           INFO       Finished loading data for 22 drivers: ['1', '3', '5', '6', '10', '11', '12', '14', '16', '18', '23', '27', '30', '31', '41', '43', '44', '55', '63', '77', '81', '87']
backend-1   | INFO:fastf1.fastf1.core:Finished loading data for 22 drivers: ['1', '3', '5', '6', '10', '11', '12', '14', '16', '18', '23', '27', '30', '31', '41', '43', '44', '55', '63', '77', '81', '87']
backend-1   | INFO:services.f1_data:Session 2026/1/FP3 loaded.
backend-1   | INFO:services.storage:Saved sessions/2026/1/FP3/info.json (2772 bytes)
backend-1   | INFO:services.process:[2026 R1 FP3] Processing track data...
backend-1   | INFO:services.f1_data:Sector boundaries: S1 ends at point 204/588, S2 ends at 333/588
backend-1   | INFO:services.storage:Saved sessions/2026/1/FP3/track.json (28841 bytes)
backend-1   | INFO:services.process:[2026 R1 FP3] Processing lap data...
backend-1   | INFO:services.storage:Saved sessions/2026/1/FP3/laps.json (71001 bytes)
backend-1   | INFO:services.storage:Saved sessions/2026/1/FP3/results.json (4239 bytes)
backend-1   | INFO:services.process:[2026 R1 FP3] Building replay frames (this may take a minute)...
backend-1   | INFO:     100.116.133.84:56246 - "GET /api/auth/status HTTP/1.1" 200 OK
backend-1   | WARNING:  Invalid HTTP request received.
backend-1   | WARNING:  Invalid HTTP request received.
backend-1   | INFO:     100.116.133.84:56246 - "GET /api/auth/status HTTP/1.1" 200 OK
backend-1   | WARNING:  Invalid HTTP request received.
backend-1   | WARNING:  Invalid HTTP request received.
backend-1   | INFO:     100.116.133.84:56246 - "GET /api/ HTTP/1.1" 404 Not Found
backend-1   | WARNING:  Invalid HTTP request received.
backend-1   | WARNING:  Invalid HTTP request received.
backend-1   | INFO:services.f1_data:Race control messages: 60 entries
backend-1   | INFO:services.f1_data:RCM columns: ['Time', 'Category', 'Message', 'Status', 'Flag', 'Scope', 'Sector', 'RacingNumber', 'Lap']
backend-1   | INFO:services.f1_data:Parsed 0 flag events: []
backend-1   | INFO:services.f1_data:Loaded 15 track status entries
backend-1   | INFO:services.f1_data:Loaded 90 weather entries
backend-1   | INFO:services.f1_data:Pre-processed 21 drivers for frame generation, 7923 frames to build
backend-1   | req            INFO       Using cached data for _extended_timing_data
backend-1   | INFO:fastf1.fastf1.req:Using cached data for _extended_timing_data
backend-1   | INFO:services.f1_data:Loaded F1 timing data for 21 drivers (460 entries), intervals=yes
backend-1   | INFO:services.storage:Saved sessions/2026/1/FP3/replay.json (86308397 bytes)
backend-1   | INFO:services.process:[2026 R1 FP3] Uploaded 7923 replay frames
backend-1   | INFO:services.process:[2026 R1 FP3] Processing telemetry...
backend-1   | INFO:services.storage:Saved sessions/2026/1/FP3/telemetry/NOR.json (1083627 bytes)
backend-1   | INFO:services.storage:Saved sessions/2026/1/FP3/telemetry/VER.json (678855 bytes)
backend-1   | INFO:services.storage:Saved sessions/2026/1/FP3/telemetry/BOR.json (980447 bytes)
backend-1   | INFO:services.storage:Saved sessions/2026/1/FP3/telemetry/HAD.json (723571 bytes)
backend-1   | INFO:services.storage:Saved sessions/2026/1/FP3/telemetry/GAS.json (1254313 bytes)
backend-1   | INFO:services.storage:Saved sessions/2026/1/FP3/telemetry/PER.json (988157 bytes)
backend-1   | INFO:services.storage:Saved sessions/2026/1/FP3/telemetry/ANT.json (866859 bytes)
backend-1   | INFO:services.storage:Saved sessions/2026/1/FP3/telemetry/ALO.json (934898 bytes)
backend-1   | INFO:services.storage:Saved sessions/2026/1/FP3/telemetry/LEC.json (997619 bytes)
backend-1   | INFO:services.storage:Saved sessions/2026/1/FP3/telemetry/ALB.json (834136 bytes)
backend-1   | INFO:services.storage:Saved sessions/2026/1/FP3/telemetry/HUL.json (1073684 bytes)
backend-1   | INFO:services.storage:Saved sessions/2026/1/FP3/telemetry/LAW.json (661296 bytes)
backend-1   | INFO:services.storage:Saved sessions/2026/1/FP3/telemetry/OCO.json (950058 bytes)
backend-1   | INFO:services.storage:Saved sessions/2026/1/FP3/telemetry/LIN.json (774620 bytes)
backend-1   | INFO:services.storage:Saved sessions/2026/1/FP3/telemetry/COL.json (1094132 bytes)
backend-1   | INFO:services.storage:Saved sessions/2026/1/FP3/telemetry/HAM.json (1049870 bytes)
backend-1   | INFO:services.storage:Saved sessions/2026/1/FP3/telemetry/SAI.json (24760 bytes)
backend-1   | INFO:services.storage:Saved sessions/2026/1/FP3/telemetry/RUS.json (1113476 bytes)
backend-1   | INFO:services.storage:Saved sessions/2026/1/FP3/telemetry/BOT.json (619420 bytes)
backend-1   | INFO:services.storage:Saved sessions/2026/1/FP3/telemetry/PIA.json (842256 bytes)
backend-1   | INFO:services.storage:Saved sessions/2026/1/FP3/telemetry/BEA.json (871454 bytes)
backend-1   | INFO:services.process:[2026 R1 FP3] Uploaded telemetry for 22 drivers
backend-1   | INFO:services.process:[2026 R1 FP3] Done
backend-1   | INFO:services.process:[2026 R1 FP3] Done
backend-1   | INFO:auto_precompute:[auto] Successfully processed 2026 R1 FP3
backend-1   | INFO:services.storage:Saved seasons/2026/schedule.json (12414 bytes)
backend-1   | INFO:auto_precompute:[auto] New session detected: 2026 R1 Q, attempting precompute...
backend-1   | INFO:services.process:[2026 R1 Q] Loading session data from F1 API...
backend-1   | INFO:services.f1_data:Loading session 2026/1/Q from FastF1...
backend-1   | core           INFO       Loading data for Australian Grand Prix - Qualifying [v3.8.1]
backend-1   | INFO:fastf1.fastf1.core:Loading data for Australian Grand Prix - Qualifying [v3.8.1]
backend-1   | req            INFO       No cached data found for session_info. Loading data...
backend-1   | INFO:fastf1.fastf1.req:No cached data found for session_info. Loading data...
backend-1   | _api           INFO       Fetching session info data...
backend-1   | INFO:fastf1.api:Fetching session info data...
backend-1   | req            INFO       Data has been written to cache!
backend-1   | INFO:fastf1.fastf1.req:Data has been written to cache!
backend-1   | req            INFO       No cached data found for driver_info. Loading data...
backend-1   | INFO:fastf1.fastf1.req:No cached data found for driver_info. Loading data...
backend-1   | _api           INFO       Fetching driver list...
backend-1   | INFO:fastf1.api:Fetching driver list...
backend-1   | req            INFO       Data has been written to cache!
backend-1   | INFO:fastf1.fastf1.req:Data has been written to cache!
backend-1   | DEBUG:fastf1.ergast:Failed to parse timestamp '' in Ergastresponse.
backend-1   | req            INFO       No cached data found for session_status_data. Loading data...
backend-1   | INFO:fastf1.fastf1.req:No cached data found for session_status_data. Loading data...
backend-1   | _api           INFO       Fetching session status data...
backend-1   | INFO:fastf1.api:Fetching session status data...
backend-1   | req            INFO       Data has been written to cache!
backend-1   | INFO:fastf1.fastf1.req:Data has been written to cache!
backend-1   | req            INFO       No cached data found for track_status_data. Loading data...
backend-1   | INFO:fastf1.fastf1.req:No cached data found for track_status_data. Loading data...
backend-1   | _api           INFO       Fetching track status data...
backend-1   | INFO:fastf1.api:Fetching track status data...
backend-1   | req            INFO       Data has been written to cache!
backend-1   | INFO:fastf1.fastf1.req:Data has been written to cache!
backend-1   | req            INFO       No cached data found for _extended_timing_data. Loading data...
backend-1   | INFO:fastf1.fastf1.req:No cached data found for _extended_timing_data. Loading data...
backend-1   | _api           INFO       Fetching timing data...
backend-1   | INFO:fastf1.api:Fetching timing data...
backend-1   | _api           INFO       Parsing timing data...
backend-1   | INFO:fastf1.api:Parsing timing data...
backend-1   | req            INFO       Data has been written to cache!
backend-1   | INFO:fastf1.fastf1.req:Data has been written to cache!
backend-1   | req            INFO       No cached data found for timing_app_data. Loading data...
backend-1   | INFO:fastf1.fastf1.req:No cached data found for timing_app_data. Loading data...
backend-1   | _api           INFO       Fetching timing app data...
backend-1   | INFO:fastf1.api:Fetching timing app data...
backend-1   | req            INFO       Data has been written to cache!
backend-1   | INFO:fastf1.fastf1.req:Data has been written to cache!
backend-1   | core           INFO       Processing timing data...
backend-1   | INFO:fastf1.fastf1.core:Processing timing data...
backend-1   | core        WARNING       No lap data for driver 18
backend-1   | WARNING:fastf1.fastf1.core:No lap data for driver 18
backend-1   | core        WARNING       No lap data for driver 55
backend-1   | WARNING:fastf1.fastf1.core:No lap data for driver 55
backend-1   | core        WARNING       Failed to perform lap accuracy check - all laps marked as inaccurate (driver 18)
backend-1   | WARNING:fastf1.fastf1.core:Failed to perform lap accuracy check - all laps marked as inaccurate (driver 18)
backend-1   | core        WARNING       Failed to perform lap accuracy check - all laps marked as inaccurate (driver 55)
backend-1   | WARNING:fastf1.fastf1.core:Failed to perform lap accuracy check - all laps marked as inaccurate (driver 55)
backend-1   | req            INFO       No cached data found for car_data. Loading data...
backend-1   | INFO:fastf1.fastf1.req:No cached data found for car_data. Loading data...
backend-1   | _api           INFO       Fetching car data...
backend-1   | INFO:fastf1.api:Fetching car data...
backend-1   | _api           INFO       Parsing car data...
backend-1   | INFO:fastf1.api:Parsing car data...
backend-1   | req            INFO       Data has been written to cache!
backend-1   | INFO:fastf1.fastf1.req:Data has been written to cache!
backend-1   | req            INFO       No cached data found for position_data. Loading data...
backend-1   | INFO:fastf1.fastf1.req:No cached data found for position_data. Loading data...
backend-1   | _api           INFO       Fetching position data...
backend-1   | INFO:fastf1.api:Fetching position data...
backend-1   | _api           INFO       Parsing position data...
backend-1   | INFO:fastf1.api:Parsing position data...
backend-1   | req            INFO       Data has been written to cache!
backend-1   | INFO:fastf1.fastf1.req:Data has been written to cache!
backend-1   | req            INFO       No cached data found for weather_data. Loading data...
backend-1   | INFO:fastf1.fastf1.req:No cached data found for weather_data. Loading data...
backend-1   | _api           INFO       Fetching weather data...
backend-1   | INFO:fastf1.api:Fetching weather data...
backend-1   | req            INFO       Data has been written to cache!
backend-1   | INFO:fastf1.fastf1.req:Data has been written to cache!
backend-1   | req            INFO       No cached data found for race_control_messages. Loading data...
backend-1   | INFO:fastf1.fastf1.req:No cached data found for race_control_messages. Loading data...
backend-1   | _api           INFO       Fetching race control messages...
backend-1   | INFO:fastf1.api:Fetching race control messages...
backend-1   | req            INFO       Data has been written to cache!
backend-1   | INFO:fastf1.fastf1.req:Data has been written to cache!
backend-1   | core           INFO       Finished loading data for 22 drivers: ['63', '12', '6', '16', '81', '1', '44', '30', '41', '5', '27', '87', '31', '10', '23', '43', '14', '11', '77', '18', '3', '55']
backend-1   | INFO:fastf1.fastf1.core:Finished loading data for 22 drivers: ['63', '12', '6', '16', '81', '1', '44', '30', '41', '5', '27', '87', '31', '10', '23', '43', '14', '11', '77', '18', '3', '55']
backend-1   | INFO:services.f1_data:Session 2026/1/Q loaded.
backend-1   | INFO:services.storage:Saved sessions/2026/1/Q/info.json (2770 bytes)
backend-1   | INFO:services.process:[2026 R1 Q] Processing track data...
backend-1   | INFO:services.f1_data:Sector boundaries: S1 ends at point 200/567, S2 ends at 322/567
backend-1   | INFO:services.storage:Saved sessions/2026/1/Q/track.json (27798 bytes)
backend-1   | INFO:services.process:[2026 R1 Q] Processing lap data...
backend-1   | INFO:services.storage:Saved sessions/2026/1/Q/laps.json (66013 bytes)
backend-1   | INFO:services.storage:Saved sessions/2026/1/Q/results.json (4192 bytes)
backend-1   | INFO:services.process:[2026 R1 Q] Building replay frames (this may take a minute)...
backend-1   | INFO:services.f1_data:Race control messages: 99 entries
backend-1   | INFO:services.f1_data:RCM columns: ['Time', 'Category', 'Message', 'Status', 'Flag', 'Scope', 'Sector', 'RacingNumber', 'Lap']
backend-1   | INFO:services.f1_data:RCM flag: ANT | investigation | msg=INCIDENT INVOLVING CAR 12 (ANT) NOTED - PIT LANE INFRINGEMENT | t=1324s
backend-1   | INFO:services.f1_data:RCM flag: GAS | investigation | msg=INCIDENT INVOLVING CAR 10 (GAS) NOTED - UNSAFE CONDITION | t=3408s
backend-1   | INFO:services.f1_data:RCM flag: ANT | investigation | msg=INCIDENT INVOLVING CAR 12 (ANT) NOTED - UNSAFE CONDITION | t=3716s
backend-1   | INFO:services.f1_data:Parsed 3 flag events: [(1323.851, 'ANT', 'investigation'), (3407.851, 'GAS', 'investigation'), (3715.851, 'ANT', 'investigation')]
backend-1   | INFO:services.f1_data:Loaded 15 track status entries
backend-1   | INFO:services.f1_data:Qualifying phases: [('Q1', '761-1393'), ('Q1', '1901-2350'), ('Q2', '2802-3701'), ('Q3', '4301-4495'), ('Q3', '4962-5548')]
backend-1   | INFO:services.f1_data:Quali: set session_time_offset to Q1 green start (761.5s)
backend-1   | INFO:services.f1_data:Loaded 95 weather entries
backend-1   | INFO:services.f1_data:Pre-processed 20 drivers for frame generation, 9790 frames to build
backend-1   | req            INFO       Using cached data for _extended_timing_data
backend-1   | INFO:fastf1.fastf1.req:Using cached data for _extended_timing_data
backend-1   | INFO:services.f1_data:Loaded F1 timing data for 20 drivers (1090 entries), intervals=yes
backend-1   | INFO:services.storage:Saved sessions/2026/1/Q/replay.json (130321748 bytes)
backend-1   | INFO:services.process:[2026 R1 Q] Uploaded 9790 replay frames
backend-1   | INFO:services.process:[2026 R1 Q] Processing telemetry...
backend-1   | INFO:services.storage:Saved sessions/2026/1/Q/telemetry/RUS.json (1012822 bytes)
backend-1   | INFO:services.storage:Saved sessions/2026/1/Q/telemetry/ANT.json (842650 bytes)

Thanks for this great project :)

J

[adn8naiagent]

Hey everyone, thanks for all the reports here. These have been really helpful in identifying the issues and others have raised similar concerns.

2 main issues:

1. When the frontend couldn't connect to the backend, it was showing the passphrase screen instead of an actual
   error message. This made it look like an auth problem when it was a connection problem.
2. NEXT_PUBLIC_API_URL was hardcoded into the frontend JavaScript at build time. The pre-built Docker images had
   http://localhost:8000 baked in, so setting it as an environment variable in docker-compose had no effect. This is
   why it only worked when accessing via localhost on the same machine. Confusing and unhelpful

Have just released 1.2.1 to address both:

• The frontend now shows a "Cannot connect to backend" error screen with the URL it tried to reach, instead of the
  passphrase form
• NEXT_PUBLIC_API_URL is now a runtime environment variable. Set it on the frontend container in docker-compose
  and it works. No rebuilding required
• The README has been updated with configuration examples for LAN access and reverse proxy setups

For Docker deployments, all configuration goes in docker-compose.yml, not in .env files. The .env files are only for local development without Docker. There are two variables that need to match your setup:

• NEXT_PUBLIC_API_URL - set on the frontend service in docker-compose. The URL your browser uses to reach the
  backend.
• FRONTEND_URL - set on the backend service in docker-compose. The URL your browser uses to reach the frontend
  (needed for CORS).

@andreuinyu For your setup with port 6050:

backend:
environment:
- FRONTEND_URL=http://localhost:6050

frontend:
environment:
- NEXT_PUBLIC_API_URL=http://localhost:8000

@e1w00db1ue5 Your Unraid setup needs both URLs set to your Unraid server's IP if you're accessing from another machine:

backend:
environment:
- FRONTEND_URL=http://:3000

frontend:
environment:
- NEXT_PUBLIC_API_URL=http://:8000

@matze939939 Same fix. Set NEXT_PUBLIC_API_URL on the frontend service in docker-compose. With the new release it
works at runtime.

@svillar You were right that the port couldn't be changed with the pre-built images before. That's now fixed.

@snipem They're split because the frontend is a Next.js app and the backend is a Python/FastAPI server

Thanks again for chekcing out the project and your feedback. Let me know any other issues or suggestions and I'll look into them

[andreuinyu]

I am pleased to say that that fixed it for me boss, thanks a lot, can't wait to try it with today's sprint. BTW I got me an Openrouter API key, I tried passing it to the backend as an extra environment variable and I still can't see the "Sync" button, is it available in this docker deployment?

[adn8naiagent]

Great to hear! I'll be watching the sprint race and testing out the new live timing. It's unfortunate that driver track position isn't shared without F1 TV auth, but having the live leaderboard with more info is going to be great.

On the sync button, it only appears on race and sprint sessions. For practice and qualifying you'd just manually adjust the playback time until the session clock lines up with your broadcast. If you want to try out the sync function try on the Aus race.
The OpenRouter API key is only needed for the photo sync tab where you take a photo or upload a screenshot so it can extract the text from the image to pass to the app to compare against the data to line up timing. There's also a manual entry tab that works without any API key. You just enter the lap number and the top 3 gaps.

One thing I have noticed with the photo sync in 2026 is that they've dropped the hundredths and thousandths decimals from the timing tower the photo sync isn't as reliable to get to the exact moment. I'm going to have a look at how we might be able to work around this, but I think taking a photo with more drivers on the board means it will have more info to validate against.

[e1w00db1ue5]

@adn8naiagent this is now working for me, thank you.