Related

Join the DigitalOcean Community Community

Join 1M+ other developers and:

  • Get help and share knowledge in Q&A
  • Subscribe to topics of interest
  • Get courses & tools that help you grow as a developer or small business owner
 Join Now
how to remove node 4.1 from one-click app Question Question
node/express ERR_CONNECTION_REFUSED on static files Question Question

Question

I'm getting this error: WARNING: All keys were skipped because they already exist on the remote system. with Flight Plan

Posted February 9, 2016 15.2k views
Node.jsDigitalOcean

I’m using flightplan.js and following this video, https://www.youtube.com/watch?v=XxRuW1pfGTI

But I get the following error: 

rendezvousNode $ fly production 
✈ Running default:production
✈ Executing local task
localhost Copy files to remote hosts
localhost $ git ls-files
localhost ● ok
localhost $ rsync --files-from /var/folders/vf/38fsn66x58z04p9jkhkwbspm0000gn/T/4d0f74b86207e9a991820d952a8d25f3 -az --rsh="ssh -p22" ./ deploy@162.243.109.67:/tmp/rendezvous-1454984501830
localhost ● ok
✈ Local task finished after 41 s
✈ Connecting to '162.243.109.67'
● Error connecting to '162.243.109.67': All configured authentication methods failed
rendezvousNode $ ssh-copy-id deploy@162.243.109.67
/usr/local/bin/ssh-copy-id: INFO: attempting to log in with the new key(s), to filter out any that are already installed

/usr/local/bin/ssh-copy-id: WARNING: All keys were skipped because they already exist on the remote system.

What does this mean?

Add a comment
nikotzikas
By:
nikotzikas

Related

Join the DigitalOcean Community Community

Join 1M+ other developers and:

  • Get help and share knowledge in Q&A
  • Subscribe to topics of interest
  • Get courses & tools that help you grow as a developer or small business owner
 Join Now
how to remove node 4.1 from one-click app Question Question
node/express ERR_CONNECTION_REFUSED on static files Question Question

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
Submit an Answer
1 answer
ryanpq June 16, 2016

This error can usually be resolved either by

1.) Making sure that ~/.ssh for the user you are connecting as is owned by that user and the user has full permissions.

2.) Ensuring that PubkeyAuthentication yes is set in /etc/ssh/sshd_config and not commented out.

Reply Report
  • jeremybernardw July 13, 2016

    I have the same problem but I don’t understand your answer. Could you explain it a bit more?

    Reply Report
    • alexdo October 31, 2020

      Hello,

      You can open the sshd config file and make sure that the PubkeyAuthentication is set to yes. You can do a quick check with this command:

      cat /etc/ssh/sshd_config | grep PubkeyAuthentication

      Also as per ryanpq reply make sure that that ~/.ssh is owned by the user and has full permissions to it. You can check this by logging into the server and examine the directory and files permissions.

      Hope that this helps!
      Regards,
      Alex

      Reply Report

Related

Looking for something else?

Ask a new question Search for more help