-
Notifications
You must be signed in to change notification settings - Fork 27k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
E-connection reset error on getInitialProps when requestion from server. #9006
Comments
Please follow the issue template. https://github.com/zeit/next.js/issues/new/choose https://github.com/zeit/next.js/issues/new?template=8.Question_about_next.md
|
@para27rsh did you find the solution???. I am also experiencing this issue. |
@mnksingh1996 did you find the solution???. I am also experiencing this issue. |
I'm stuck with this as well.. Any news? I tried with NodeJs It happens when I run my nextjs ( It cannot reproduce this locally. |
I tried with axios and fetch and the error is similar. I stopped using getInitialProps for now. |
Did anyone fix this? I'm having the same issue since Next JS 11. In my case it's when I'm running two fetch calls in the same block of code fairly close together (they're both preceded by await, so they don't overlap). The second call consistently fails. |
Ahhh I've found my issue. In case this helps anyone, I eventually discovered in NextJS 11 I'd initially struggled to turn this off in express because I have a custom server. |
hi everyone |
Hi,
I am trying to send request to the below api:
https://stagecore.mentorz.com:8443/mentorz/api/v3/user/0/trendingmentors
And I am sometimes getting ECONNRESET error when requesting the api from server. But it is not replicating when calling from client(browser) or postman.
Also Sometimes the same thing works. The api works 6 out of 10 times on page refresh.
I have tried increasing timeout of node.js and switching networks and whatnot and nothing seems to work. Please find below the stack trace I am getting from axios error object.
The text was updated successfully, but these errors were encountered: