Socket hang up
See original GitHub issueWhen it starts generating the images after running npm run generate
, I get an error similar to the one below many times, is it because I am generating too many images? Maybe I need an interval?
ERROR request to http://localhost:56688/_image/local/_/w_1920_cover/villas/house.jpg failed, reason: socket hang up
I have 6 pages and each page has ~30 images:
<div
v-for="(image, index) of gallery"
:key="image"
>
<NuxtImage
:key="image"
:src="image"
sets="300, 600, 1280, 1920"
:legacy="true"
/>
</div>
Edit: maybe is because I am using composition API?
Issue Analytics
- State:
- Created 2 years ago
- Comments:6
Top Results From Across the Web
NodeJS - What does "socket hang up" actually mean?
It means that socket does not send connection end event within the timeout period. If you are getting the request for cheerio via...
Read more >NodeJS - What does socket hang up actually mean - Edureka
When a socket hang up is thrown, one of two things happens: When you're a customer, When you send a request to a...
Read more >Could not get any response socket hang up - Help - Postman
I am not able to Post to the server. I am receiving “Could not get any response” error. While checking the logs found...
Read more >502 Bad Gateway - Socket hang up | Apigee Edge
The error code [socket hang up][ECONNRESET] indicates that the target server has closed the connection with Edge Microgateway. This can be searched in...
Read more >Hang in There! (A solution to socket hang up) - Medium
(A solution to socket hang up). Recently, while watching a YouTube video about how to create a Node.js backend (Building a RESTful API...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Yeah, it seems that is doing too many calls at once, I’ve replaced this module completely with a custom node script using
sharp
and a batcher function, to avoid the socket hang up issue altogether.I still get this error when running
yarn generate
from my CI but I don’t have it when running locally … (I’m on 0.6.0). Any ideas ?