When the shared folder does not appear or does not behave.
That is direct-transfer mode: no FUSE driver was detected. Install the driver for your platform, restart KeibiDrop, and connect again:
macOS blocks the driver until you allow it: System Settings, Privacy & Security, allow "System software from developer Benjamin Fleischer", then reboot once. On Apple Silicon, the Allow button appears only after enabling reduced security with kernel extensions from Recovery. On macOS 15.4 and later, the FSKit backend avoids the kernel extension entirely: System Settings, macFUSE, "Use FSKit".
KeibiDrop mounts with allow_other so your programs and service accounts can read the folder. The kernel refuses that unless /etc/fuse.conf contains an uncommented user_allow_other line:
sudo sed -i 's/#user_allow_other/user_allow_other/' /etc/fuse.conf
Then disconnect and connect again.
KeibiDrop detects a dead mount at the next start and repairs it. If you need to clean up by hand:
sudo umount -f ~/KeibiDrop/Mount # macOS fusermount3 -u ~/KeibiDrop/Mount # Linux fusermount3 -z ~/KeibiDrop/Mount # Linux, if the above is busy
K: is simpler.K: blocks the mount. Change mount_path in the config file.By design. The mount stays alive across a disconnect: reads in flight are cancelled, and a reconnect to the same peer finds its files without refetching. Partial downloads resume by themselves (.kdbitmap sidecars mark them; note that resume does not work in incognito mode). The mount goes away when you quit the app or stop the daemon.
Still stuck? Collect a log and report.