-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using RSA Private Key to Deploy in EC2 #30
Comments
I have the same problem, that it is not clear to me, why my key is not accepted. |
I have the same problem trying to connect to a Digital Ocean Droplet. The key format is
my deploy script looks like this name: .NET
on:
push:
branches: [ master ]
jobs:
build:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
- name: Setup .NET
uses: actions/setup-dotnet@v1
with:
dotnet-version: 5.0.x
- name: Restore dependencies
run: dotnet restore
- name: Release Build
run: dotnet build --configuration Release --no-restore
- name: Test
run: dotnet test --verbosity normal
- name: Start Deploy
uses: garygrossgarten/github-action-scp@release
with:
local: /home/runner/work/MfWebDevApiCore/MfWebDevApiCore/MfWebDevServiceNew/bin/Release
remote: var/www/MfWebDevServices
host: ${{ secrets.SSH_HOST }}
username: ${{ secrets.SSH_USERNAME }}
privateKey: ${{ secrets.SSH_KEY }}
rmRemote: true
dotfiles: true Full output from run:
EDIT: SOLVED, SSH key was encrypted with a passphrase |
@Dud3core-webdev I have had this same problem, how did u solve this? |
@matheusfrancisco I added my SSH passphrase with the call:
It worked every time after that |
Hello,
I'm trying to deploy the build of my app through the SCP directly in my EC2 instance, but I'm getting error in reading the key file (it is private RSA key from AWS).
Error:
Workflow config:
uses: garygrossgarten/github-action-scp@release
with:
local: "app.zip"
remote: "/home/ubuntu/"
host: ${{ secrets.AWS_HOST }}
username: "ubuntu"
privateKey: ${{ secrets.AWS_PEM }}
Am I doing something wrong? Or it does not support this type of key?
Thanks!
The text was updated successfully, but these errors were encountered: