Deploying to custom server

[daandegooijer]

Hi,

Im want to bring all our Next.js websites over from vercel to our own hosting solution. This hosting solution does not operate on localhost (or 127.0.0.1) but on another IP address. I can correctly start the Next.js server using the -H parameter.

But everytime i want to visit a locale on the site (i.e. example.com/nl) it gets a loopback to localhost (https://localhost:3000/nl)

The logs show the following:
`✓ Starting...
▲ Next.js 14.2.16

• Local: http://127.110.72.233:3000
• Network: http://127.110.72.233:3000

✓ Starting...
✓ Ready in 221ms`

Failed to proxy https://localhost:3000/nl AggregateError at internalConnectMultiple (node:net:1114:18) at afterConnectMultiple (node:net:1667:5) at TCPConnectWrap.callbackTrampoline (node:internal/async_hooks:130:17) { code: 'ECONNREFUSED', [errors]: [ Error: connect ECONNREFUSED ::1:3000 at createConnectionError (node:net:1634:14) at afterConnectMultiple (node:net:1664:40) at TCPConnectWrap.callbackTrampoline (node:internal/async_hooks:130:17) { errno: -111, code: 'ECONNREFUSED', syscall: 'connect', address: '::1', port: 3000 },

When i disable next-intl it works.

Does next-intl work without vercel?

[amannn]

But everytime i want to visit a locale on the site (i.e. example.com/nl) it gets a loopback to localhost (https://localhost:3000/nl)

Do you mean you get a redirect where the host is changed to localhost?

I have a feeling this could be an issue with a reverse proxy. Is there an internal proxy that calls the Next.js server with e.g. localhost instead of the public URL? Can you share more details about the hosting setup? Also the Node.js version you're using?

Can you try if you get the same error with this middleware instead of the one from next-intl?

export default function middleware(request: NextRequest) {
  if (request.nextUrl.pathname === '/') {
    const url = new URL('/de', request.url);
    return NextResponse.redirect(url.toString());
  }
}

… and then call /? Isolating the error a bit further would be really helpful here.

Does next-intl work without vercel?

Absolutely, yes—if you run npm run start locally you can verify this.

[daandegooijer]

Thanks for the fast reply!

If i go to our homepage https://frontend.foundation.ef2.builders/ It redirects to localhost:3000/nl. Thats because nl is our default language. But instead of going to our root domain, it goes to localhost.

The server is setup so it has a loopback to another ip address environment=HOST="127.110.72.233",PORT="3000"

Added the above code, the /nl does now work (changed /de to /nl). So it maybe has something to do with the middleware?
https://frontend.foundation.ef2.builders/nl

[amannn]

But so on https://frontend.foundation.ef2.builders/ the provided middleware sample is now running instead of the next-intl middleware, right?

It contains the broken redirect that causes the issue:

If you inspect your app locally, you're probably seeing a redirect to /nl instead, right?

Can you dig a bit into this and debug why NextResponse.redirect(…) causes the broken redirect in this case? Maybe if you add logging for request.url in your middleware, you can see the localhost header. Maybe the Next.js issue tracker has a bit more on this too …

As far as I know, next-intl really just follows the Next.js docs here.

[daandegooijer]

Thanks for the fast response, gonna dig into it :)

[daandegooijer]

Well, delved deeper and deeper. I removed the next-intl all together and added a single redirect in the middleware from the docs and i get the same result.

Asked the hosting provider if they can come up with a solution. Because normal rewrites are also a big part of our projects.

Thanks for the help!

[amannn]

That sounds great, would be cool if you could share the resolution then!

I also found these relevant parts in the Next.js source:

1. Call to relativizeURL
2. Implementation of relativizeURL
3. Implementation of initUrl

I think the issue really is that the host is not read correctly by Next.js and therefore not stripped out from the location header in the response.

[daandegooijer]

Too bad I still dont have a solution. We tried everything but redirects are not working correctly because of the headers. Currently rewriting them in the middleware doesnt work, because i get a 431 with an infinite loop.

So currently my only option is to use Vercel, which i really really don't want to.

[amannn]

I think Next.js tries to read the host header of the request. If it's not set, it uses localhost by default.

Maybe some logging in the middleware could help to see if that's set?

function middleware(request: NextRequest) {
  console.log(request.headers.get('host'));
}

If not, maybe that's something for your hosting solution to supply.