api/auth/* not found on production

[curmande]

Description 🐜

Hello,

it is 2 days now which i struggling with totally not working as expected issue.

I tried everything - configure my project correctly by documentation, start x new projects to test it but i am not successful at all.

Sometimes it doesn't work when i develop and sometimes it works - if it not works in develop, then i got error - client failed to fetch - err_too_many_redirects

But everytime when i export my build using "npm build && npm export" and try to make it work on server it ALWAYS end up on

https://next-auth.js.org/errors#client_fetch_error session SyntaxError: Unexpected token < in JSON at position 0

which seems like bug in library or i really don't know what i am doing wrong

Yes i have NEXTAUTH_URL in my .env + i using custom credentials but when i want to use signin in build it seems like the /api/auth/* is just not working and **** with 404

also thin happens on https or http - still the same

any advice ?

Many thanks

Is this a bug in your own project?

Yes

How to reproduce ☕️

<button onClick={() => signIn()}>Sign in

Screenshots / Logs 📽

Environment 🖥

production

Contributing 🙌🏽

Yes, I am willing to help solve this bug in a PR

[balazsorban44]

Certainly a configuration issue. Do you have reproduction?

Make sure the .env file is present in production.

[balazsorban44]

You don't need to set env variables in next.config.js. See https://nextjs.org/docs/basic-features/environment-variables

NEXTAUTH_URL_INTERNAL might be useful here as well maybe?: https://next-auth.js.org/configuration/options#nextauth_url_internal

[curmande]

Actually i don't see env variable from .env but if i set it in next.config.js -> then i see it also when i building or running there is clear message that the .env is loading

"info - Loaded env from .../testing-typescript-next-auth-master/.env"

NEXTAUTH_URL_INTERNAL unfortunately doesn't help

Everything still the same

[curmande]

Also i need to mention that i was using "next build && next export" and my build is static site

● (SSG) automatically generated as static HTML + JSON (uses getStaticProps)

Maybe it will help

[balazsorban44]

If I understand this correctly, next export disables API routes, meaning you won't be able to use next-auth

https://nextjs.org/docs/messages/api-routes-static-export

There is nothing for us to do in this situation

[curmande]

Okay, then i think we are done. I choose another method for authorizations in my app

Thank you for your time and help