--remsh has security issues you should be aware of when using it on your local machine. Please be sure to read the security section at the bottom of this article.
Recently I learned about a fun option built into IEx called
--remsh or “remote shell”. It creates an IEx shell in the context of an Elixir node, allowing you to debug and reproduce issues inside a running application! Also note that despite the name,
--remsh can connect IEx to either local or remote nodes / applications. Here’s an example of how it works:
--remsh works in combination with two other options,
--cookie. The first is required and creates a named IEx shell to identify yourself to other nodes in the cluster. The second is not required but usually needed - it’s the the security cookie needed to access the node (often found under your home directory at
You could also wrap this up in a simple bash script to make it even easier to use:
reiex <environment name> to connect to your staging or production servers.
--remsh has security implications you should be aware of before using it. Remember - Elixir / Erlang nodes have complete access to all other nodes in a given cluster. So when you connect from your laptop via
--remsh, other nodes in that cluster can now access and make RPC calls on your local workstation. If you connect to a remote node that has been compromised from your local machine, your private files (even private SSH keys) would be up for grabs.
If you plan to do any serious work with remsh, I recommend reading Alex Weber’s writeup which goes in further detail about this issue. Alex also offers us a more secure alternative: create an SSH connection to your remote machine first and
remsh locally to the node from there. This can at least prevent node RPC calls from being made against your workstation as well as establish a more secure connection between your machine and the node.