connect ECONNREFUSED 127.0.0.1:80

[imjamesku]

In my getServerSideProps, I want to make an API call to my next.js app's own API route. the function is as follows:

export async function getServerSideProps(context) {
    const searchParams = {
        startDate: moment().subtract(7, 'd').toDate(),
        endDate: moment().toDate(),
        geo: 'US'
    }
    const res = await axios.get(`/api/trends/date?start=${searchParams.startDate.toISOString()}&end=${searchParams.endDate.toISOString()}&geo=${searchParams.geo}`)
    return {
        props: {data: res}
    }
}

I get connect ECONNREFUSED 127.0.0.1:80. If I put the data fetching on the client side, it works. But I'd like to reder the data on the server side. How to I get the SSR to work?

[jamesmosier]

Next recommends you write your server code directly in getServerSideProps: https://nextjs.org/docs/basic-features/data-fetching#write-server-side-code-directly

Otherwise you'd have to put the fully qualified url in your axios.get(`https://my-domain.com/api/trends...`) because the server doesn't know what your domain is.

[rafaelnogueira1]

To use the second approach without problems with deploy for exempla, you can create a .env file and use a variable to store your api url and use that variable here axios.get(${process.envMY_VARIABLE_API}/api/trends...).
When you deploy, your server will have the same variables with different values.

[nickjuntilla]

This is crazy. You should be able to get data from a server at localhost.

[m3c-ode]

Could you be more explicit with the code, in terms of the solution you found?
I wonder hen, what is the point of developing your /api/ folder?

[amanbhatt26]

@m3c-ode I think client side data fetching is a use case for /api/ folder. We can make requests to /api/something using axios or fetch.

[sanalpanicker]

During the build, there is no server running. All server components are prerendered so they can be served during runtime/request time. So the reference to localhost during buildtime isn't going to work unless you have a dedicated server running on that port.

if you want to use the /api route use it with a real host that can serve your data to prerender pages.
/api routes that point to localhost should be used only with client side during runtime/request time ('use client'). At this point you have a server running at localhost that can serve your data.

I think its an issue with your mental model of hoe nextjs works- not an issue with nextjs.

[alexislefebvre]

I had the same error because of a typo, a / was missing after http:/. If you have the same error, check your URL.

[Ekundee]

Thanks so much. You saved my time

[leoplct]

In my case I had to replace http://localhost:1337/api with http://127.0.0.1:1337/api

[sanalpanicker]

During the build, there is no server running. All server components are prerendered so they can be served during runtime/request time. So the reference to localhost during buildtime isn't going to work unless you have a dedicated server running on that port.

if you want to use the /api route use it with a real host that can serve your data to prerender pages.
/api routes that point to localhost should be used only with client side during runtime/request time ('use client'). At this point you have a server running at localhost that can serve your data.

I think its an issue with your mental model of how nextjs works- not an issue with nextjs.

if its not working for you - probably you are using node version less than 17?

[ajnart]

Having the same issue. Had to rollback to v13.2.4 like @TaylanTatli suggested. Works now! Is there a new issue we can follow for this ? It is definitely not fixed @imjamesku

[Jxck]

any updates here ?

[alextenczar]

Issue still exists on 13.5.4. Reverting to 13.2.4 allowed for the build to execute without an error

[RaymondMwaura]

Many thanks sir 😤

[Mergeando]

I solved it by adding a new path in .env
NEXT_PUBLIC BASE_URL LOCAL=http://127.0.0.1:8000

[SoolaimanG]

hello
please how to do resolve this issue

[ajnart]

@Mergeando Can you explain more in details ? is the variable name NEXT_PUBLIC_BASE_URL_LOCAL ?

[ashwin-maurya]

Once check your next version. In my case I was using 13v which was causing the error. Upgraded to 14 and this solved the issue.