-
-
Notifications
You must be signed in to change notification settings - Fork 998
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
Problem: After updating to v2.10.2: "Permission denied (publickey,password)" #2098
Comments
I have the exact same problem, if the server is using password ( the invertory is set properly as password ) ssh connection tries to connect using public key instead of password and fails as unreachable. |
Same issue here |
ya i same setup and encouter same problem too 9:04:18 AM |
i downgrade back to v2.9.112 and it's back to normal |
Hi @fiftin, Sadly, no change:
|
Same here |
@johnyb0y , @Menschomat thank you! Reproduced the issue, fixing. |
@fiftin Confirmed working again with |
…2d72350 by renovate (#23577) This PR contains the following updates: | Package | Update | Change | |---|---|---| | [semaphoreui/semaphore](https://togithub.com/semaphoreui/semaphore) | patch | `v2.10.2` -> `v2.10.7` | --- > [!WARNING] > Some dependencies could not be looked up. Check the Dependency Dashboard for more information. --- ### Release Notes <details> <summary>semaphoreui/semaphore (semaphoreui/semaphore)</summary> ### [`v2.10.7`](https://togithub.com/semaphoreui/semaphore/releases/tag/v2.10.7) [Compare Source](https://togithub.com/semaphoreui/semaphore/compare/v2.10.2...v2.10.7) [![](https://img.shields.io/badge/semaphore\_2.10.7\_container_configurator-skyblue?style=for-the-badge\&logo=docker)](https://semaphoreui.com/install/docker/2\_10\_7/) [![ko-fi](https://img.shields.io/badge/support_semaphore-teal?style=for-the-badge\&logo=patreon)](https://www.patreon.com/semaphoreui) #### Features - Added support for Terraform code, OpenTofu code and Bash scripts. ![image](https://togithub.com/semaphoreui/semaphore/assets/914224/e29aea49-dbd4-488b-a7f4-dd71b0af8821) - Added usage examples. - Added DEBUG Docker image for remote debugging from Goland. #### Bugfixes - Fixed infinite "Waiting" status. - Reduced size of Docker image. - Fixed issue with authentication on the server with login/password ([semaphoreui/semaphore#2098) - Fixed `web_host` option usage in Docker image. - Docker Image: Fixed overriding config file options by empty `SEMAPHORE_ACCESS_KEY_ENCRYPTION` and `SEMAPHORE_WEB_ROOT` environment variables. - Web interface: Removed predefined variables from Environment form. - Fixed bug with supporting HTTP protocol. </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Enabled. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://togithub.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy40MTMuMiIsInVwZGF0ZWRJblZlciI6IjM3LjQxMy4yIiwidGFyZ2V0QnJhbmNoIjoibWFzdGVyIiwibGFiZWxzIjpbImF1dG9tZXJnZSIsInVwZGF0ZS9kb2NrZXIvZ2VuZXJhbC9ub24tbWFqb3IiXX0=-->
It is fixed in v2.10.6-beta but the issue reappears in v2.10.7 |
@Goldenflamer Works fine for me on 2.10.7:
|
ah I think I didn't delete the old latest tag image, my bad sorry |
Issue
Hello everyone,
this is just to let you know that I ran into this issue after updating to v2.10.2:
ANSIBLE_HOST_KEY_CHECKING: false
and I'm authenticating to my hosts via username/password. This has worked flawlessly before.-vvvv
, swapped some privacy details like username.Please let me know if there's anything else I can do to debug this.
Thank you!
Impact
Ansible (task execution)
Installation method
Docker
Database
Postgres
Browser
No response
Semaphore Version
v2.10.2-cc91501-1718257299
Ansible Version
No response
Logs & errors
Manual installation - system information
No response
Configuration
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: