Filebrowser not have permission

eWeLink CUBE
1

Good morning,

Since a few days I have problems with the filebrowser.
After an upgrade, both the filebrowser to its latest version and ihost to 2.5.2
I can’t create or edit files on the volumes I have mounted.
I browse through the volumes, ready them and it all works correctly, but if I try to create a file, directory or edit an existing one, it gives me a permissions error: permission denied

I don’t know if anything has changed in the way ihost mounts the volumes or permissions and some extra variable with UID, GID, etc. should be put in order to correct this problem.

Any of you have this problem and have been able to find a solution?

Thank you very much

2025-07-08T10:25:11 2025/07/08 08:25:11 /HomeAssistant/test/: 403 192.168.68.136 mkdir /srv/HomeAssistant/test: permission denied

2

Good afternoon! Try adding the “auth.method=noauth” parameter when starting the file browser.

3

Good morning,

Could you please indicate how to introduce it in the docker deployment on ihost?

I’ve tried to put it in Show Advanced Settings → Command : "auth.method=noauth

And when I pick it up I get error:

Error: unknown command “auth.method=noauth” for “file browser”

2025-07-08T13:43:19 Run ‘file browser --help’ for usage.

4

The installation instructions can be found at the link:

In the end, it should look something like this

Снимок2
Снимок2946×597 43.4 KB

5

Yes, but it doesn’t let me edit the gray shaded area you indicate, in order to add it, the ihost options are these:

image
image889×947 41.3 KB

once I fill it up, it appears:

image
image1703×1328 146 KB

as I can edit those gray values ​​in order to add the auth.method=noauth

Thank you very much

6

Unfortunately, I no longer remember which fields I wrote the application launch parameters into. Try two options: 1) specify the value “auth.method” in the “Variable” field, and “noauth” in the “Value” field; 2) write the parameter “auth.method=noauth” in the “Command” field.

7

I have included the noauth , and verified that it appears, but it continues an erroneous operation without permissions:

image
image1443×1292 70.9 KB

I am trying to create a test directory:

2025-07-10T08:33:43.652922369Z 2025/07/10 08:33:43 /HomeAssistant/test: 403 192.168.68.109 unlinked /srv/HomeAssistant/test: permission denied
2025-07-10T08:33:52.729875741Z 2025/07/10 08:33:52 /HomeAssistant/test/: 500 192.168.68.109 mkdir /srv/HomeAssistant/test: not a directory

8

Then look at these settings

Снимок
Снимок3751×1741 258 KB

9

Also, try installing file browser not in the root, but in your volume.
For example, like mine:
filebrowser-volume:/config
filebrowser-volume:/database
filebrowser-volume:/srv

10

Hi. I am having the same issue, can read the files but cannot write to them. As I saw only volumes that were created upfront is affected, my node-red is in a volume which was not created in advance and files in this one can be modified. Any suggestions on how to make the files read / writable once more?