Skip to content
Fix supabase alias resolution PeopleSelect/creerlio-platform main
creerlio2026
OP

10 months ago

my App Builds and deploys successfully however after about 30 seconds it crashes. The above

$15 Bounty

6 Replies

10 months ago

Hey there!

We're working towards a fix with logs. Best place to track for live updates is here: https://status.railway.com/cmkoh9s6c004r10w1g7eexb9q.

So sorry for the inconvenience! After thats sorted though checking through them would be best to figure out whats going on.


Status changed to Awaiting User Response Railway • 10 months ago


noahd

Hey there! We're working towards a fix with logs. Best place to track for live updates is here: <https://status.railway.com/cmkoh9s6c004r10w1g7eexb9q>. So sorry for the inconvenience! After thats sorted though checking through them would be best to figure out whats going on.

creerlio2026
OP

10 months ago

thank you. is that the reason I'm not getting logs? Could this also be why it builds and then crashes after 30 seconds


Status changed to Awaiting Railway Response Railway • 10 months ago


10 months ago

That'd be it! The crashes are something unrelated. We have resolved it and logs should be coming back in. Do you see anything indicating why you had a crash?


Status changed to Awaiting User Response Railway • 10 months ago


creerlio2026
OP

10 months ago

crashed again


Status changed to Awaiting Railway Response Railway • 10 months ago


creerlio2026
OP

10 months ago

i am getting these about supabse etc. i have installed the variables. could i have done something wrong


sanjeet-the-insane
Top 10% Contributor

17 days ago

Your screenshots dated January 22, 2026 show a specific startup failure separate from the Supabase environment warnings. I cannot tell whether those logs still describe your current deployment.

The traceback reaches backend/main.py:357 while registering /api/resume/upload, and the next screenshot says:

Form data requires "python-multipart" to be installed.

This points to multipart support being unavailable to the Python environment importing that route, before it can handle requests. FastAPI's documentation explicitly requires python-multipart for file/form inputs.

Check the deployed backend's dependencies first:

I checked your public repository at commit 33a56f93cb8802aa7dc77f6f077d7b61e448db86. Its nixpacks.toml installs backend/requirements.txt into /opt/venv; the start command uses that same virtual environment. That backend dependency file does not declare python-multipart, while main.py still registers an UploadFile = File(...) parameter. If this is the configuration your Railway service consumes, the concrete dependency change belongs in backend/requirements.txt, not just the repository-root requirements file:

 fastapi
+python-multipart
 uvicorn[standard]

Test a compatible version with your existing dependency workflow and pin it if that is your release convention. A current repository snapshot is not proof of which commit/configuration your service deployed.

  1. Identify the dependency manifest and install command that this service actually builds from. In a monorepo, check its configured root directory; do not assume the repository-root manifest is used or change the root blindly.
  2. If missing, declare python-multipart as a runtime dependency in that existing manifest: for example, the consumed requirements.txt, or pyproject.toml plus its existing lockfile workflow. Use the project's existing package manager. If already declared, check that the build installs it into the Python environment used by the start command, rather than adding a duplicate or installing it manually in the running container.
  3. Test the reviewed dependency change locally or in staging before your normal deployment. Verify that route registration/startup no longer raises this error; that alone does not establish the whole application works.

Treat the environment warnings separately. The app reports missing DATABASE_URL, SUPABASE_URL, and SUPABASE_ANON_KEY; these are not the multipart exception. Check the exact names and references on the backend service in the intended environment, and whether intended variable changes were actually deployed. Railway documents service-scoped variables, shared-variable references, and staged changes. If those are correct, the app's configuration-loading code needs inspection. Do not post credential values or replace credentials just to suppress warnings.

I have not independently reproduced the title's Supabase alias-resolution issue. This addresses the failure visible in the dated screenshots, not a confirmed current end-to-end fix.

Disclosure: AI-assisted, source-checked answer. I inspected the published error screenshots and the pinned public source; I did not access your deployment or test a full dependency install or end-to-end repair. - Rivet /07, assisting Michael Squier


Welcome!

Sign in to your Railway account to join the conversation.

Loading...