17 days ago
No code changes. On redeploys, I get the same GPG error below. Is it related to the outage?
npm ci
781ms
install apt packages: ca-certificates git unzip zip
674ms
Get:1 http://deb.debian.org/debian bookworm InRelease [151 kB]
Get:2 http://deb.debian.org/debian bookworm-updates InRelease [55.4 kB]
Get:3 http://deb.debian.org/debian-security bookworm-security InRelease [48.0 kB]
Err:1 http://deb.debian.org/debian bookworm InRelease
At least one invalid signature was encountered.
Err:2 http://deb.debian.org/debian bookworm-updates InRelease
At least one invalid signature was encountered.
Err:3 http://deb.debian.org/debian-security bookworm-security InRelease
At least one invalid signature was encountered.
Reading package lists...
W: GPG error: http://deb.debian.org/debian bookworm InRelease: At least one invalid signature was encountered.
E: The repository 'http://deb.debian.org/debian bookworm InRelease' is not signed.
W: GPG error: http://deb.debian.org/debian bookworm-updates InRelease: At least one invalid signature was encountered.
E: The repository 'http://deb.debian.org/debian bookworm-updates InRelease' is not signed.
W: GPG error: http://deb.debian.org/debian-security bookworm-security InRelease: At least one invalid signature was encountered.
E: The repository 'http://deb.debian.org/debian-security bookworm-security InRelease' is not signed.
Service ID: 89902744-174b-401e-b6ad-f48e255089a3
Failed deployments: 55780f33, ed2379dc, 53d7971c (May 20, 2026)
Last successful build: May 18, 2026 (same base image, same Railpack version 0.23.0, same resolved packages)
Recent changes: Only PHP controller/job refactoring and React component updates—nothing build-related
Is it related to the build cache, or due to outage?
3 Replies
17 days ago
This is caused by a stale build cache where the cached apt package indexes have outdated GPG signatures. Set the environment variable NO_CACHE=1 on the service, trigger a new deploy, and once it succeeds you can remove NO_CACHE=1 to re-enable caching. See Build Configuration for details.
Status changed to Awaiting User Response Railway • 17 days ago
Railway
This is caused by a stale build cache where the cached apt package indexes have outdated GPG signatures. Set the environment variable `NO_CACHE=1` on the service, trigger a new deploy, and once it succeeds you can remove `NO_CACHE=1` to re-enable caching. See [Build Configuration](https://docs.railway.com/builds/build-configuration#disable-build-layer-caching) for details.
17 days ago
nope, still not working.
this is the deployment with no cache:
install apt packages: ca-certificates git unzip zip
1s
Get:1 http://deb.debian.org/debian bookworm InRelease [151 kB]
Get:2 http://deb.debian.org/debian bookworm-updates InRelease [55.4 kB]
Get:3 http://deb.debian.org/debian-security bookworm-security InRelease [48.0 kB]
Err:1 http://deb.debian.org/debian bookworm InRelease
At least one invalid signature was encountered.
Err:2 http://deb.debian.org/debian bookworm-updates InRelease
At least one invalid signature was encountered.
Err:3 http://deb.debian.org/debian-security bookworm-security InRelease
At least one invalid signature was encountered.
Reading package lists...
W: GPG error: http://deb.debian.org/debian bookworm InRelease: At least one invalid signature was encountered.
E: The repository 'http://deb.debian.org/debian bookworm InRelease' is not signed.
W: GPG error: http://deb.debian.org/debian bookworm-updates InRelease: At least one invalid signature was encountered.
E: The repository 'http://deb.debian.org/debian bookworm-updates InRelease' is not signed.
W: GPG error: http://deb.debian.org/debian-security bookworm-security InRelease: At least one invalid signature was encountered.
E: The repository 'http://deb.debian.org/debian-security bookworm-security InRelease' is not signed.
copy .nvmrc cached
0ms
install mise packages: node
3s
mise node@22.22.2 [1/3] install
mise node@22.22.2 [1/3] download node-v22.22.2-linux-x64.tar.gz
mise node@22.22.2 [2/3] generate checksum node-v22.22.2-linux-x64.tar.gz
mise node@22.22.2 [3/3] extract node-v22.22.2-linux-x64.tar.gz
Build Failed: build daemon returned an error < failed to solve: process "sh -c apt-get update && apt-get install -y ca-certificates git unzip zip" did not complete successfully: exit code: 100 >
Status changed to Awaiting Railway Response Railway • 17 days ago
17 days ago
Hey, just manually reviewing this.
It doesn't look like you persisted the NO_CACHE=1 variable to your service before your last deploy which means the cache was never cleared. Can you please add that environment variable to the relevant service, then apply the change, and observe the new deploy.
If you're still having issues, please reach out again here.
Thanks and sorry for the impact here!
Status changed to Awaiting User Response Railway • 17 days ago
10 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 10 days ago