You do not need to restart the ssh daemon.

Add the following 1 line configuration in this file.

Problem: ssh -i server_user_name.pem error - ssh failed Permission denied (publickey, gssapi-keyex, gssapi-with-mic). A command line is a way of interacting with a computer by typing text-based commands to it and recei. It had nothing to do with the settings on the local or remote servers. In order to use Certbot for most purposes, you’ll need to be able to install and run it on the command line of your web server, which is usually accessed over SSH. So he found out that the recent version of OpenSSH after the High Sierra Upgrade on mac caused this issue. Somewhere while googling, I noticed a used mentioned on a Github issues that he was not able to connect to AWS EC2 instance running Ubuntu via ssh from his mac. So I spent a few hours to debug this, compared both /etc/ssh/ssh_config and /etc/ssh/sshd_config with same files on my local, restarted the sshd service, perform ssh-add and ssh-add-l but nothing worked out. From any linux based machine, I was able to access connect or ssh to the server. I have two users eng_qa and support_qa which are created on the server machines running on CentOS 6.10. However on macOS, I came across a very weird issue. Those who work with AWS quite often are very well versed with it, I suppose. pem file are quite successful when it comes to connecting to the server machine using SSH in the world of cloud.

One very quick article if you’re struggling to connect to the remote server machine using.

Install ssh for mac