Hey there! We've found the following might help you get unblocked faster:

• 🧵 SSL PostgreSQL connection ?sslmode=disable safe?

• 🧵 posgres database issues.

• 🧵 PostgreSQL Database Connection Issues - ECONNRESET Errors

• 🧵 Postgres down? Can't connect to [roundhouse.proxy.rlwy.net](roundhouse.proxy.rlwy.net)

If you find the answer from one of these, please let us know by solving the thread!

I couldn't find answer

Current Status Summary

What's Working:

• backend is deploying successfully to Railway

• The server is starting and registering routes properly

• Health checks are passing

What's Not Working:

1. API Routing: Requests to /api/* endpoints aren't reaching your Express app

2. Database Connection: Still having connectivity issues even with private network

I can see some progress! Now it says "Database host: postgres.railway.internal" which confirms it's using the individual environment variables correctly. However, it's still getting an ENETUNREACH error, but this time it's a different IPv6 address.

Database Progress

• Private Network: Successfully configured to use postgres.railway.internal

• Environment Variables: Individual DB vars are being used correctly

• SSL Configuration: Properly configured for private network (no SSL required)

Remaining Issues

1. Database Connectivity: Even the private network shows ENETUNREACH errors, suggesting Railway's internal DNS resolution or network routing is having issues

2. API Routing: Express routes are registering successfully but requests aren't reaching the middleware stack

My Recommendation

I'm experiencing both database and API routing issues that appear to be Railway infrastructure-related.

Hey, have you tried redeploying the database? Furthermore, can you check if you have opted in for the IPv4 private networking feature flag which can be found at https://railway.com/account/feature-flags, it is best to opt out and redeploy your services if this is the case.

Working Endpoints:

• GET /health - Health check

• GET /api/suppliers/all - Returns mock supplier data (exactly what needed for frontend testing!)

• GET /api/suppliers/test - Test endpoint confirming supplier routes work

Issues Remaining:

• Database connectivity still failing (PostgreSQL ENETUNREACH IPv6 issues)

• Some endpoints like /api/products and /api/auth/login returning "API endpoint not found"

• Railway appears to be running a hybrid version - not exactly server.js or server-simple.js

I am not sure what "Railway appears to be running a hybrid version - not exactly server.js or server-simple.js" means, but can you confirm that you have done what I have suggested above? Additionally, you may check if the database is running at all, such as having an active deployment and being able to access the Database tab, which connects to your database via public networking, to confirm that this problem is isolated to private networking only.

Just to update. The problem was solved by this:

1. Fixed Database Connection Issues - Railway PostgreSQL external connections were broken, now using reliable local PostgreSQL

2. Set Up Local Development - PostgreSQL 14 running locally with stylemate database

3. Maintained Railway Production - production deployment will still use Railway's internal PostgreSQL

( Free local development + Railway production hosting)