Frontend unable to reach private backend domain
muhammadalvi
FREEOP

a year ago

Logs:

Starting Container

Listening on port 8080 url: http://0.0.0.0:8080

Stopping Container

[API] Using backend URL: http://odyssey-backend:8080

[API/trips POST] Request received at Next.js server

[API/trips POST] Backend URL: http://odyssey-backend:8080

[API/trips POST] Attempting fetch to: http://odyssey-backend:8080/trips

[API/trips POST] Error creating trip: TypeError: fetch failed

at node:internal/deps/undici/undici:12637:11

at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {

cause: Error: connect ECONNREFUSED fd12:82b:aff5:0:a000:46:e7ad:4bd6:8080

at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16)

at TCPConnectWrap.callbackTrampoline (node:internal/async_hooks:128:17) {

errno: -111,

code: 'ECONNREFUSED',

syscall: 'connect',

address: 'fd12:82b:aff5:0:a000:46:e7ad:4bd6',

port: 8080

}

}

[API/trips POST] Error type: TypeError

[API/trips POST] Error message: fetch failed

[API/trips POST] Error cause: Error: connect ECONNREFUSED fd12:82b:aff5:0:a000:46:e7ad:4bd6:8080

at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16)

at TCPConnectWrap.callbackTrampoline (node:internal/async_hooks:128:17) {

errno: -111,

code: 'ECONNREFUSED',

syscall: 'connect',

address: 'fd12:82b:aff5:0:a000:46:e7ad:4bd6',

port: 8080

}

$10 Bounty

3 Replies

Railway
BOT

a year ago

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

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


Status changed to Solved muhammadalvi 11 months ago


10 months ago

This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.

Status changed to Open brody 11 months ago


10 months ago

It looks like its binding to an ipv6 not an ipv4. Try binding to

::

instead of:

0.0.0.0


fra
HOBBY

10 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...