internal connection error
4tendev
HOBBYOP

2 years ago

im trying to fetch data trough internal connection from my next app to nginx container

the public connections works ok but internal connection from next to nginx getting refused

TypeError: fetch failed

Sep 17 12:30:06

at Object.fetch (node:internal/deps/undici/undici:11730:11)

Sep 17 12:30:06

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

Sep 17 12:30:06

at async l (/app/.next/server/chunks/791.js:1:15607)

Sep 17 12:30:06

at async c (/app/.next/server/app/user/store/addproduct/page.js:1:12933) {

Sep 17 12:30:06

cause: Error: connect ECONNREFUSED fd12:d5b3:325::71:9b4a:a356:80

Sep 17 12:30:06

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

Sep 17 12:30:06

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

Sep 17 12:30:06

errno: -111,

Sep 17 12:30:06

code: 'ECONNREFUSED',

Sep 17 12:30:06

syscall: 'connect',

Sep 17 12:30:06

address: 'fd12:d5b3:325::71:9b4a:a356',

Sep 17 12:30:06

port: 80

Sep 17 12:30:06

},

Sep 17 12:30:06

digest: '1502078682'

Sep 17 12:30:06

}

dc995e0b-6c2b-4228-add9-fd64346b4281

the url that i tried already with are :

http://nginx.railway.internal:80

http://nginx.railway.internal

nginx.railway.internal

nginx.railway.internal:80

2 Replies

4tendev
HOBBYOP

2 years ago

Resolved


Status changed to Solved brody over 1 year ago


colombusah
HOBBY

a year ago

have the same issue , can you share ?

my ngnix serve correctly the fe but failed to proxy to an internal be


Status changed to Open Railway about 1 year ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...