Skip to content

[Bug]: Timed out waiting for backend readiness at http://127.0.0.1:3773. #1998

Description

@mbruhler

Before submitting

  • I searched existing issues and did not find a duplicate.
  • I included enough detail to reproduce or investigate the problem.

Area

apps/web

Steps to reproduce

When starting freshly downloaded t3code I get:

Stage: bootstrap
Timed out waiting for backend readiness at http://127.0.0.1:3773.
Error: Timed out waiting for backend readiness at http://127.0.0.1:3773.
at waitForHttpReady (/Applications/T3 Code (Alpha).app/Contents/Resources/app.asar/apps/desktop/dist-electron/main.js:3703:37)
at process.processTicksAndRejections (node:internal/process/task_queues:103:5)
at async waitForBackendHttpReady (/Applications/T3 Code (Alpha).app/Contents/Resources/app.asar/apps/desktop/dist-electron/main.js:4228:3)
at async bootstrap (/Applications/T3 Code (Alpha).app/Contents/Resources/app.asar/apps/desktop/dist-electron/main.js:5272:2)

Expected behavior

No error, app starts normally

Actual behavior

There is above bug

Impact

Blocks work completely

Version or commit

No response

Environment

macOS Tahoe 26.3.1 (25D2128)

Logs or stack traces

Mentioned above

Screenshots, recordings, or supporting files

image.png

Workaround

No available, app is unusable

Activity

  1. added
    bugSomething is broken or behaving incorrectly.
    needs-triageIssue needs maintainer review and initial categorization.
    on Apr 13, 2026
  2. MuhammedAlkhudiry commented on Apr 14, 2026

    @MuhammedAlkhudiry

    same after upgrading from 15 to 17, clicked restart to upgrade:

    Image
  3. RenatoPorfirio commented on Apr 14, 2026

    @RenatoPorfirio

    Same issue here. Windows 11 Pro (V. 25H2)

  4. GuuhBoss commented on Apr 14, 2026

    @GuuhBoss

    Same, after updating from 16 to 17, with ubuntu 24.04, T3-Code-0.0.17-x86_64.AppImage

  5. adammansfield commented on Apr 14, 2026

    @adammansfield
    Contributor

    This seems to be duplicate of #1916.

    #1979 is a merged PR, which should fix this issue in the next release.

  6. cinderblock commented on Apr 15, 2026

    @cinderblock

    Simple fix for this before the release: instead of clicking "ok", wait until the backend starts. (Check at http://localhost:3773)
    Once started, start a second instance of t3 code. Once the second instance's UI loads, click "ok" in the first instance. Second instance disconnects from backend and then ~10 seconds later connects to the restarted backend and you're off to the races.

  7. juliusmarminge commented on Apr 17, 2026

    @juliusmarminge
    Member

    should be fixed in 0.0.20

  8. nbyula-engineering commented on Apr 22, 2026

    @nbyula-engineering

    Still the same issue in 0.0.20

    [22/04 12:19:35] ➜ ./T3-Code-0.0.20-x86_64.AppImage 
    [desktop-updater] Using update channel 'latest' (allowPrerelease=false, allowDowngrade=false).
    MESA-INTEL: warning: Performance support disabled, consider sysctl dev.i915.perf_stream_paranoid=0
    
    [258852:0422/121944.090693:ERROR:dbus/object_proxy.cc:573] Failed to call method: org.freedesktop.systemd1.Manager.StartTransientUnit: object_path= /org/freedesktop/systemd1: org.freedesktop.systemd1.UnitExists: Unit app-org.chromium.Chromium-258852.scope already exists.
    [259573:0422/121944.165718:ERROR:media/gpu/vaapi/vaapi_wrapper.cc:1649] Installed VAAPI version is too old. min supported version: 1.17 installed version: 1.7
    [desktop] backend exited unexpectedly (code=1 signal=null); restarting in 500ms
    [desktop] backend readiness check timed out during packaged bootstrap Error: backend exited before logging readiness (code=1 signal=null)
        at ChildProcess.<anonymous> (/tmp/.mount_T3-CodpmBrgm/resources/app.asar/apps/desktop/dist-electron/main.js:5350:43)
        at ChildProcess.emit (node:events:508:28)
        at ChildProcess._handle.onexit (node:internal/child_process:294:12)
    [desktop] backend exited unexpectedly (code=1 signal=null); restarting in 500ms
    [desktop] backend readiness check timed out during packaged bootstrap Error: backend exited before logging readiness (code=1 signal=null)
        at ChildProcess.<anonymous> (/tmp/.mount_T3-CodpmBrgm/resources/app.asar/apps/desktop/dist-electron/main.js:5350:43)
        at ChildProcess.emit (node:events:508:28)
        at ChildProcess._handle.onexit (node:internal/child_process:294:12)
    [desktop] backend exited unexpectedly (code=1 signal=null); restarting in 500ms
    [desktop] backend readiness check timed out during packaged bootstrap Error: backend exited before logging readiness (code=1 signal=null)
        at ChildProcess.<anonymous> (/tmp/.mount_T3-CodpmBrgm/resources/app.asar/apps/desktop/dist-electron/main.js:5350:43)
        at ChildProcess.emit (node:events:508:28)
        at ChildProcess._handle.onexit (node:internal/child_process:294:12)
    [desktop-updater] Checking for updates (startup)...
    Checking for update
    [desktop-updater] Looking for updates...
    (node:258852) [DEP0169] DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for `url.parse()` vulnerabilities.
    (Use `t3code --trace-deprecation ...` to show where the warning was created)
    [desktop] backend exited unexpectedly (code=1 signal=null); restarting in 500ms
    [desktop] backend readiness check timed out during packaged bootstrap Error: backend exited before logging readiness (code=1 signal=null)
        at ChildProcess.<anonymous> (/tmp/.mount_T3-CodpmBrgm/resources/app.asar/apps/desktop/dist-electron/main.js:5350:43)
        at ChildProcess.emit (node:events:508:28)
        at ChildProcess._handle.onexit (node:internal/child_process:294:12)
    Update for version 0.0.20 is not available (latest version: 0.0.20, downgrade is disallowed).
    [desktop-updater] No updates available.
    [desktop] backend exited unexpectedly (code=1 signal=null); restarting in 500ms
    [desktop] backend readiness check timed out during packaged bootstrap Error: backend exited before logging readiness (code=1 signal=null)
        at ChildProcess.<anonymous> (/tmp/.mount_T3-CodpmBrgm/resources/app.asar/apps/desktop/dist-electron/main.js:5350:43)
        at ChildProcess.emit (node:events:508:28)
        at ChildProcess._handle.onexit (node:internal/child_process:294:12)
    [desktop] backend exited unexpectedly (code=1 signal=null); restarting in 500ms
    [desktop] backend readiness check timed out during packaged bootstrap Error: backend exited before logging readiness (code=1 signal=null)
        at ChildProcess.<anonymous> (/tmp/.mount_T3-CodpmBrgm/resources/app.asar/apps/desktop/dist-electron/main.js:5350:43)
        at ChildProcess.emit (node:events:508:28)
        at ChildProcess._handle.onexit (node:internal/child_process:294:12)
    ...
    
    [22/04 12:20:26] ➜  uname -a
    Linux nbyula 5.15.0-139-generic #149~20.04.1-Ubuntu SMP Wed Apr 16 08:29:56 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
    
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething is broken or behaving incorrectly.needs-triageIssue needs maintainer review and initial categorization.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions