LibreELEC custom shares: edit the persistent configuration, not its sample

Define one share change

Before editing LibreELEC’s Samba configuration, state the intended change in plain language. Adding a particular authorized folder is different from altering authentication or replacing every default share. Keep the actual path and intended users private, and preserve the working setup.

Use one harmless test file in the target folder. Confirm the appliance itself can access that path before exposing it to another computer. A path that exists only on a laptop cannot be shared from the appliance simply by placing it in a configuration file.

Distinguish the generated sample and persistent file

LibreELEC’s sharing guide identifies samba.conf.sample as a regenerated template and samba.conf as the persistent custom configuration. It says edits to the sample are lost on reboot. Locate the current files through an authorized administration route and inspect whether a custom configuration already exists.

Keep a copy of an existing custom file before editing. If none exists, use the current sample as a starting point through the documented route. Do not overwrite an administrator’s existing file merely because a tutorial begins by copying a template. Preserve unrelated working share definitions.

Apply the smallest intended modification

Edit only the share or setting required for the task and verify its actual folder path and access policy. Keep the syntax and surrounding structure valid. A public share name does not justify exposing credentials or broad filesystem access to everyone on the network.

Use the documented Samba restart or a normal device reboot to apply the configuration. Retain a way to recover the previous file if the sharing service does not return. A successful text save is not the same result as a running service accepting the new configuration.

Verify from the intended client and after reboot

Connect from the actual authorized computer and inspect the intended share. Confirm the harmless test file can be read or written according to the defined policy. Test the direction you intended; reading an existing file does not prove permission to create one, and vice versa.

After a normal reboot, repeat the connection and confirm the change persists. Keep the configuration backup and the observed client result in the device notes. The expected outcome is a narrow persistent share change. It does not replace a file backup, certify every network client or make appliance storage suitable for public exposure.

Related reading

• LibreELEC sharing settings: distinguish its Samba server from Kodi’s SMB client

Questions answered

Sources & further reading

Official references for the subjects discussed. Service terms and device software can change.

• https://wiki.libreelec.tv/how-to/add-content-via-samba-shares