You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
hexo server fails to bind to 127.0.0.1 while using node inspector. If you explicitly define the IP and port the same as that configured for Node Inspector, it will fail to start.
Do you mean that the default port of the hexo server conflicts with the debugger? You can specify a different port for hexo to avoid the conflict. I don't think this is a bug that needs fixing, as the port for either the debugger or the hexo server can be configured by the user. Whether it binds to 127.0.0.1 or localhost is not the main issue.
Problem
hexo server fails to bind to
127.0.0.1
while using node inspector. If you explicitly define the IP and port the same as that configured for Node Inspector, it will fail to start.However, if you don't define the IP and leave it to defaults, everything starts, but the browser doesn't reach the server over
127.0.0.1
...Related issue
127.0.0.1
with node inspector #275Environment
MacOS 13.2.1
node: v19.6.1
Hexo:
Expected behavior
Server should work Node inspector. How else does one troubleshoot issues if it won't bind on the same domain (IP) and port? IP alias?
The text was updated successfully, but these errors were encountered: