a month ago
Like the title says, switched over plan from Hobby to Free and Railway message said it would remove my active deployments for some reason and gave me these errors when re-trying to redeploy:
/mise/installs/poetry/2.4.1/venv/bin/python: error while loading shared libraries: libexpat.so.1: cannot open shared object file: No such file or directory
Pinned Solution
a month ago
Try clicking on your service and select "Deploy latest commit" or something similar.
3 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
Try clicking on your service and select "Deploy latest commit" or something similar.
Status changed to Solved brody • about 1 month ago
0x5b62656e5d
Try clicking on your service and select "Deploy latest commit" or something similar.
a month ago
I tried doing that for the latest successful commit and deploy, but got the same error. As soon as I downgraded from Hobby to Free, it removed all of my deploys and won't let me re-deploy the latest successful commit.
Status changed to Awaiting Conductor Response Railway • about 1 month ago
a month ago
Re-deploying the same previously-successful commit failing identically after the plan downgrade actually rules out a stale-build/cache issue — it points at the build environment itself changing with the plan switch, not the code or commit. This matches the libexpat.so.1 error: it's a missing system library (libexpat1) in whatever base image Free-tier builds are using. Worth explicitly adding it via nixpacks.toml:
Toml [phases.setup]
aptPkgs = ["libexpat1"]
or a RUN apt-get install -y libexpat1 step if you're on a Dockerfile — that should work regardless of plan. But it'd also help to flag to Railway directly whether Free and Hobby plans intentionally use different base builder images, since that's the actual root cause of why a working deploy broke on downgrade alone.