Socket.io constant connection in terminal even though not installed
Answered
Argente Brun posted this in #help-forum
Argente BrunOP
I'm building a NextJS project in VSCode and since today, I've been randomly getting this in the Terminal when I do npm run dev:
GET /socket.io?X_LOCAL_SECURITY_COOKIE=&EIO=3&transport=polling&t=1723741295312-369 200 in 22ms
the same message is repeating constantly every couple of seconds, what I don't get is I'm not using socket.io in my project and I'm not aware of any other installed libraries that depend on it so where could this be coming from?
The same thing happens in a different project I open once I start the server
My info from running npx next info:
Operating System:
Platform: win32
Arch: x64
Version: Windows 10 Pro
Available memory (MB): 32725
Available CPU cores: 8
Binaries:
Node: 20.16.0
npm: N/A
Yarn: N/A
pnpm: N/A
Relevant Packages:
next: 14.2.5 // Latest available version is detected (14.2.5).
eslint-config-next: N/A
react: 18.3.1
react-dom: 18.3.1
typescript: 5.5.3
Next.js Config:
output: N/A
GET /socket.io?X_LOCAL_SECURITY_COOKIE=&EIO=3&transport=polling&t=1723741295312-369 200 in 22ms
the same message is repeating constantly every couple of seconds, what I don't get is I'm not using socket.io in my project and I'm not aware of any other installed libraries that depend on it so where could this be coming from?
The same thing happens in a different project I open once I start the server
My info from running npx next info:
Operating System:
Platform: win32
Arch: x64
Version: Windows 10 Pro
Available memory (MB): 32725
Available CPU cores: 8
Binaries:
Node: 20.16.0
npm: N/A
Yarn: N/A
pnpm: N/A
Relevant Packages:
next: 14.2.5 // Latest available version is detected (14.2.5).
eslint-config-next: N/A
react: 18.3.1
react-dom: 18.3.1
typescript: 5.5.3
Next.js Config:
output: N/A
Answered by Argente Brun
So I've managed to find the solution thanks to someone on a different server who pointed me to this article:
https://superuser.com/questions/1448490/how-to-find-source-of-traffic-to-socket-io-on-win-10-desktop
Turns out is was related to the Nvidia GeForce Experience app, which did have an update yesterday. I noticed that the app wouldn't open and I got a generic error - same as the user in the article above. I decided to completely uninstall the app and lo and behold, the socket.io connections stopped. Very strange. I haven't reinstalled the app yet but when I do I will disable the game overlay/shadowplay features since I don't use them anyway.
https://superuser.com/questions/1448490/how-to-find-source-of-traffic-to-socket-io-on-win-10-desktop
Turns out is was related to the Nvidia GeForce Experience app, which did have an update yesterday. I noticed that the app wouldn't open and I got a generic error - same as the user in the article above. I decided to completely uninstall the app and lo and behold, the socket.io connections stopped. Very strange. I haven't reinstalled the app yet but when I do I will disable the game overlay/shadowplay features since I don't use them anyway.
3 Replies
@Argente Brun I'm building a NextJS project in VSCode and since today, I've been randomly getting this in the Terminal when I do npm run dev:
GET /socket.io?X_LOCAL_SECURITY_COOKIE=&EIO=3&transport=polling&t=1723741295312-369 200 in 22ms
the same message is repeating constantly every couple of seconds, what I don't get is I'm not using socket.io in my project and I'm not aware of any other installed libraries that depend on it so where could this be coming from?
The same thing happens in a different project I open once I start the server
My info from running npx next info:
**Operating System:**
Platform: win32
Arch: x64
Version: Windows 10 Pro
Available memory (MB): 32725
Available CPU cores: 8
**Binaries:**
Node: 20.16.0
npm: N/A
Yarn: N/A
pnpm: N/A
**Relevant Packages:**
next: 14.2.5 // Latest available version is detected (14.2.5).
eslint-config-next: N/A
react: 18.3.1
react-dom: 18.3.1
typescript: 5.5.3
**Next.js Config:**
output: N/A
Rhinelander
did you try running it in the incognito... i had same problem last week it turns out it was one of my chrome extensions and when i deleted it it worked fine.
Argente BrunOP
Thanks for the suggestion. I was about to try that but just realised I don't even need to open the browser, it is actually happening in the VSCode terminal regardless once npm run dev is entered
Argente BrunOP
So I've managed to find the solution thanks to someone on a different server who pointed me to this article:
https://superuser.com/questions/1448490/how-to-find-source-of-traffic-to-socket-io-on-win-10-desktop
Turns out is was related to the Nvidia GeForce Experience app, which did have an update yesterday. I noticed that the app wouldn't open and I got a generic error - same as the user in the article above. I decided to completely uninstall the app and lo and behold, the socket.io connections stopped. Very strange. I haven't reinstalled the app yet but when I do I will disable the game overlay/shadowplay features since I don't use them anyway.
https://superuser.com/questions/1448490/how-to-find-source-of-traffic-to-socket-io-on-win-10-desktop
Turns out is was related to the Nvidia GeForce Experience app, which did have an update yesterday. I noticed that the app wouldn't open and I got a generic error - same as the user in the article above. I decided to completely uninstall the app and lo and behold, the socket.io connections stopped. Very strange. I haven't reinstalled the app yet but when I do I will disable the game overlay/shadowplay features since I don't use them anyway.
Answer