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
Describe the bug
Erlang ls in stdio mode still starts a server on 0.0.0.0 with a random port.
The context here is that I'm trying to add erlang_ls to replit.com but Replit exposes things on 0.0.0.0 to the world, and we don't want to do that in this case.
To Reproduce
erlang_ls --transport stdio
server starts at random port on 0.0.0.0 host
Expected behavior
Either no server is started, but if that's necessary for running the language server i expect it to start on 127.0.0.1 (localhost) instead.
Actual behavior
Explained before
Context
erlang_ls version (tag/sha): any version
Editor used: any
LSP client used: any
The text was updated successfully, but these errors were encountered:
Hi @masad-frost , Erlang LS uses Erlang distribution to have the Language Server talking to the "project node" (e.g. for reloading code on save). This will result in a daemon (EPMD, Erlang Port Mapper Daemon) starting at a random port. I guess that's what you are referring to. You should be able to configure this behaviour using Environment Variables. See, for example, https://www.erlang.org/doc/man/epmd.html.
Describe the bug
Erlang ls in stdio mode still starts a server on 0.0.0.0 with a random port.
The context here is that I'm trying to add erlang_ls to replit.com but Replit exposes things on 0.0.0.0 to the world, and we don't want to do that in this case.
To Reproduce
erlang_ls --transport stdio
Expected behavior
Either no server is started, but if that's necessary for running the language server i expect it to start on 127.0.0.1 (localhost) instead.
Actual behavior
Explained before
Context
erlang_ls
version (tag/sha): any versionThe text was updated successfully, but these errors were encountered: