2.16 no longer follows symlink

[princemaple]

Description
Opening a symlink to a folder no longer works

Expected behaviour
in 2.15 it works

What is happening instead?

500 read /path/to/target/location is a directory

Additional context
N/A

How to reproduce?

ln -s some_where some_link

try and open some_link

Files
N/A

[princemaple]

Thanks!

[Andoramb]

Hi!
I'm on 2.16.1 (docker) symlinks are still considered a file

[ramiresviana]

Hi!
I'm on 2.16.1 (docker) symlinks are still considered a file

Are you able to access the link using a shell? Invalid links will be shown as a file on FileBrowser.

[Andoramb]

Hi @ramiresviana
You're right, I also cannot open symlinks (running filebrowser in docker). However symlinks are ok on the host. Has it something to do with permissions? UID/GID?
Thanks :)

[Andoramb]

Attaching the same folders in docker-compose works without problem.
As for the symlinks: ls -al shows the original path for the folders, which is inaccessible of course from within the container.

EDIT: another strange behavior: in docker compose: by adding
- "${MEDIA}/DATA2:/srv/media"
to the volume, the app creates empty folders on the host at "/srv/media"

[Nepherim]

Looks like this is still an issue. Path is navigable from the OS, but the link shows as a file in FB. Happy to help with log info, etc.

[ParronS3]

Hello, sorry for the refloating.I was having the same error. 2 symlinks i had were working, but the new I was trying to make was not.

I had solved it. The difference was that the woking ones were pointing from a relative route, the one thas i was creating was from an absolute one

[scambier]

I'm having the same issue, but relative or absolute links don't seem to make a difference. I'm on 2.27.0.

If the symlink target is a folder that is already available from Filebrowser, it works. If the target is outside, the link is shown as incorrect. The folder's owner is the same in both cases, if that matters.

Edit: I guess it's due to Docker to having rights to "outside" folders?

Edit2: It works as expected when Filebrowser is not executed through Docker