Termix-SSH / Termix-SSH/Support

[BUG] - Filebrowser fails when using Vault Credentials

Open
#1,225 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

auth bug file-manager platform-proxmox platform-web ssh
Dominant language
No language data
Stars
28
Forks
4
PR merge metrics
No merged PRs in 30d

Description

Title

Filebrowser fails when using Vault Credentials

Platform

Website - Chrome

Server Installation Method

Proxmox (Community Scripts)

Version

2.7.1

CLI Installation Method

None

CLI Version

No response

Troubleshooting
  • I have examined logs and tried to find the issue
  • I have reviewed opened and closed issues
  • I have tried restarting the application
  • I have checked open issues and ensured this is not a duplicate
The Problem

Using Vault Authentication makes it impossible to use the File Browser.
Opening the File Browser fails during auth with:

13:41:47
Initiating SFTP connection to XX@HOST
13:41:47
Resolving authentication credentials
13:41:47
Credentials resolved from server-side host data
13:41:47
No valid authentication method provided
13:41:47
Failed to connect to SSH: Either password or SSH key must be provided```

### How to Reproduce

1. Create a Host or edit a Host to use Vault / a Vault Profile for Auth. 
2. Start an ssh Session to verify it works
3. Start a File Browser Session to receive the SSH Connection Issue

### Additional Context

Aug 28 13:44:33 termix node[1167846]: [1:44:33 PM] [WARN] [📁] No valid authentication method provided for file manager [op:file_connect,host:XX,session:XX]

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the File Browser connection with a Host using Vault or a Vault Profile, then compare its credential-resolution path with the working SSH session. Use the reported file manager warning and SSH authentication error as the initial trace points; done means File Browser can authenticate through Vault credentials without requiring a separate password or SSH key.

Written by the indexing model from the issue text.

Assessment

Domain
authentication, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.