Repository navigation
SSH Provider: "Add new connection" form fails to save entries, while editing existing hosts works #1088
Replies: 4 comments
|
I can't reproduce this, but why are you running YASB as admin? |
|
I am running YASB as an Administrator to test whether new SSH connections can be saved properly, but the issue persists. Since saving new hosts through the app continuously failed, I manually edited the Both hosts were successfully detected under the SSH Provider, and editing these existing hosts through YASB works as expected. However, whenever I attempt to add a new host via the application, it is never saved to |
|
Works fine for me... 2026-08-31.01-46-05.mp4I will check, and maybe I can add some logging there, but I am not sure what can fail because the log should already show if something is wrong. Did you check the YASB log? Or open a terminal, type |

Uh oh!
There was an error while loading. Please reload this page.
When using the ssh provider inside the quick_launch widget, attempting to add a new SSH host via the "Add new connection" UI panel does not work. Clicking the Save button does not append any new entries to the ~/.ssh/config file, nor does it yield any UI feedback or error logs in yasbc logs.
However, modifying an already existing host via the "Edit connection" right-click context menu works as expected and correctly writes changes back to the config file.
Environment
OS: Windows
Widget: yasb.quick_launch.QuickLaunchWidget (SSH Provider)
Execution: Ran as Administrator (permissions verified, file is not read-only)
Steps to Reproduce
Open Quick Launch (Alt + Space) and type ssh.
Click on "Add new connection" in the list.
Fill in the fields (Host alias, Hostname / IP, User, Port).
Click the Save button.
Expected Behavior
The new host entry should be appended to the ~/.ssh/config file and appear immediately in the SSH provider search results.
Actual Behavior
Nothing happens upon clicking Save. The form does not submit, no new entry is saved to the config file, and no error message is outputted to the logs.
Editing existing hosts via the UI works completely fine, indicating that write permissions to ~/.ssh/config are not the root cause.
Adding entries manually to ~/.ssh/config via a text editor works and YASB reloads them correctly.
All reactions