I have deployed a Django app to Railway, and while everything works fine in my local development server, the /accounts/login/ page throws a 404 error on the live server.

Live URL:

https://server-production-7653.up.railway.app/accounts/login

My Project Structure:

pgsql

CopyEdit

project-root/ ├── mysite/ │ └── urls.py ├── accounts/ │ ├── urls.py │ └── views.py ├── templates/ │ └── accounts/ │ └── login.html

Code Snapshots:

mysite/urls.py:

python

CopyEdit

from django.contrib import admin from django.urls import path, include urlpatterns = [ path('admin/', admin.site.urls), path('accounts/', include('accounts.urls')), ]

accounts/urls.py:

python

CopyEdit

from django.urls import path from django.contrib.auth import views as auth_views urlpatterns = [ path('login/', auth_views.LoginView.as_view(template_name='accounts/login.html'), name='login'), ]

settings.py:

python

CopyEdit

TEMPLATES = [ { 'BACKEND': 'django.template.backends.django.DjangoTemplates', 'DIRS': [ BASE_DIR / "templates" ], 'APP_DIRS': True, ... } ]

What I’ve Tried:

• Confirmed the templates/accounts/login.html exists and renders locally.

• Verified all files are pushed to GitHub.

• Confirmed Railway is deploying the latest commit.

• Tried accessing /accounts/ and /accounts/login/ — both give 404.

• No errors during deployment, and /admin/ works fine.

Suspicions:

• Template not being picked up in production?

• Git may not have tracked the templates/ folder earlier (already forced git add -f templates/).

• Could Railway have cached an old build?

Request:

Could anyone help me debug what I might be missing or doing wrong? Any tips to ensure the app correctly routes /accounts/login/ in production?

Thanks in advance!