search

nextauthjs / next-auth

Authentication for the Web.
https://authjs.dev
ISC License
24.78k stars 3.49k forks source link

Getting error "fetch failed" #9332

Closed twalker1998 closed 11 months ago

twalker1998 commented 11 months ago

Environment

System: OS: Linux 4.18 Red Hat Enterprise Linux 8.9 (Ootpa) CPU: (16) x64 Common KVM processor Memory: 21.38 GB / 31.14 GB Container: Yes Shell: 4.4.20 - /bin/bash Binaries: Node: 10.24.0 - /bin/node npm: 6.14.11 - /bin/npm

Reproduction URL

https://gitlab.com/twalk-tech/oklahoma-biological-survey/obis

Describe the issue

Logging in to the application results in a "fetch failed" error.

I am able to log in to the application in a test environment, but once it is deployed in production, I get a "fetch failed" error. The test and production environment are the exact same.

This is the third issue I've created for this. The first two times, it was closed due to an invalid reproduction URL. It is not invalid. If this is closed again please email me at twalker1998@ou.edu.

How to reproduce

Navigate to obis.ou.edu Click on the "User" icon in the top right Enter any credentials (valid or invalid credentials results in the same error) Notice the "fetch failed" error message in the URL

Expected behavior

Users should be able to login with valid credentials, or redirected to a page with an "Invalid Credentials" message with invalid credentials

Again, this works just fine in a test environment. Errors out only in production.

github-actions[bot] commented 11 months ago

We could not detect a valid reproduction link. Make sure to follow the bug report template carefully.

Why was this issue closed?

To be able to investigate, we need access to a reproduction to identify what triggered the issue. We need a link to a public GitHub repository. Example: (NextAuth.js example repository).

The bug template that you filled out has a section called "Reproduction URL", which is where you should provide the link to the reproduction.

What should I do?

Depending on the reason the issue was closed, you can do the following:

In general, assume that we should not go through a lengthy onboarding process at your company code only to be able to verify an issue.

My repository is private and cannot make it public

In most cases, a private repo will not be a sufficient minimal reproduction, as this codebase might contain a lot of unrelated parts that would make our investigation take longer. Please do not make it public. Instead, create a new repository using the templates above, adding the relevant code to reproduce the issue. Common things to look out for:

I did not open this issue, but it is relevant to me, what can I do to help?

Anyone experiencing the same issue is welcome to provide a minimal reproduction following the above steps by opening a new issue.

I think my reproduction is good enough, why aren't you looking into it quickly?

We look into every issue and monitor open issues for new comments.

However, sometimes we might miss a few due to the popularity/high traffic of the repository. We apologize, and kindly ask you to refrain from tagging core maintainers, as that will usually not result in increased priority.

Upvoting issues to show your interest will help us prioritize and address them as quickly as possible. That said, every issue is important to us, and if an issue gets closed by accident, we encourage you to open a new one linking to the old issue and we will look into it.

Useful Resources