# Railway Support Request - Critical Production Issue

## URGENT: Container Being Killed - Google OAuth Broken

Date: October 9, 2025

Railway Project: PLWGSCREATIVEAPPAREL

Service: plwgscreativeapparel-production

Issue: Container crashes after startup, Google OAuth fails

---

## PROBLEM SUMMARY

Node.js container killed by Railway after 5-10 seconds with SIGTERM. Server starts successfully but Railway terminates it before HTTP requests can be processed.

Impact: Google OAuth login completely broken (404 on callback), website unresponsive.

---

## RAILWAY LOGS

```

Starting server...

Google OAuth client initialized

Registering OAuth callback route: GET /oauth/callback

Starting Express server on port 8080...

SERVER RUNNING on port 8080

Initializing admin credentials in background...

Admin credentials initialized

Stopping Container    ← Railway kills it here

npm error signal SIGTERM

```

---

## TECHNICAL CONFIG

```json

{

  "build": {

    "builder": "NIXPACKS",

    "buildCommand": "npm install && npm run build:css"

  },

  "deploy": {

    "startCommand": "node server.js",

    "healthcheckPath": "/api/health",

    "healthcheckTimeout": 300

  }

}

```

Server Code:

```javascript

const server = app.listen(PORT, '0.0.0.0', () => {

  console.log SERVER RUNNING on 0.0.0.0:${PORT});

});

app.get('/oauth/callback', async (req, res) => {

// OAuth logic

});

app.get('/api/health', (req, res) => {

  res.json({ status: 'healthy' });

});

```

Environment: All 40+ variables confirmed present in Railway.

---

## ATTEMPTED FIXES (15+)

### Healthcheck Config (Tried 6+ times)

- Changed from / to /api/health

- Increased timeout to 300s

- Removed healthcheck entirely

- Result: Same crash every time

### Static Middleware

- Removed app.use(express.static('.'))

- Added specific routes for /public, /css, /pages

- Result: Homepage broke, OAuth still fails

### Port Binding

- Changed to app.listen(PORT, '0.0.0.0')

- Result: Not yet tested

### Dependencies

- Fixed package-lock.json dotenv version

- Result: Build succeeds, runtime crash continues

---

## CODE VERIFICATION

OAuth Route: Defined at line 4079 in server.js

```javascript

app.get('/oauth/callback', async (req, res) => {

// Proper OAuth callback implementation

});

```

Frontend: Popup opens correctly to Google OAuth URL, redirects back to /oauth/callback

---

## QUESTIONS FOR RAILWAY

1. Why is container being killed? No error messages, just SIGTERM

2. Healthcheck logs? Need Railway's healthcheck failure details

3. Resource limits? Memory/CPU/network quotas being hit?

4. Load balancer issue? Server listening but requests not reaching it?

5. Platform issues? Network problems or service disruptions?

---

## EVIDENCE THIS IS RAILWAY ISSUE

Code works locally - OAuth functions perfectly

Server starts successfully - All initialization completes

No startup errors - Clean logs until Railway kills it

Only Railway kills container - Consistent across 15+ configs

---

## BUSINESS IMPACT

Critical: Google OAuth broken, customer auth blocked, business halted.

---

## SUPPORT REQUEST

Priority: URGENT - Production down

Issue: Container deployment failure

Response: Within 24 hours

Application code is correct and works locally. This appears to be a Railway platform issue.

Contact: PLWGS Creative Apparel

Site:https://plwgscreativeapparel.com

Project: PLWGSCREATIVEAPPAREL