Version
v24.18.1
Platform
Linux ssh2 6.18.43-alwaysdata #1 SMP PREEMPT_DYNAMIC Fri Aug 7 07:39:43 UTC 2026 x86_64 GNU/Linux
Subsystem
No response
What steps will reproduce the bug?
- Run a HTTP server (code below)
- Try to connect to it (via e.g. python, netcat, a browser etc.)
code:
const http = require("http");
const server = http.createServer((req,res)=>{
res.writeHead(200, "Content-Type", "text/plain");
res.write("ok");
res.end();
});
server.listen({ port: 8300 }, ()=> {
console.log("Server is running");
});
I also tried all the following:
server.listen({ port: 8300, host: "::" }, ()=> {
console.log("Server is running");
});
server.listen({ port: 8300, host: "::", ipv6Only: true }, ()=> {
console.log("Server is running");
});
server.listen({ port: 8300, host: "", ipv6Only: true }, ()=> {
console.log("Server is running");
});
server.listen({ port: 8300, host: "0.0.0.0", ipv6Only: true }, ()=> {
console.log("Server is running");
});
server.listen({ port: 8300, host: "::1", ipv6Only: true }, ()=> {
console.log("Server is running");
});
server.listen({ port: 8300, host: "" }, ()=> {
console.log("Server is running");
});
server.listen(8300, "::", ()=> {
console.log("Server is running");
});
server.listen(8300, "", ()=> {
console.log("Server is running");
});
// maybe even more i forgot
How often does it reproduce? Is there a required condition?
TCPv4 must not be available on the OS.
For example, netstat -lntp must say this:
netstat: no support for `AF INET (tcp)' on this system.
netstat -lntp6 must not say that, however - instead, it should succeed:
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
What is the expected behavior? Why is that the expected behavior?
The server should be accessible
What do you see instead?
No error is thrown or logged, however, I cannot connect to the server in any imaginable way
Additional information
Thx for the ai-generated slop which is node.js nowadays.
Why does every single project have to use this?
It's not like I have a choice on whether to use node.js or not, if I don't want to spend a lot of money nor a lot of time, and I'm trying to host something in javascript, I do have to use Node.js. And there's only 1, one single Node.js alternative that doesn't use AI, that seems good, that I found. Yeah, I love my life...
Version
v24.18.1
Platform
Subsystem
No response
What steps will reproduce the bug?
code:
I also tried all the following:
How often does it reproduce? Is there a required condition?
TCPv4 must not be available on the OS.
For example,
netstat -lntpmust say this:netstat -lntp6must not say that, however - instead, it should succeed:What is the expected behavior? Why is that the expected behavior?
The server should be accessible
What do you see instead?
No error is thrown or logged, however, I cannot connect to the server in any imaginable way
Additional information
Thx for the ai-generated slop which is node.js nowadays.
Why does every single project have to use this?
It's not like I have a choice on whether to use node.js or not, if I don't want to spend a lot of money nor a lot of time, and I'm trying to host something in javascript, I do have to use Node.js. And there's only 1, one single Node.js alternative that doesn't use AI, that seems good, that I found. Yeah, I love my life...