Repository navigation
[Bug]: Can't install anymore in devcontainer in docker, Error HTTP 504 #32897
Description
Before submitting
- I searched existing issues and did not find a duplicate.
- I included enough detail to reproduce or investigate the problem.
Area
apps/server
Steps to reproduce
Install the App using the following commands (try 2 of them);
vp ➜ ~ (main) $ t3 up --lan --yes
t3: GET https://github.com/pingdotgg/t3code/releases/download/v0.1.7/SHA256SUMS returned HTTP 504
vp ➜ ~ (main) $ curl -fsSL https://t3.codes/install.sh | sh
██████████ ████████
███ ▄██▀ T3 Code
███ ████▄ CLI installer
███ ▄ ███
███ ███████▀
Finding your release...GET https://github.com/pingdotgg/t3code/releases/latest returned HTTP 504Not sure if it's related but I am using tailscale inside the container but no change with tailscale disconnected.
It was working fine yesterday and I had to rebuild the container. It's seems like I got blacklisted by GitHub but not sure why.
I checked the rate_limit on the api and got ;
{"resources":{"code_search":{"limit":60,"remaining":59,"reset":1794133532,"used":1},"core":{"limit":60,"remaining":59,"reset":1794133532,"used":1},"graphql":{"limit":0,"remaining":0,"reset":1794134307,"used":0},"integration_manifest":{"limit":5000,"remaining":5000,"reset":1794134307,"used":0},"search":{"limit":10,"remaining":10,"reset":1794130767,"used":0}},"rate":{"limit":60,"remaining":59,"reset":1794133532,"used":1}}Copilot was not able to help me on that, I run out of idea too
Expected behavior
T3 code should be able to install
Actual behavior
T3 code did not install
Impact
Blocks work completely
Version or commit
0.1.7
Environment
Docker image based on ghcr.io/voidzero-dev/vite-plus
Logs or stack traces
See Steps to reproduce sectionScreenshots, recordings, or supporting files
No response
Workaround
None
Activity
LuisUrrutia commentedon Nov 8, 2026
not a blacklist, github's web release path was failing from more than one network at the same time. from a mac in Spain, 2026-11-08 08:48 to ~10:58 UTC:
/releases/download/...,/releases/latest,/releasesandreleases.atomanswered HTTP 504 in ~35 ms for every repo i tried (t3code, cli/cli, oven-sh/bun, microsoft/vscode, neovim/neovim), withx-github-request-idandx-github-edge-region: switzerlandnorthheaders, no redirect, HAProxy "504 Gateway Time-out" body. it was intermittent: a few requests went through after ~11 s, and at 10:58 UTC downloads work again whilecli/cli/releases/latestandreleases.atomstill 504. the desktop nightly updater (electron-updater, same path) failed the same way here, trace:Cannot download "<url>", status 504two things t3 could do about it:
install.shfetch()and the npm launcherget()do one request and fail on anything but 2xx/404 (scripts/install.sh:62-69, scripts/npm-launcher/t3.mjs:23-31). a retry with backoff on 5xx would have survived most of this windowapi.github.com/repos/pingdotgg/t3code/releases/latestreturned 200 andreleases/assets/<id>withAccept: application/octet-streamredirected to release-assets.githubusercontent.com and served, both unauthenticated. cliRelease.ts already uses that api for track resolution, so a 5xx fallback to it (60 req/h anonymous) is reachable.gh release downloaduses it and worked the whole timeif you still see it,
curl -sI https://github.com/pingdotgg/t3code/releases/latest | grep -i x-github-edge-regionwould tell whether it's regionalZehir commentedon Nov 8, 2026
Yes I think you right, I have the same issue when trying to download from other repos too. But for some reasons it's working on my computer but not in the raspberry pi (they are in the same local network).
Tried again and same result; I am in the French region;
x-github-edge-region: fratest(scripts): reproduce #32897, installers give up on one HTTP 504
Zehir commentedon Nov 8, 2026
Github region seems to be fixed no it's working fine. Maybe we can close this issue or maybe the linked PR is worth to do anyways