missing field "providers" ( Cannot read /dev/disk/by-label)

[teto]

What system are you running Yazi on?

Linux Wayland

What terminal are you running Yazi in?

kitty

yazi --debug output

Yazi
    Version: 25.9.15 (c6e03e9 2025-12-03)
    Debug  : false
    Triple : x86_64-unknown-linux-gnu (linux-x86_64)
    Rustc  : 1.91.1 (ed61e7d7 2025-11-07)

Ya
    Version: 25.9.15 (c6e03e9 2025-12-03)

Config
    Yazi             : /home/teto/.config/yazi/yazi.toml (6933 chars)
    Keymap           : /home/teto/.config/yazi/keymap.toml (2164 chars)
    Theme            : /home/teto/.config/yazi/theme.toml (No such file or directory (os error 2))
    VFS              : /home/teto/.config/yazi/vfs.toml (No such file or directory (os error 2))
    Package          : /home/teto/.config/yazi/package.toml (219 chars)
    Dark/light flavor: "" / ""

Emulator
    TERM                : Some("xterm-kitty")
    TERM_PROGRAM        : None
    TERM_PROGRAM_VERSION: None
    Brand.from_env      : Some(Kitty)
    Emulator.detect     : Emulator { kind: Left(Kitty), version: "kitty(0.44.0)", light: false, csi_16t: (10, 22), force_16t: false }

Adapter
    Adapter.matches    : Kgp
    Dimension.available: Dimension { rows: 51, columns: 192, width: 1920, height: 1122 }

Desktop
    XDG_SESSION_TYPE           : Some("wayland")
    WAYLAND_DISPLAY            : Some("wayland-1")
    DISPLAY                    : None
    SWAYSOCK                   : Some("/run/user/1000/sway-ipc.1000.2776.sock")
    HYPRLAND_INSTANCE_SIGNATURE: None
    WAYFIRE_SOCKET             : None

SSH
    shared.in_ssh_connection: false

WSL
    WSL: false

Variables
    SHELL              : Some("/run/current-system/sw/bin/zsh")
    EDITOR             : Some("nvim")
    VISUAL             : None
    YAZI_FILE_ONE      : None
    YAZI_CONFIG_HOME   : None
    YAZI_ZOXIDE_OPTS   : None
    FZF_DEFAULT_OPTS   : Some("--bind=\'ctrl-o:execute(code {})+abort\'")
    FZF_DEFAULT_COMMAND: Some("/nix/store/027m34av4nx0246ia2qdbfygzy9dbikw-fd-10.3.0/bin/fd --type f")

Text Opener
    default     : Some(OpenerRule { run: "xdg-open \"$1\"", block: true, orphan: false, desc: "xdg-open", for: None, spread: false })
    block-create: Some(OpenerRule { run: "xdg-open \"$1\"", block: true, orphan: false, desc: "xdg-open", for: None, spread: false })
    block-rename: Some(OpenerRule { run: "xdg-open \"$1\"", block: true, orphan: false, desc: "xdg-open", for: None, spread: false })

Multiplexers
    TMUX               : false
    tmux version       : 3.6
    tmux build flags   : enable-sixel=Supported
    ZELLIJ_SESSION_NAME: None
    Zellij version     : No such file or directory (os error 2)

Dependencies
    file          : 5.45
    ueberzugpp    : No such file or directory (os error 2)
    ffmpeg/ffprobe: 8.0 / 8.0
    pdftoppm      : 25.10.0
    magick        : 7.1.2-8
    fzf           : 0.67.0
    fd/fdfind     : 10.3.0 / No such file or directory (os error 2)
    rg            : 15.1.0
    chafa         : 1.18.0
    zoxide        : 0.9.8
    7zz/7z        : 25.01 / No such file or directory (os error 2)
    resvg         : 0.45.1
    jq            : 1.8.1

Clipboard
    wl-copy/paste: 2.2.1 / 2.2.1
    xclip        : No such file or directory (os error 2)
    xsel         : No such file or directory (os error 2)

Routine
    `file -bL --mime-type`: text/plain


See https://yazi-rs.github.io/docs/plugins/overview#debugging on how to enable logging or debug runtime errors.

Describe the bug

Thank you so much for native suppor ! It's one of the things I didnt have a good workflow before and yazi fixes it in the best way possible. Amazing work as usual.
While yazi sftp://... worked on several attempts, for one of my host I had a weird error

On startup

           │ Error: TOML parse error at line 1, │
           │              column 1              │
           │                   |                │
           │                1 |                 │
           │                  | ^               │
           │      missing field `providers`     

while trying to run:

