Hey everybody,
I already had a working Redwood app with baremetal deployment. Was deploying fine until recently, now I get a message informing me that All configured authentication methods failed
- apart from a system upgrade on my local machine, nothing much changedβ¦
Here is an excerpt from my deploy.toml
[[production.servers]]
host = "REMOTE IP"
username = "REMOTE USER"
agentForward = true
sides = ["api","web"]
packageManagerCommand = "yarn"
monitorCommand = "pm2"
path = "/var/www/app"
processNames = ["serve"]
repo = "git@MYPROJECT-REPO"
branch = "master"
keepReleases = 2
Again, this was working fine until recently.
I used this config along with the following deploy-prod.sh
script:
eval $(ssh-agent)
ssh-add ~/.ssh/MYPRIVATEKEY
yarn rw deploy baremetal production
Okay⦠So I went back to the documentation and added the following line to my deploy.toml
privateKeyPath = "/home/MYUSER/.ssh/MYPRIVATEKEY"
Then, when I try to run the deploy-prod.sh
I get:
β Connecting...
β Cannot parse privateKey: Unsupported OpenSSH private key type: ssh-ed25519
Cloning `master` branch...
Symlink .env...
Installing dependencies...
DB Migrations...
Building api...
Building web...
Symlinking current release...
Restarting serve process...
After restart: `yarn rw exec syncNotionUsers && yarn rw exec syncSlackUsers && yarn rw exec syncAbsences && yarn rw exec syncSupportStats`
Cleaning up old deploys...
Disconnecting...
Deploy failed:
ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
β Cannot parse privateKey: Unsupported OpenSSH private key type: ssh-ed25519 β
ββββββββββββββββββββββ
Do I really have to use a RSA key? Is this a redwood issue? When I do a normal ssh
into my remote box from the terminal it all works great. Just the deployment fails.
(Variables written in ALL CAPS are values that I want to keep private)