2 years ago
The frontend is in vercel, today I paid my subscription again, I redeployed my project and I get a 503 error: "Application failed to respond" the project was working perfectly before with the configuration as it was, do I need to do something else?
11 Replies
2 years ago
try another redeploy
2 years ago
send your build and deploy logs please
[Region: us-west1]
==============
Using Nixpacks
==============
context: 126033706145d86fa374cf56a3b39dbf
╔════════ Nixpacks v1.21.2 ═══════╗
║ setup │ nodejs_21, npm-8_x ║
║─────────────────────────────────║
║ install │ npm ci ║
║─────────────────────────────────║
║ start │ npm start ║
╚═════════════════════════════════╝
#0 building with "default" instance using docker driver
#1 [internal] load build definition from Dockerfile
#1 transferring dockerfile: 2.22kB done
#1 DONE 0.0s
#2 [internal] load metadata for ghcr.io/railwayapp/nixpacks:ubuntu-1707782610
#2 DONE 0.2s
#3 [internal] load .dockerignore
#3 transferring context: 2B done
#3 DONE 0.0s
#4 [stage-0 1/8] FROM ghcr.io/railwayapp/nixpacks:ubuntu-1707782610@sha256:8f4b0fd95dc3311cf9a59f236d8d7d7f956fe21a2a1d64b53c82f12c4e859f09
#4 DONE 0.0s
#5 [internal] load build context
#5 transferring context: 368.98kB done
#5 DONE 0.0s
#6 [stage-0 2/8] WORKDIR /app/
#6 CACHED
#7 [stage-0 3/8] COPY .nixpacks/nixpkgs-bf744fe90419885eefced41b3e5ae442d732712d.nix .nixpacks/nixpkgs-bf744fe90419885eefced41b3e5ae442d732712d.nix
#7 CACHED
#8 [stage-0 4/8] RUN nix-env -if .nixpacks/nixpkgs-bf744fe90419885eefced41b3e5ae442d732712d.nix && nix-collect-garbage -d
#8 CACHED
#9 [stage-0 5/8] COPY . /app/.
#9 DONE 0.0s
#10 [stage-0 6/8] RUN --mount=type=cache,id=s/a80c82f0-c771-4f78-ae0e-1d3407cd5c6b-/root/npm,target=/root/.npm npm ci
#10 0.450 npm
WARN config production Use --omit=dev instead.
#10 4.713
#10 4.713 added 242 packages, and audited 243 packages in 4s
#10 4.713
#10 4.713 28 packages are looking for funding
Deploy:
npm WARN config production Use --omit=dev instead.
api@1.0.0 start
node index.js
ConnectionRefusedError [SequelizeConnectionRefusedError]: connect ECONNREFUSED 34.82.27.207:7552
at Client._connectionCallback (/app/node_modules/sequelize/lib/dialects/postgres/connection-manager.js:131:24)
at Client._handleErrorWhileConnecting (/app/node_modules/pg/lib/client.js:318:19)
at Client._handleErrorEvent (/app/node_modules/pg/lib/client.js:328:19)
at Connection.emit (node:events:515:28)
at Socket.reportStreamError (/app/node_modules/pg/lib/connection.js:57:12)
at Socket.emit (node:events:515:28)
at emitErrorNT (node:internal/streams/destroy:151:8)
at emitErrorCloseNT (node:internal/streams/destroy:116:3)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
parent: Error: connect ECONNREFUSED 34.82.27.207:7552
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1595:16) {
errno: -111,
code: 'ECONNREFUSED',
syscall: 'connect',
address: '34.82.27.207',
port: 7552
},
original: Error: connect ECONNREFUSED 34.82.27.207:7552
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1595:16) {
errno: -111,
code: 'ECONNREFUSED',
syscall: 'connect',
address: '34.82.27.207',
port: 7552
}
}
2 years ago
please use the bookmarklet to send the log file
Thanks Brody, is this enough?
ah 👌
2 years ago
yes that's correct, I'll have a look when I'm back at my computer
2 years ago
your app is still trying to connect to the deleted legacy database, please update the connection details.