In Next.js, not using sockets but getting GET 404

Question

There was another post like this, but the only answer it had was to just restart, which didn't work for me.

I added sockets to my project for the first time, it wasn't working so i reverted to a previous commit to before I added anything socket related, before I downloaded npm packages for sockets too (there were no issues originally), and now I'm getting

GET /api/socket?EIO=4&transport=polling&t=y1kw1z5n 404 in 75ms

in the console. I don't have any files or folders related to sockets, nor the npm package installed. I did delete node_modules and .next and re-generated them. Closed out of VS code and re-started also re-started my computer, and cleared website cache, the issue is still there.

Mofe Ejegi · Accepted Answer · 2025-07-22 06:28:18Z

0

this issue may persist due to leftover cached routes or client code still referencing the socket API.

Here's what to check:

1. Make sure there's no socket-related code left in your _app.js or components.

2. Remove any rewrites in next.config.js for /api/socket.

3. Delete .next, node_modules, and package-lock.json, then run:

edited Jul 22 at 6:28

Mofe Ejegi

1,5835 gold badges20 silver badges30 bronze badges

answered Jul 18 at 17:05

Aman Rohilla

12 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

In Next.js, not using sockets but getting GET 404

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related