➜ y sftp://REDACTED.com
Running with log level `yazi=DEBUG`, logs are written to "/home/teto/.local/state/yazi/yazi.log"
~ took 3s 
➜ less /home/teto/.local/state/yazi/yazi.log
  2025-12-04T09:06:50.564428Z DEBUG yazi_adapter::emulator: Terminal responded to DA1 in 3.274699ms: [27, 80, 62, 124, 107, 105, 116, 116, 121, 40, 48, 46, 52, 52, 46, 48, 41, 27, 92, 27, 91, 54, 59, 50, 50, 59, 49, 48, 116, 27, 93, 49, 49, 59, 114, 103, 98, 58, 48, 48, 48, 48, 47, 48, 48, 48, 48, 47, 48, 48, 48, 48, 27, 92, 27, 91, 63, 54, 50, 59, 53, 50, 59, 99]
    at yazi-adapter/src/emulator.rs:130

  2025-12-04T09:06:50.564737Z DEBUG yazi_adapter::emulator: Detected background color: 0000/0000/0000 (luma = 0.00)
    at yazi-adapter/src/emulator.rs:198

  2025-12-04T09:06:50.572341Z DEBUG yazi_adapter::emulator: Terminal responded to DA1 in 3.567018ms: [27, 80, 49, 36, 114, 49, 32, 113, 27, 92, 27, 91, 63, 49, 50, 59, 48, 36, 121, 27, 91, 63, 48, 117, 27, 91, 63, 54, 50, 59, 53, 50, 59, 99]
    at yazi-adapter/src/emulator.rs:130

  2025-12-04T09:06:50.573151Z ERROR yazi_fs::mounts::linux: Cannot read /dev/disk/by-label
    at yazi-fs/src/mounts/linux.rs:147

  2025-12-04T09:06:50.573333Z ERROR yazi_fs::mounts::linux: Cannot read /dev/disk/by-label
    at yazi-fs/src/mounts/linux.rs:147

At first I was not sure if ths was an error in my config but grepping for "providers", I could see references in yazi-config/src/vfs/vfs.rs.

and indeed on the remote server I see no /dev/disk/by-label:

$ ls /dev/disk/by-<TAB>
by-designator/  by-id/          by-partuuid/    by-uuid/        
by-diskseq/     by-partlabel/   by-path/   

I guess I could try attaching a label to workaround that

Minimal reproducer

see before

Anything else?

No response

Checklist

• I tried the latest nightly build, and the issue is still reproducible
• I updated the debug information (yazi --debug) input box to the nightly that I tried
• I can reproduce it after disabling all custom configs/plugins (mv ~/.config/yazi ~/.config/yazi-backup)

[github-actions]

Hey @teto, I noticed that you did not correctly follow the issue template. Please ensure that:

• The bug can still be reproduced on the newest nightly build.
• The debug information (yazi --debug) is updated for the newest nightly.
• The non-optional items in the checklist are checked.

Issues with needs info will be marked ready once edited with the proper content, or closed after 2 days of inactivity.

[teto]

can you be more precise @github-actions ?

[sxyazi]

Hi, thanks for the report and for trying out the new feature!

VFS              : /home/teto/.config/yazi/vfs.toml (No such file or directory (os error 2))

I noticed Yazi couldn't find vfs.toml, did you create it and register your SFTP service there?

As for the error, it looks like parsing failed because nothing could be loaded from vfs.toml. I think we should add a preset vfs.toml and initialize providers as an empty dictionary by default in that case. I'll open a PR to fix it later - nice catch!

[teto]

I noticed Yazi couldn't find vfs.toml, did you create it and register your SFTP service there?

I missed that ty ^^'' Is it supposed to be created manually ? I've never created any, I thought yazi would pic my ssh config.

I've been testing yazi sftp://redacted from 2 different machines yesterday and I thought it was working on the first one and not the second but now it looks like it fails on both with the same message here. I dont know if I dreamt it worked or if I changed anything in my config in those few hours that broke it ^^''

[sxyazi]

Yeah, that won't be created automatically and needs to be created manually

[teto]

Is there a technical reason behind this ? I have everything specified in my ssh config such that I just have to do ssh mydomain.com.
Ideally I would have yazi recognize the domain after sftp:// and use it as is, passing it to some libssh library in charge of reading my ssh config, taking care of auth and everything.

[sxyazi]

I want to have a protocol-agnostic config file where all VFS services (SSH, S3, Rclone, etc.) can be configured, and can be extended to add fields to meet Yazi's own needs in the future more easily, which would also make troubleshooting simpler as users only need to debug this one file along with the docs of Yazi if any VFS service doesn't work

…

On Sun, Dec 7, 2025 at 9:57 PM Matthieu Coudron ***@***.***> wrote: *teto* left a comment (sxyazi/yazi#3401) <#3401 (comment)> Is there a technical reason behind this ? I have everything specified in my ssh config such that I just have to do ssh mydomain.com. Ideally I would have yazi recognize the domain after sftp:// and use it as is, passing it to some libssh library in charge of reading my ssh config, taking care of auth and everything. — Reply to this email directly, view it on GitHub <#3401 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEFWFIHCQWQLSPU63GOTMRT4AQW55AVCNFSM6AAAAACOAMTFE6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMMRSGEYTIOBXGY> . You are receiving this because you commented.Message ID: ***@***.***>

[teto]

ty for the fix.

As for your answer, I am not sure it prevents my proposition. if you open yazi with yazi sftp://MYDOMAIN.com, yazi can parse the protocol sftp://, look for a matching provider in /home/teto/.config/yazi/vfs.toml but even if it doesn't exist, it could go on and let libssh (or whatever yazi uses) deal with the connection. That yazi dependency "just" needs to understand the ssh config (that's the point I dont know if it's the case or not).

[sxyazi]

vfs.toml was introduced to avoid trying to parse the config of the various providers (SSH, Rclone, etc.) as those configs have many options and it's unlikely we can support all of them, and when users set an option there and find it doesn't work in Yazi might be surprised.

For SSH, Yazi defaults to using your SSH agent for authentication, so if you can connect to your server with the agent, you should be able to connect in Yazi as well, but you'd still need to register it in vfs.toml as a service. If you're looking for a solution that fully follows your SSH config, you might want something like sshfs.yazi