Sven65
commented
9 months ago Also experiencing this issue. I've set the debug input to true, yet it appears that no debug information is output.
Closed sahgilbert closed 1 month ago
Sven65
commented
9 months ago Also experiencing this issue. I've set the debug input to true, yet it appears that no debug information is output.
LucasRoquilly
commented
8 months ago I have exact same problem. I followed every instruction in documentation but still same error :
ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
However it works using this Github Action : https://github.com/marketplace/actions/copy-via-ssh
sahgilbert
commented
8 months ago I have exact same problem. I followed every instruction in documentation but still same error :
ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remainHowever it works using this Github Action : https://github.com/marketplace/actions/copy-via-ssh
Do you have a full working example of a workflow.yml file, for this implementation, that you could share? That would be greatly appreciated, thank you.
real-F-00
commented
8 months ago i'm getting the same thing here, after days of going crazy i couldn't figure out what i did wrong, and apparently i'm not the only one facing this issue, i should mention that i'm running a hardened SSH server on Debian 12 using the configuration provided by ssh-audit.com simply trying to follow this guide i found on Youtube and using a separate user as opposed to the root user.
appleboy
commented
8 months ago @real-F-00 Have you solved the problem?
LucasRoquilly
commented
8 months ago I fixed my problem and ssh-action is now working. I feel stupid, I was using SSH_USERNAME in my yml file but the secret was called SSH_USER in GitHub Secrets 😑
Here is my working yml file for anyone it might help :
name: Deploy to VPS
on:
push:
branches:
- main # Adjust this to your main branch name
workflow_dispatch:
jobs:
deploy:
runs-on: ubuntu-latest
steps:
- name: Checkout code
uses: actions/checkout@v2
- name: Copy files to VPS
uses: appleboy/scp-action@master
with:
host: ${{ secrets.SSH_HOST }}
username: ${{ secrets.SSH_USER }}
key: ${{ secrets.SSH_PRIVATE_KEY }}
port: ${{ secrets.SSH_PORT }} # If your SSH server uses a different port, add this line
source: "public_html" # Adjust this to the directory or files you want to copy
target: "/var/www/domain.com/" # Adjust this to the destination directory on your VPS
- name: multiple command
uses: appleboy/ssh-action@v1.0.3
with:
host: ${{ secrets.SSH_HOST }}
username: ${{ secrets.SSH_USER }}
key: ${{ secrets.SSH_PRIVATE_KEY }}
port: ${{ secrets.SSH_PORT }}
script: |
chown -R openvc:www-data /var/www/domain.com/public_html
chmod -R 770 /var/www/domain.com/public_html`I fixed my problem and ssh-action is now working. I feel stupid, I was using SSH_USERNAME in my yml file but the secret was called SSH_USER in GitHub Secrets 😑
Here is my working yml file for anyone it might help :
name: Deploy to VPS on: push: branches: - main # Adjust this to your main branch name workflow_dispatch: jobs: deploy: runs-on: ubuntu-latest steps: - name: Checkout code uses: actions/checkout@v2 - name: Copy files to VPS uses: appleboy/scp-action@master with: host: ${{ secrets.SSH_HOST }} username: ${{ secrets.SSH_USER }} key: ${{ secrets.SSH_PRIVATE_KEY }} port: ${{ secrets.SSH_PORT }} # If your SSH server uses a different port, add this line source: "public_html" # Adjust this to the directory or files you want to copy target: "/var/www/domain.com/" # Adjust this to the destination directory on your VPS - name: multiple command uses: appleboy/ssh-action@v1.0.3 with: host: ${{ secrets.SSH_HOST }} username: ${{ secrets.SSH_USER }} key: ${{ secrets.SSH_PRIVATE_KEY }} port: ${{ secrets.SSH_PORT }} script: | chown -R openvc:www-data /var/www/domain.com/public_html chmod -R 770 /var/www/domain.com/public_html`
Does this deploy to Microsoft Azure? Or are you using a different Cloud Provider? Thanks
real-F-00
commented
8 months ago @real-F-00 Have you solved the problem?
Yes! after days of headaches i finally solved the issue, i think this should be added to the documentation (if it isn't already) but the problem was that the user i was trying to use was locked, to keep the user locked but allowing ssh access to it i used usermod -p '*' user that solved my issue.
LucasRoquilly
commented
8 months ago Does this deploy to Microsoft Azure? Or are you using a different Cloud Provider? Thanks
@sahgilbert This was made for deployment to a OVHCloud VPS (Virtual Private Server) but I believe it should work for any Linux machine
appleboy
commented
7 months ago @LucasRoquilly Can you provide the ssh username and password through email (appleboy.tw AT gmail.com). Maybe I can try it and get you back soon?
Thanks.
appleboy
commented
7 months ago @LucasRoquilly
I will try out OVHCloud and promptly inform you if the product becomes available.
appleboy
commented
7 months ago Sorry, I misunderstood @LucasRoquilly. The issue lies with @sahgilbert problem on Azure. I will find time to test the issue on Azure again.
RishabhBajpai97
commented
4 months ago Hey guys, changing the version for master for ssh worked for me. `steps:
appleboy
commented
4 months ago @RishabhBajpai97
I think the behavior of the master version is consistent with the v1.0.3 version. There should be no differences. Could you please provide the following detailed information:
RishabhBajpai97
commented
4 months ago @RishabhBajpai97
I think the behavior of the
masterversion is consistent with thev1.0.3version. There should be no differences. Could you please provide the following detailed information:
- SSH version and sshd_config content
- Ubuntu version?
- GitHub Actions logs.
Sure i will be happy to.....
# This is the sshd server system-wide configuration file. See
# sshd_config(5) for more information.
# This sshd was compiled with PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
# The strategy used for options in the default sshd_config shipped with
# OpenSSH is to specify options with their default value where
# possible, but leave them commented. Uncommented options override the
# default value.
Include /etc/ssh/sshd_config.d/*.conf
#Port 22
#AddressFamily any
#ListenAddress 0.0.0.0
#ListenAddress ::
#HostKey /etc/ssh/ssh_host_rsa_key
#HostKey /etc/ssh/ssh_host_ecdsa_key
#HostKey /etc/ssh/ssh_host_ed25519_key
# Ciphers and keying
#RekeyLimit default none
# Logging
#SyslogFacility AUTH
#LogLevel INFO
# Authentication:
#LoginGraceTime 2m
#PermitRootLogin prohibit-password
#StrictModes yes
#MaxAuthTries 6
#MaxSessions 10
#CASignatureAlgorithms +ssh-rsa
#PubkeyAuthentication yes
# Expect .ssh/authorized_keys2 to be disregarded by default in future.
#AuthorizedKeysFile .ssh/authorized_keys .ssh/authorized_keys2
#AuthorizedPrincipalsFile none
#AuthorizedKeysCommand none
#AuthorizedKeysCommandUser nobody
# For this to work you will also need host keys in /etc/ssh/ssh_known_hosts
#HostbasedAuthentication no
# Change to yes if you don't trust ~/.ssh/known_hosts for
# HostbasedAuthentication
#IgnoreUserKnownHosts no
# Don't read the user's ~/.rhosts and ~/.shosts files
#IgnoreRhosts yes
# To disable tunneled clear text passwords, change to no here!
#PasswordAuthentication yes
PermitEmptyPasswords no
# Change to yes to enable challenge-response passwords (beware issues with
# some PAM modules and threads)
KbdInteractiveAuthentication no
# Kerberos options
#KerberosAuthentication no
#KerberosOrLocalPasswd yes
#KerberosTicketCleanup yes
#KerberosGetAFSToken no
# GSSAPI options
#GSSAPIAuthentication no
#GSSAPICleanupCredentials yes
#GSSAPIStrictAcceptorCheck yes
#GSSAPIKeyExchange no
# Set this to 'yes' to enable PAM authentication, account processing,
# and session processing. If this is enabled, PAM authentication will
# be allowed through the KbdInteractiveAuthentication and
# PasswordAuthentication. Depending on your PAM configuration,
# PAM authentication via KbdInteractiveAuthentication may bypass
# the setting of "PermitRootLogin prohibit-password".
# If you just want the PAM account and session checks to run without
# PAM authentication, then enable this but set PasswordAuthentication
# and KbdInteractiveAuthentication to 'no'.
UsePAM yes
#AllowAgentForwarding yes
#AllowTcpForwarding yes
#GatewayPorts no
X11Forwarding yes
#X11DisplayOffset 10
#X11UseLocalhost yes
#PermitTTY yes
PrintMotd no
#PrintLastLog yes
#TCPKeepAlive yes
#PermitUserEnvironment no
#Compression delayed
#ClientAliveInterval 0
#ClientAliveCountMax 3
#UseDNS no
#PidFile /run/sshd.pid
#MaxStartups 10:30:100
#PermitTunnel no
#ChrootDirectory none
#VersionAddendum none
# no default banner path
#Banner none
# Allow client to pass locale environment variables
AcceptEnv LANG LC_*
# override default of no subsystems
Subsystem sftp /usr/lib/openssh/sftp-server
# Example of overriding settings on a per-user basis
#Match User anoncvs
# X11Forwarding no
# AllowTcpForwarding no
# PermitTTY no
# ForceCommand cvs server`
======END====== 2024/06/15 22:50:28 ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
This one for master :
Will download drone-ssh-1.7.4-linux-amd64 from https://github.com/appleboy/drone-ssh/releases/download/v1.7.4 % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
100 5580k 100 5580k 0 0 9401k 0 --:--:-- --:--:-- --:--:-- 9401k ======CMD====== docker pull /lets-talk:$GITHUB_SHA docker stop lets-talk || true docker rm lets-talk || true docker run -d -p 3000:3000 --name lets-talk /lets-talk:$GITHUB_SHA
======END====== err: invalid reference format err: Error response from daemon: No such container: lets-talk err: Error response from daemon: No such container: lets-talk err: docker: invalid reference format. err: See 'docker run --help'. 2024/06/15 23:31:09 Process exited with status 125 Error: Process completed with exit code 1.
I did get error but it was because of docker commands. However i did get logged in. Please do let me know if i am wrong. I thought that it worked for me so i should share it.
mathurinhauville
commented
4 months ago I had exactly the same problem. First, I noticed that my variables did not have the same names in my YAML file and in the secrets repository. Then I realized that I had a passphrase for my private key, so I added it to my YAML file. Finally, the problem was that my key copy contained line breaks. I removed them from each line, and everything worked.
This is my YAML file
- name: Deploy to server via SSH
uses: appleboy/ssh-action@master
with:
host: ${{ secrets.SSH_HOST }}
username: ${{ secrets.SSH_USER }}
key: ${{ secrets.SSH_PRIVATE_KEY }}
passphrase: ${{ secrets.SSH_PASSPHRASE }}
script: whoami(It's a fake private key)
mohammed5420
commented
3 months ago I had exactly the same problem. First, I noticed that my variables did not have the same names in my YAML file and in the secrets repository. Then I realized that I had a passphrase for my private key, so I added it to my YAML file. Finally, the problem was that my key copy contained line breaks. I removed them from each line, and everything worked.
This is my YAML file
- name: Deploy to server via SSH uses: appleboy/ssh-action@master with: host: ${{ secrets.SSH_HOST }} username: ${{ secrets.SSH_USER }} key: ${{ secrets.SSH_PRIVATE_KEY }} passphrase: ${{ secrets.SSH_PASSPHRASE }} script: whoamiThis is my initial private key when I copied it from my terminal
This is after I removed the line breaks
Sorry but it's better not to share your private keys
appleboy
commented
3 months ago @aswanth6000 I don't know what you mean. This repo is appleboy/ssh-action
100001010
commented
3 months ago master
I changed to master and passed, but I am a super novice, I hope I can help everyone.
iMohammadd
commented
2 months ago use your local machine private key instead of your vps pvk
chibyk101
commented
2 months ago use your local machine private key instead of your vps pvk
I just followed your comment and it didn't work
it shouldn't, since the handshake is not between my local machine & GitHub runners, but rather btw my VPS & GitHub
chibyk101
commented
2 months ago I have this same issue, I copied a working workflow to a new repo and it didn't work
name: Deploy to VPS
on:
push:
branches:
- dev
jobs:
deploy:
runs-on: ubuntu-latest
steps:
- name: Checkout code
uses: actions/checkout@v2
- name: Deploy to VPS
uses: appleboy/ssh-action@master
with:
host: ${{ secrets.VPS_HOST }}
username: ${{ secrets.VPS_USER }}
key: ${{ secrets.VPS_KEY }}
script: |
cd /var/www/domain.dev
git pull origin dev
composer install --no-interaction --prefer-dist
php artisan migrate:fresh --seed
I removed the secrets and added them again and it worked I can't tell what the problem was
Arafatmollik1
commented
2 months ago I had exactly the same problem. First, I noticed that my variables did not have the same names in my YAML file and in the secrets repository. Then I realized that I had a passphrase for my private key, so I added it to my YAML file. Finally, the problem was that my key copy contained line breaks. I removed them from each line, and everything worked.
This is my YAML file
- name: Deploy to server via SSH uses: appleboy/ssh-action@master with: host: ${{ secrets.SSH_HOST }} username: ${{ secrets.SSH_USER }} key: ${{ secrets.SSH_PRIVATE_KEY }} passphrase: ${{ secrets.SSH_PASSPHRASE }} script: whoamiThis is my initial private key when I copied it from my terminal
This is after I removed the line breaks
(It's a fake private key)
This worked for me thanks
piyushhanchate
commented
2 months ago I was facing the same issue and spent hours trying to resolve it. Turns out, it was a version issue. Got resolved for me once I started using: appleboy/ssh-action@master
andrewbenrichard
commented
2 months ago I was facing the same issue and spent hours trying to resolve it. Turns out, it was a version issue. Got resolved for me once I started using:
appleboy/ssh-action@master
This fixed it for me.
advancedsoftwarecanada
commented
1 month ago appleboy/ssh-action@master
Confirming fix.
Nehyan9895
commented
1 month ago I was facing the same issue and spent hours trying to resolve it. Turns out, it was a version issue. Got resolved for me once I started using:
appleboy/ssh-action@master
Broo. Thank you so much. I was sitting for around 8 hours on this and it worked after I changed it
usman61
commented
1 month ago I was facing the same issue and spent hours trying to resolve it. Turns out, it was a version issue. Got resolved for me once I started using:
appleboy/ssh-action@master
it works.
chinemeze847
commented
1 month ago worked for me appleboy/ssh-action@master, thanks
appleboy
commented
1 month ago I bump the new version appleboy/ssh-action@v1.1.0. Please try it out.
I have an Asp.Net Core (.Net 8.0) app, straight out of the box from Visual Studio for Mac.
I'm using a MacBook Pro (Silicon chip).
I have generated an SSH RSA key pair on my local mac machine.
I have created an Azure Virtual Machine running Linux.
When I created the Virtual Machine in the Azure Portal, I uploaded my public key which was generated by my previous step.
I have added the 3 required secrets to the source code repository on GitHub, based on the secrets variables in the deploy.yml file, as per the below screenshot:
I'm getting the following error when trying to deploy Asp.Net Core to an Azure Virtual Machine using GitHub Actions & appleboy/ssh-action:
ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
I have created a deploy.yml file for the deployment via GitHub Actions, with the following contents
`name: Deploy to Azure VM
on: push: branches:
main
jobs: deploy: runs-on: ubuntu-latest
steps:
name: Checkout Repository uses: actions/checkout@v2
name: Setup .NET Core uses: actions/setup-dotnet@v1 with: dotnet-version: '8.x'
name: Build and Publish run: dotnet publish -c Release -o publish
name: Deploy to Azure VM uses: appleboy/ssh-action@master with: host: ${{ secrets.AZURE_VM_HOST }} # Azure VM IP address or hostname username: ${{ secrets.AZURE_VM_USERNAME }} key: ${{ secrets.AZURE_VM_SSH_PRIVATE_KEY }} script: | whoami cd /home/runner/work/ git pull origin main sudo systemctl restart nameofmyvirtualmachineinmicrosoftazuregoeshere ` How do I debug this error? Are there some debug settings that I can add to my deploy.yml file?
Thanks