-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
SSH unsupported option "accept-new" #2908
Comments
Ok, so it looks like you can get around this bug if you define git_ssh_command as "ssh". set('git_ssh_command', 'ssh'); |
A note here that you'd think the answer would be "upgrade the version of openssh on your server" since the accept-new option was introduced in 7.6... However this is going to be a common problem as AmazonLinux only officially supports openssh v7.4. |
This is bad :( accept-new is really helpful. Will write a doc. |
Same problem. I asked hosting to be transferred to another server with |
@antonmedv Could this be mentioned somewhere clearly in the docs? I couldn't get around this issue until I searched the github issues and found the |
* Require deployer/deployer 7.1 * Don't suggest deprecated deployer/dist package * Remove removed options * Replace locateBinaryPath() with which() * Replace inventory() with import() * Rename task success to deploy:success and cleanup to deploy:cleanup. * Remove duplicate Composer action * Override git_ssh_command to fix git clone command deployphp/deployer#2908 * Remove duplicate deploy task which are now included in deploy:prepare * Add reusable workflow * Update PHP and Deployer version used for deploy action * Remove parallel, set no-interaction * Use release_or_current_path so tasks can be used after a deployment too * Use selectors via labels to define which stage should be deployed * Add support for ACTIONS_STEP_DEBUG * Run printenv * Check for RUNNER_DEBUG * Update check for RUNNER_DEBUG * Set LANG to fix 'perl: warning: Setting locale failed.' * Update locale by default * Set LANG as step env
@antonmedv Issue may be closed. Or is there anything else I can help out with? |
Nice catch) it can be closed. |
Just wanted to leave a note here that adding |
Im using ubuntu 22.04 with "OpenSSH_8.9p1 Ubuntu-3ubuntu0.4, OpenSSL 3.0.2", but still facing
But when I manually cd to the directory and run the |
|
Fun fact: deployer successfully cloned the repo (so not suppose to have "Could not read from remote repository" error), but it error when executing I can cd to the directory Deployer: |
If using yaml , you can config it like below: config:
git_ssh_command: ssh |
Upvote & Fund
The text was updated successfully, but these errors were encountered: