a month ago
Deployment ID: b35f78e0-8278-472c-aef9-4d1396fb86a1
Service ID: 8c5a3e03-e19a-44b8-912a-aee05546aee5
Error: secret Google not found during Python installation
Timeline: Started failing at 08:27 UTC; same commit succeeded at 08:16 UTC
Pinned Solution
a month ago
Fix 1: Add a dummy Google variable (quickest workaround)
You can solve this by adding a variable called Google in Railway's Variables tab. Railway
Go to your service → Variables → add:
Google = placeholder
This satisfies the build system's secret requirement without breaking anything at runtime. Your actual GOOGLE_MAPS_API_KEY stays as-is.
Fix 2: Check your build logs for the Railpack plan
The generated railpack-plan.json content shows up in your build logs — look for the section right before the line that says "load build definition from railpack-plan.json". If there's a secret called Google in the plan, it will be listed there. Railway
This helps confirm whether it's Railpack auto-generating that secret from googlemaps.
Fix 3: Add a railpack.json to override the secrets list
Create a railpack.json file in your project root to explicitly control what secrets are expected:
{
"$schema": "https://schema.railpack.com",
"deploy": {
"startCommand": "gunicorn app:app"}
}
Fix 4: Pin your Python version
You can set the RAILPACK_PYTHON_VERSION environment variable on your service to specify which Python version to use. Railway
Since you mentioned it previously built fine on 3.11 but is now pulling 3.13.13, add this variable:
RAILPACK_PYTHON_VERSION = 3.11
Version mismatches between builds can sometimes trigger new auto-detection behavior.
you can try this.
11 Replies
a month ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 1 month ago
a month ago
Do you have your "secret Google" set up as an environment variable in your service?
a month ago
No. The Only Google-related variable is GOOGLE_MAPS_API_KEY. Do I need one? is there a workaround?
a month ago
Can you provide more information (complete error logs if any)? The error message is a bit vague, so I'm not sure what the cause of the error is.
a month ago
i appreciate your help. i'm sorry i'm not so familiar with all these terms yet so i'm working a little slow.
a month ago
No worries, it's totally fine. Taking a screenshot of the failed deployment error logs might be helpful here.
a month ago
does this add context?
Build fails during pip install with: failed to solve: secret Google not found
Full sequence:
$ python -m venv /app/.venv
$ pip install -r requirements.txt
Build Failed: failed to solve: secret Google not found
requirements.txt contains: flask, twilio, gunicorn, googlemaps, APScheduler
No environment variable or build secret named "google" is configured. GOOGLE_MAPS_API_KEY is set as a runtime env var. Using railpack with nixpacks on Python 3.11. Same commit built successfully earlier today.
a month ago
install mise packages: python
Build Failed: build daemon returned an error < failed to solve: secret Google not found >
a month ago
The error "failed to solve: secret Google not found" suggests that you are trying to access/use an env variable called "Google" somewhere in your config files. I recommend you check/search for the usage of this variable in your codebase and remove it. Don't forget to check variables configured in your service as well.
a month ago
The build fails when Railpack tries to install Python via mise (a version manager). The BuildKit daemon is looking for an internal secret called "Google" that doesn't exist or isn't accessible.
Deployment ID: da0bd500-d371-460d-a85e-9b894982cfa0
Service ID: 8c5a3e03-e19a-44b8-912a-aee05546aee5
Error: failed to solve: secret Google not found during install mise packages: python
Build system: Railpack v0.26.1
Runtime: Python 3.13.13
This is a Railpack/BuildKit infrastructure issue — the build system is misconfigured or the secret is missing from the builder. Support will need to investigate the build infrastructure.
a month ago
Fix 1: Add a dummy Google variable (quickest workaround)
You can solve this by adding a variable called Google in Railway's Variables tab. Railway
Go to your service → Variables → add:
Google = placeholder
This satisfies the build system's secret requirement without breaking anything at runtime. Your actual GOOGLE_MAPS_API_KEY stays as-is.
Fix 2: Check your build logs for the Railpack plan
The generated railpack-plan.json content shows up in your build logs — look for the section right before the line that says "load build definition from railpack-plan.json". If there's a secret called Google in the plan, it will be listed there. Railway
This helps confirm whether it's Railpack auto-generating that secret from googlemaps.
Fix 3: Add a railpack.json to override the secrets list
Create a railpack.json file in your project root to explicitly control what secrets are expected:
{
"$schema": "https://schema.railpack.com",
"deploy": {
"startCommand": "gunicorn app:app"}
}
Fix 4: Pin your Python version
You can set the RAILPACK_PYTHON_VERSION environment variable on your service to specify which Python version to use. Railway
Since you mentioned it previously built fine on 3.11 but is now pulling 3.13.13, add this variable:
RAILPACK_PYTHON_VERSION = 3.11
Version mismatches between builds can sometimes trigger new auto-detection behavior.
you can try this.
a month ago
Deploy Success! Thank you! All i did was add the secret
Status changed to Solved passos • 17 days ago