Skip to main content
Unix & Linux

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

6
  • I guess you need specify the key in -e argument that is ` ... -e ''ssh -p 50000 -i ~/path/to/pem/file.pem" ... ` Commented Mar 31, 2016 at 15:39
  • I've tried that, but doing so attempts to reference the remote server, where the file naturally does not exist. Commented Mar 31, 2016 at 15:42
  • yes indeed. I could suggest using ssh agent + agent forwarding - the things would go automatically, if that's acceptable option. If usure on how to implement that, i can provide it as an answer Commented Mar 31, 2016 at 15:46
  • Sure give that a go and if it works, it works :) What's surprising is I've updated by .ssh/config file and tried specifying the IdentifyFile and User defaults for hosts, but that doesn't seem to work either. It's almost like the reverse-port forwarding doesn't adhere to the .ssh/config rules? Not sure. Commented Mar 31, 2016 at 15:49
  • just one more point to check - pem extension may mean the key file is not in appropriate format. Anyways it's a good idea to add -v option to ssh command. Commented Mar 31, 2016 at 15:58